oracle3001 wrote:I have just downloaded the process explorer app, as I also suffer from serious hog etc when I go from 5/6 tables to 7/8 tables.
I am not sure how to post a screenshot, but I will try and explain some of the things I see which seem odd / don't understand. I have a dual core machine + 2GB RAM, very similar to the spec of machine Josh says he can run lots and lots of tables. I do have a quite complex HUD, with 4 separate "always visible" panels of stats for each player (+ pop-up's for each of them).
1) Overall when I run PT3 + HUD with 7/8 tables I get up to 100% on one core and hardly any use of the other. When I open the seperate panels for PokerTracker.exe and PokerTrackerHud.exe the CPU usage is tiny < 1%. The PartyGaming.exe spikes upto 30%. The vast majority of the rest is being used by "System Idle Process".
2) i) While the CPU usage is tiny on PokerTracker.exe and PokerTrackerHud.exe, the Private Bytes graph for PokerTrackerHud.exe is maxed out all the time. I don't know what this stat / graph means, but I am sure I it is not suppose to max out. It says it is out of 9.4MB, and is always using 100% of that. PokerTracker.exe uses about 75% of 120MB at all times. PartyGaming uses 90% of 50MB at all times. Could you tell me what this stat is etc
Are there any other things I should be looking at / trying to capture to see what the problems might be.
1. I don't know if PT3 has been coded to use > 1 core... - partygaming at 30% sounds reasonable; when i have 20 full-tilt huds going, tilt runs at around 45% CPU...
2. Don't worry about the private bytes - this is the total footprint of the process. The working set is the amount of that that is currently resident, i.e. available without a page fault. A page fault occurs when a process requests access to a procedure or data that is not currently resident in RAM and the operating system has to fetch it; large numbers of these are really bad news and a well known problem with systems with not enough RAM is that they constantly page fault (thrash) - this then leads to other problems with applications slowing, desktops unresponsive, etc.
I need to know your I/o's; both read & write and the page faults and the working sets for the postgres & PT + child processes...
susan