Veteran68
11-08-2011, 12:35 AM
I've been seeing a number of reports of horrible HM2 performance and high CPU utilization lately. Too many to discount, but personally I had not experienced it -- HM2 has been running pretty well for me though late alpha and the beta.
Then tonight after I activated my release HM2 key, I looked through my HUD settings and realized I had disabled NC in a much earlier alpha or beta build. So I re-enabled both NC options and restarted HM2. Later, while playing only 2 tables on Lock (Merge), I noticed the CPU gauge in my sidebar and saw one core was nearly pegged and total CPU utilization was something like 24% (I have a quad core i7, so that's about right for 1 core at nearly 100%). Checked Task Manager and the culprit was HM2. So I unchecked the NC options which requires an HM2 restart. I exited HM2 but didn't restart it right away. After a few minutes I noticed my CPU utilization had not decreased. There were no HM2 icons open nor anything in the task tray, but I realized the HUD was still on my tables. I had to kill HM2 from Task Manager.
Then I restarted HM2 (without NC enabled) and things ran fine again like they have been -- hardly a blip on the CPU gauge while playing the same 2 tables. I recall that I had disabled NC some time ago during the alpha/beta because of some stability or performance problem, and forgot to turn it back on. I had never gotten used to using it, so didn't really miss it. I would have re-enabled it again to try and reproduce the issue, but my session was winding down. Maybe I'll try again on my next session.
I'm wondering if this could be the culprit with new users who enable NC (or if it's enabled by default). It could explain why some of us (me) haven't been seeing these performance issues.
Win7 64-bit
Core i7 @ 3.4Ghz
8GB RAM
All poker and PostgreSQL folders have been excluded from my AV scans.
Then tonight after I activated my release HM2 key, I looked through my HUD settings and realized I had disabled NC in a much earlier alpha or beta build. So I re-enabled both NC options and restarted HM2. Later, while playing only 2 tables on Lock (Merge), I noticed the CPU gauge in my sidebar and saw one core was nearly pegged and total CPU utilization was something like 24% (I have a quad core i7, so that's about right for 1 core at nearly 100%). Checked Task Manager and the culprit was HM2. So I unchecked the NC options which requires an HM2 restart. I exited HM2 but didn't restart it right away. After a few minutes I noticed my CPU utilization had not decreased. There were no HM2 icons open nor anything in the task tray, but I realized the HUD was still on my tables. I had to kill HM2 from Task Manager.
Then I restarted HM2 (without NC enabled) and things ran fine again like they have been -- hardly a blip on the CPU gauge while playing the same 2 tables. I recall that I had disabled NC some time ago during the alpha/beta because of some stability or performance problem, and forgot to turn it back on. I had never gotten used to using it, so didn't really miss it. I would have re-enabled it again to try and reproduce the issue, but my session was winding down. Maybe I'll try again on my next session.
I'm wondering if this could be the culprit with new users who enable NC (or if it's enabled by default). It could explain why some of us (me) haven't been seeing these performance issues.
Win7 64-bit
Core i7 @ 3.4Ghz
8GB RAM
All poker and PostgreSQL folders have been excluded from my AV scans.