high CPU consumption after long period of inactivity

[pt4pt4pt4]

That's the way logging works... a new file created each time you start PT4 (IIRC). If you have a PT4 crash/problem it's best to copy the current log off to, say, your desktop B4 you restart PT4.

I didn't know that. I thought it automatically appended each session to the log file.

[pt4pt4pt4]

Also notice the CPU after importing from a directory. The load was consistently about 80% while imports of the log was completed.

If you have the same CPU utilization problems, stop your import and see if the problem takes care of it self.

[pt4pt4pt4]

I thought I would try and see if I could duplicate the problem by just running PT4, Stars running, and switch user while I did other things. Tried this a couple of times (didn't play poker but did import observed hands from two tables).

So everything is working fine and then I install a new wireless mouse and right away the process Pokertracker4.exe *32 jumps to between 16 - 30 percent. Wouldn't settle down to zero until I stopped import 15 minutes later.

I then started import again and Pokertracker4.exe *32 jumps back again to between 16 - 30 percent. Wouldn't drop back down to zero.

PT4 also did a double import again. Note the time on the images and the same imported observed hands, 3 hours later:

[kraada]

Do you have a log from that attempt?

[pt4pt4pt4]

No, I forgot that it wipes out the log and restarted CPU / PT4 to see if any problems were still around.

[pt4pt4pt4]

I kinda messed up again, but I have an Import for the same hands for the 3rd time, as it imported the same hands.

First time it said imported, and then it imported again at a later time. I restarted PT4 and it imported the same hands the 3rd time.

I cut this out where i had seen an error message prior to the 3rd import:

[TableManager (Warning)] Could not locate window for table: '580676865 3'

So i went to restart PT4 again and fortunately for me, it imported the same hands for the 3rd time (i overwrote the previous log file again ).

But I have the log file for the 3rd import with the same kind of error messages. So Where do you want the log file or do I PM you with it?

[WhiteRider]

Observed hands are read from PokerStars memory and until you restart PokerStars they remain in memory, so when you restart you will see the 'observed but not imported' messages - that won't cause any problems.

So everything is working fine and then I install a new wireless mouse and right away the process Pokertracker4.exe *32 jumps to between 16 - 30 percent. Wouldn't settle down to zero until I stopped import 15 minutes later.

We do occasionally see interference from other drivers or application - please make sure you have the latest drivers for your new mouse and see if that makes any difference?

[pt4pt4pt4]

So found out when PT4 was killing my machine and CPU what was going on. I checked Task Manager and it showed nothing yet my CPU dual core running at almost %100.

I then clicked "Show process from all users" in Task Manager and there it was: All four postgres.exe*32 were running at %100 almost (?) and apparently for no reason.

So ask your users to check this if they are experiencing high CPU utilzation.


Another question: PT4 hogs all the CPU processes when you start an import while you are already playing (start PT4 after you have been playing a bit). this shuts down / hangs your poker client while %100 of the CPU is held hostage by PT4..

Can PT4 import be reduced in process consumption at start up, or at least the option of a slower import? I would rather have for 5 minutes my HUD inactive then have my poker client hang for 30 - 60 seconds at multiple tables.

Option to increase / decrease priority for PT4 import?

[WhiteRider]

When there are existing hand histories to be imported that will always generate load. PostgreSQL run independently of PT4 and we can't control it's work rate. You could change the priorities in Task Manager, but be careful if you decide to experiment with that as it could has unexpected side-effects.

[dbabo]

When there are existing hand histories to be imported that will always generate load. PostgreSQL run independently of PT4 and we can't control it's work rate. You could change the priorities in Task Manager, but be careful if you decide to experiment with that as it could has unexpected side-effects.

just to update on my troubles:
I still have the same problem - PT hanging after period of inactivity - few hours. But what still annoys me the most is that i have to restart the HH import after long inactivity. Basically PT can't detect that the HH file has changed.