Updating cache

[bpran]

I just imported 1 million hand histories into PT3 and right now it's updating cache.
The question is:
how long will take to update cache, because it's been doing that for almost 17 hours???
Is this common?

If not, what should I do next?

[kraada]

The cache update can take quite a while, especially if you already had a few million hands in the DB you imported to. Is your computer still working on it? Press ctrl+alt+del, click Task manager and see whether the postgres.exe processes (on the Processes tab) are actually doing anything. If they're using up a chunk of CPU it's still working and let it finish.

If you had logging enabled (configure --> options --> logging enabled) you can look at the last line of the log file and see where in the cache update process PT3 is. If not, you can also check the most recent file in C:\Program Files\PostgreSQL\8.3\data\pg_log and see if it's been updated recently (like within the last 2 minutes), if it hasn't the process has likely stalled and you'll need to kill it. Then I'd recommend enabling logging before rebuilding the cache just so you can follow the process in the log file.

[bpran]

My computer still updating cache right now, and it's going into 20 hours.
I have few of postgres.exe under the 'processes' tab and most of them has 0 value.
I checked the log and the message in the log is:
could not open temporary statistics file "global/pgstat.tmp": permission denied

I tried clicking cancel, but the software gave me msg that the housekeeping only will be cancelled after finishing the current action.

You said I need to 'kill' it, how to do that?
What else should I do?

[kraada]

In the Task Manager on the Processes tab, click on PokerTracker.exe and click "End Process". It will prompt you with a warning, say yes, and PT3 will be (forcefully) closed.

Depending on what state your cache creation was in it may be unstable and it would be a good idea to try and run it again (this time with logging enabled) to correct any errors.

[bpran]

I think I know what causing the problem now. Disk Space.
I am planning to uninstall my postgres and PT3 from disk C and installing again to disk D (bigger space), but I already use my 2 registration codes on 2 different computers. By uninstalling from disk C and installing on disk D, can I still use the same registration code?

[kraada]

Even though I replied to your PM, just so everybody else knows, the answer is Yes, so long as you uninstall you can reinstall PT3 again without any problem.

[preparac]

I killed the cache updating process (after 20 h running for about 2 Mio hands, I have a core duo, XP, Beta 19) like you counsel in this thread. Now I get weird stats in my reports, f.ex. 9000 player and 365,014,684 hands. From one player I have 8 Mio hands ... would be nice but not realistic. My other DBs show me still normal numbers ... what could be the problem? Any idea?

[preparac]

Ah yea, but all percentage stats (the ccall stat for example) seem to give me ok values...

[kraada]

Once you have the space, recreating the cache should resolve this issue.

[preparac]

FYI, I found out where the problem with my database was:
I was experimenting quite alot with custom stats and used for some stats the lookup_street_action DB-field in the tourney section. There seems to be really a bug with this DB-field, as it doesn't only gives sometimes weird results in the reports (millions of hands for a single player...) but also it causes a terrible slowdown when I tried to update the cache (runnnig for days with my basic DB before I finaly shot down the process, or for example running 6 minutes for 1000 hands!)...
Since I deleted the custom stats (columns) using the lookup_street_action field, I do not have problems any more ... my DB now uptdates the cache in 45 minutes.

cliffnotes: There is a bug with the lookup_street_action DB-field in the tourney section. If you have problems updating your cache, watch your customs stats ...