Datamining/new computer performance issues

[djfl]

I datamine FTP with PTO, Party w FreePHG, and Cereus with Ultimateminer.
I just bought an Acer Aspire 8930G laptop...specs here http://www.staples.ca/ENG/Catalog/cat_s ... xedcode=WW
sparing all the details, it has 4GB's of RAM Core-2 Duo processor and an 800Mhz bus. It's brand new and pretty powerful
When I fire up PAHUD...I have automatic database caching enabled...my computer overloads. It slows right down and even stops receiving input for long periods sometimes. I checked my task manager and PAHUD and PostgreSQL seem to be hogging the most resources...tho we all know how Party and Cereus are both totally-unnecessarily resource hogs.

The initial updating of the PAHUD database takes hours to do because I'm importing so many hands. However, if I disable autocaching, then I'll probably end up with the problem of stats never being updated.

Either way, datamining currently leaves my...again...brand new computer unplayable. I get automatically say out every 3 hands or so and I'm not sure what to do. Is my new computer somehow way underperforming? Am I asking too much of this computer...and if so, what kind of system do I have to be running to datamine 3 sites and have PAHUD running?

I'd love to hear anybody's ideas and the sooner the better. I only have a few days left under the 14 day no-questions-asked warranty if I need to return the computer.

I'm really baffled.

Thanks.

[WhiteRider]

I would suggest letting the cache build overnight or something, while you are not playing. The first complete build will take a long time if you have a large database(s).
Personally, I don't use auto-update on the cache - I trigger the rebuild manually at the end of each session. This completes pretty quickly if you do it every day and means you don't get the slowdown at the start of your next session.

[djfl]

I would suggest letting the cache build overnight or something, while you are not playing. The first complete build will take a long time if you have a large database(s).
Personally, I don't use auto-update on the cache - I trigger the rebuild manually at the end of each session. This completes pretty quickly if you do it every day and means you don't get the slowdown at the start of your next session.

Thanks for the quick response and sorry for my delayed response. PAHUD's already built the initial cache. It's the updating of the cache every time I start it up that's the problem. Between it and postgresql...which I'm assuming it must query to access my postgre database...it takes up 60ish percent of my processor just by themselves.

The manual rebuild is an interesting idea that I'll consider if I have to. How do you manually do it? I could do it now, but it's still updating! :)

[WhiteRider]

See Options -> Preferences -> Databases; it's pretty self-explanatory..

[djfl]

I'm having database issues with PTO right now. Once I get that resolved, I'll certainly see if I want to manually import.

Until then, why is PAHUD being so resource intensive? 60% between it and postgresql on a brand new computer running 64bit Vista, 4GB RAM, Intel core2duo etc etc seems a little much and I don't know why. That's my real problem.

Thanks.

[WhiteRider]

If you are doing a lot of mining then you have a lot of database activity, and if the cache is updating at the same time it will be hammering postgres.
Try turning automatic cache updating off and see if that helps.