Quote:
I'm getting the problem again, even with FreePHG running at higher priority. It looks like FreePHG is using about 50% of the CPU time and Party is using about 35%.
How much memory if Party using? If Party is leaking memory, then each cycle of FPHG will take longer thus using much more CPU time. If Party is leaking memory badly then their is a chance that FPHG will have to be scanning swap-file too, making it run much much slower.
Try editing run.bat like this:
freephg.exe -d 1500
This will cause it to rest longer between scans, but it will be more likely to miss hands.
If you still have problems, then edit run.bat like so:
freephg.exe -prof >> log.txt
Run FPHG using run.bat few times, then send me the logfile via email. If I get time, then I will add an extra debug mode (-prof is not ideal for this), and this may help show if Party is using tons of memory. I may even be able to identify leaked segments of memory and avoid scanning them...
One last idea, is to install ProcessGuard and check if Party is trying to read other processes and dump their contents to disk. I have caught it doing this before, and it used a serious amount of CPU time as it tried to do it, causing Party to pretty much slow to a crawl.
Juk