Playerview - Multiple DB Support?

[shant]

Excuse me if this as already been asked for, but I just started using PV today and I've thought of a feature I'd like to see.

Would it be possible to load multiple DB's for PV to scan through for players? I have a seperate DB for data-mining, and I'd like to scan those DB's as well.

[CT11]

I am very reluctant to include support for multiple DBs at the same table. (one DB per limit is ok)

The reason for this is speed. Adding more DBs will slow the program down linearly while growing one single DB will only slow things by an order of log(N). This can be a big difference.

I was considering adding a PV only DB which would be able to store only PV specific information and would be many many times faster (as in a constant factor rather than linear). You would then be able to merge PT DBs into a single PV DB.

This would be a while away (as in a release 1.5 or 2.0 sort of thing) as it requires a LOT of db code.

What are peoples feelings on this?

~CT

[kiddo]

What makes it slow is when PT is reading the handhistorys that is stored on your computer, not when PlayerView goes through the database? Or is Player View doing something at the same time, and it is that, that makes it slow?

Anyway, when your database grows you have to split it and as I understand it, this will be easier in next version of Pokertracker. If adding a "PV only DB" is the way to solve this, and u cant do it without a lot of work, I would gladly do another donation when u done it.

[amirpc]

I have multiple DB support coded and I have tested is as good as I can on my own system. Is there anyone out there whos willing to spend a little time on me with AIM or e-mail and test some stuff out? If so, please get with me (l0lnix) and once I'm satisfied I'll get this released.

[sthief09]

[ QUOTE ]
I am very reluctant to include support for multiple DBs at the same table. (one DB per limit is ok)

The reason for this is speed. Adding more DBs will slow the program down linearly while growing one single DB will only slow things by an order of log(N). This can be a big difference.

I was considering adding a PV only DB which would be able to store only PV specific information and would be many many times faster (as in a constant factor rather than linear). You would then be able to merge PT DBs into a single PV DB.

This would be a while away (as in a release 1.5 or 2.0 sort of thing) as it requires a LOT of db code.

What are peoples feelings on this?

~CT

[/ QUOTE ]


is that log(N) stuff Big-O notation? I'm wondering because if so, that means I learned something from the programming class I had to take last year

also, given that most of us data mine, multiple DB support is the #1 most important feature-to-be IMO

[goodguy_1]

Hey guys great work on PlayerView...but I had the same question as the initial poster.I have 7 large databases in PT.It would be great if your product supported multiple databases.I'm now into a new database.I've taken MS Sunshine's advice on this and I now start a new db every month.To decide what database to use I guess I need to chose either from my last database or a different databse that may have a more data.The problem is out of the 4/5 databases I've created over last half year.. the best one about 1GB is already 3 or so months old...problem is this databse has the most hands on it and the newer databses are smaller...tough choice eh?? any advice ...
It would be awesome if Playerview could combine/read off multiple databases.
IF Playerview is a big part of your arsenal(which it isnt yet for me right now but I'm working on it)you'll need fairly large sized databases to make it worthwile!!
This is a really a deficiency in Playerview as awesome as it is.
IF you can only read off one databse.My largest database was 1GB before it just got too slow to work with (about 240 handsK)this was over a long period of time.. 4 or 5 months.
I currently use that databse to use Playerview but it is 4 months old..My newer databases are smaller.So obviously if Playerview can not support multiple databses..to get the most out of this great product you should put more play into a databse before creating a new one...Any help appreciated or opinions ! I try to play 1500/+ hands every day/6 days a week so I have no problem generating new data.But you can open up a new db with 50K/100K hand on it and still not have sufficient data.
Thoughts?

[amirpc]

We're testing a version with Multiple DB support right now (thanks sthief)

[goodguy_1]

woohoo good news!!

[amirpc]

Yep sthief is testing it and everything is looking good. If I can get my math homework done and get everything tidied up before class I'll try to release in a few hours.

[amirpc]

Done, released. .8W available on the website.

Here