Quote:
I have smth like 600K hands in my database, and PT4 starts to load graphs slowly; also when I play many tables it's slow to load the stats, and sometimes they appear only for certain players of the table (which is very annoying).
When the database was lighter this didn't happen.
I'm clustering it right now. However I'm wondeing if it's time to create a new database.
600k hands really isn't a very large database and the sort of size that PT4 should cope with very easily, even with an extremely complex HUD including 100's of custom stats.
Do you have an SSD? If not, that is the single best investment you can make to increase the performance of PT4.
In our experience, with a decent PC setup and an SSD you should be able to comfortably multi-table with databases that contain several million hands.
Unlike PT3, most of the database maintenance is handled when you import new hands and thus you shouldn't really ever have to run database clustering.
Have you auto-tuned Postgres and have the latest version that PT works with (v9.0.15) ? The default configuration settings for Postgres presume an very poorly spec'ed machine. Running the PT Auto-Tune will adjust these to your actual machine spec.
Finally do you have "last x hand" or "last x weeks" set to anything other than 0. If you have, this means that the built-in stats wont take advantage of the cache system and seriously affect performance.
In terms of going to a new database, containing just your recent hands, there is certainly no harm in doing that. And on a personal level it is something I try to carry out every few months, mostly to stop database bloat of old irrelevant hands.
Quote:
Same for new players, if someone sits with me, I imagine that his stats are read from the new db, right?
It depends which databases you have set to be used in your HUD.
