Quote:
Quote:
I open 4-6 tables, cpu is fine. Over the course of the next 90 minutes I open and closes many tables and am playing at 5 (that I opened early) while mining 5 others, and soon the cpu is getting pegged every few seconds and everthing slows way down.
Tera
I cant really see an explanation, but even for me Party seems to be running badly lately (even for datamining). I used to be able to mine 3 clients without too many problems, but recently just 2 clients maxes my CPU.
Juk
I don't think it's the hhf's. I know from my experience speed-testing FPHG and playing with different loading conditions that Party behaves differently when you're playing tables vs. observing tables.
Party has significant memory creep once you start playing; more segments come into use, forcing FPHG to scan more and more memory. Part of the reason is that it starts remembering played hand histories, but the creep is too big to be explained by that; there is probably some leaking, as well.
In addition, there is a lot of creep caused by opening and closing tables; GDI objects just keep stacking up. If you're like me, you probably open and close a lot of tables finding your chosen four or five to play. . . and that causes a lot of dud objects to hang out in memory.
If you open 12 tables and just observe, Party will run stable for quite a while. This is probably how they ran it to test for bugs and leaks.
If you play four tables while cycling through all the rest of the tables, your memory consumption will increase steadily and you will build up thousands of discarded GDI objects. You can see them easily in task manager; just open and close tables and the number continues to grow! They obviousl did not test it while playing and surfing tables.