PokerTracker

Hi, I have noticed that everytime I play with stacked tables (15) my computer becomes extremely slow. The tables don't even cycle fast enough.

In the CPU 'processes' tab pokertrackerhud.exe takes up most of the memory and is using upto 50% of the CPU. If I turn the HUD off everything starts running smoothly again. Things seem working fine with tiled tables as well. I am running Table Ninja as well but turning it off doesn't seem to fix the problem.

Is there any setting I can change in PT3 that enhances HUD performance when my tables are being cycled so fast.

What are the specs on your computer? What version of PT3 are you currently using? Is your cache at 100%?

cache @ 100%
PT3 v3.07.4 beta

Windows XP Pro SP2
Intel Core 2 Duo
E7200@ 2.53Ghz
2.53 Ghz, 2.00 GB RAM
The name of my PC is HP XW 4600 by Hewlett Packard. I am running AVG anti-virus on it

Have you tried following the steps in the Performance Tuning: PostgreSQL thread? If not, give that a try. If that doesn't help, please restart PT3 with Logging Enabled, reproduce and report this problem so that we can investigate further and see what we can do for you.

hey kraada I just found it is definitely my computer. The same thing started happening when I just added more tables without HUD. If I wanted to improve my computer's specs what would you recommend I change?

i figure my processor speed is quite good so it must be the RAM and more importantly the HDD. I am leaning towards purchasing a SSD and installing windows PT3 and Postgres on it. What do you reckon?

An SSD will make a very large and noticible improvement. The only thing to note is that if you datamine or play heavily, the database does take up quite a bit of room.

ok well I have an internal SSD that I am going to install on my computer today. Should I be installing a fresh copy of windows on it and then run PT3 in that copy of windows or is there a more optimal way of doing this?

That would work.

I'd also strongly recommend backing PT3 and your database up before doing anything. It's just going to be a lot safer that way.