#1
|
|||
|
|||
pros/cons of multiple databases?
what are the cons of having multiple databases?... like when you use playerview... can it somehow draw stats from all the db's or do you have to just choose one?...
|
#2
|
|||
|
|||
Re: pros/cons of multiple databases?
Playerview can draw stats from multiple databases. I'm interested in other pros and cons of multiple DBs too.
|
#3
|
|||
|
|||
Re: pros/cons of multiple databases?
oh it can?... hrmm... what can the con's possibly be then?... i'm having dreams of instantly updating small databases instead of giant take-10-min-to-update db's
|
#4
|
|||
|
|||
Re: pros/cons of multiple databases?
I have 12 databases, it's good to have lots of smaller ones [img]/images/graemlins/wink.gif[/img]
|
#5
|
|||
|
|||
Re: pros/cons of multiple databases?
Kind of on topic.. I just recently stopped using multiple DBs in playerview because it was causing a ~5 second lag each update (during which I couldn't do anything). Using one relatively empty DB for recent hands fixes the lag problem, but I no longer have big sample sizes on frequent players.
|
#6
|
|||
|
|||
Re: pros/cons of multiple databases?
I'm currently using several databases, but I find that PV often disappears in the middle of hands.
I have 6 monthly databases with about 30k hands in each. This makes PT really simple and straightforward and pretty fast. Then I have 1 observation database that's at the max size and a new one that's growing. These are all 3/6 hands, and therefore nominally useful to me. In terms of PT, I don't mind consolidating old databases so that several months are stacked together, I'd just like to know whether that'll make PV more reliable. I'm always going to keep the new month separate, but if august-december became one DB, would that make PV faster? |
#7
|
|||
|
|||
Re: pros/cons of multiple databases?
how do these things work with the multiple databases?... like if you had 400 hands on player X on one mdb, and 800 hands on player X on another mdb, it would say "1200 hands and statx stax statx" on playerview?... how about when i'm looking on pokertracked will i get to see all the stats together?... sorry for so many questions i just started using all this stuff about a month ago and it's starting to take forever when i'm updating every 2 min....
|
#8
|
|||
|
|||
Re: pros/cons of multiple databases?
According to the designer, playerview will take the stats from every selected DB and compute the total stats.
PT will only ever internally display a player's stats contained in the current DB. |
#9
|
|||
|
|||
Re: pros/cons of multiple databases?
[ QUOTE ]
I'm always going to keep the new month separate, but if august-december became one DB, would that make PV faster? [/ QUOTE ] Yes, but probably not drastically faster. |
#10
|
|||
|
|||
Re: pros/cons of multiple databases?
I haven't run comparisons, but anectdotally PV is a lot more responsive now that I am running 4 DB (2 of which are 800MB+) than it was when I was running 8, one of which is 800MB+.
(same data basically) |
|
|