by oracle3001 » Sat Aug 30, 2008 5:25 am
It always postgres.exe 's for me. It is the same problem as with the alpha releases, although much improved (i.e i can 8 table). It still remains that when auto-import is running, and a new hand is imported, the postgres.exe CPU usage spikes. However, mine might be linked to the fact that the cache building is playing up (which I have obviously posted about), in that I successfully build the cache and then on restart it says it doesn't exist. However, I don't believe that the cache doesn't exist, as before its inception I couldn't play more than 4-5 tables with my big datamined DB's due to the lag / constant high CPU usage. Since the cache introduction things are much improved, other than in this specific situation. Furthermore, the cache doesn't exist warning doesn't appear in a82, only b16. Given these two factors, I believe the cache has been built, but on start-up b16 is complaining about it. However on playing at the tables I am 100% sure it is using it.