PokerTracker

I've been using postres 8.4 for a year, and I guess w/out too many problems, even if i don't always love it's speed. I just noticed that there's a new 9.0.2 version our. Is it definitely texted w/ PT3? Will there be any noticeable differences?

Fyi: I have Windows 7 (64-bit) machine, Quad Core processor 2.4 Ghz, 8GB memory. Is this new postgres version going to make a difference, or even hurt things? Thanks.

We have one developer using it, though I haven't switched over myself yet (I plan to I just haven't had a chance). It shouldn't break anything; there are some settings that should improve performance though exactly how much is as of yet untested.

To switch you would need to backup and then restore your databases though, so do keep that in mind if that's something you want to do.

Did either of you move over to 9.0.2 and if so did you notice any performance improvements?

I've been a bit too busy lately to make the switch, but I'll be going from 8.3 directly to 9.0 so I suspect I'll notice at least reasonable improvements. We do have more than one development team member on 9.0 full time and we haven't experienced any issues with it that I'm aware of to date.

This got me thinking.. can PT3 run off any DB?

If so what would be the absolute best

PT3 can use any version of PostgreSQL 8.3 or newer. We ship with 8.3, the latest 8.4 will work fine and we haven't had any reported problems with the latest 9.0 versions though those have gotten significantly less testing.

Personally, I plan to move to 9.0 soon, but the differences really are quite minor.

No, I meant would you get better performance off an Oricle DB or something?

PokerTracker 3 will not run on other database platforms.

I upgraded. So far so good. No problems and TBH no noticable performance increase.

I was dissapointed as I was hoping this would be the cure for the lag in my HUD (especially noticable in the time it takes for the HUD to popup on the replayer) 20 seconds or so.

I have followed the rush optimisation instructions

4GB machines:

Code: Select all
work_mem = 32MB
shared_buffers = 512MB
logging_collector = off

And also added the following

from_collapse_limit = 12
join_collapse_limit = 12


The rush optimisations didnt really do much (I have 6GB rather than 4GB)

Setting these did help a lot in bringing that lag down to 20 seconds.

from_collapse_limit = 12
join_collapse_limit = 12

My machine is blisteringly fast so its not the machine that's causing the lag, its an i7-950 over clocked to 4Ghz with 6Gb DDr3 RAM

I do have custom stats in my HUD, which I dont think helps a lot.

But that said the standard HUD dosent exactly spring to life either!

Can you think of any more tweaks I can try?

It wouldn't be so bad if the lag was just on the first hand I replayed in the replayer and then after that it was instant.. but its 20 seconds on every hand... its usable but at the same time frustratingly slow.

Any ideas would be greatly appreciated.

The Replayer cannot use the cache because it shows stats from the time that the hand was played – this means it takes a bit longer to retrieve and display them.