"System" using 4-7%CPU on 4870

[Peter Trend]

Im running the GPU2 client on a 4870, with the SMP client on the Phenom. Recently I noticed that as well as FahCore_11.exe using 22-27% of CPU constantly, there is another process launched by the GPU2 client called "System" which uses 4-7% of CPU. This is with the SMP not running and a very stripped down Vista x64.

Anyone know why this process is running and how I can minimise its impact on the SMP client?

So far I had to reduce the SMP to 70% usage, just to keep the GPU2 folding.
I read lots of mentions of FLUSH_INTERVAL with regards to ATI cards, but I still don't understand what I should set this to for best PPD.

I'll try and experiment unless somebody has any answers for me =]



p.s. GO TEAM 198! ;-)

 

[Philippart]

I have experimented with it a bit: with the most recent core, with a standard FLUSH_INTERVAL the core uses almost an entire core, the remaining % of the core usage go to the system process, sometimes also the taskmgr process due to all the data sending and switching between cpu and gpu. In the end the client uses an entire core. However you can modify the size of the work 'batches' which will be send from the cpu to the gpu up to 1024, this is your FLUSH_INTERVAL. On high end cards HD3850/3870/4850/4870/... you can set a high value, but verify that the windows gui doesn't lag. On low end or mid class cards too big batches causes freezes and gui lags. I recommend setting it to 768, that way you only have very little cpu usage (like with nvidia hardware) and you can fold on the cpu or run any other DC app on the same core.

On XP you open 'my computer', right-click-->properties, on the advanced tab click 'environment variables' and create the new FLUSH_INTERVAL variable with the value 768.
On VISTA it works exactly the same, just make sure you click on advanced system settings button on the left after displaying the system properties

EDIT: I recommend restarting your pc afterwards and to verify that it worked: use 'run' and enter 'cmd', a console window will open. Now enter in that console echo %FLUSH_INTERVAL% if everything worked it should give you the value you set before!

 

[Peter Trend]

Mods: Please delete

 

[Markfw]

Peter, that needs to be posted and cases and cooling, not DC.

 

[Peter Trend]

My mistake, ctrl+c in wrong window! Sorry

 

[Markfw]

No problem ! Also, we are more lenient in DC, but it didn't even seem related, or I wouldn't have said anything.

 

[Peter Trend]

Originally posted by: Philippart
I have experimented with it a bit: with the most recent core, with a standard FLUSH_INTERVAL the core uses almost an entire core, the remaining % of the core usage go to the system process, sometimes also the taskmgr process due to all the data sending and switching between cpu and gpu. In the end the client uses an entire core. However you can modify the size of the work 'batches' which will be send from the cpu to the gpu up to 1024, this is your FLUSH_INTERVAL. On high end cards HD3850/3870/4850/4870/... you can set a high value, but verify that the windows gui doesn't lag. On low end or mid class cards too big batches causes freezes and gui lags. I recommend setting it to 768, that way you only have very little cpu usage (like with nvidia hardware) and you can fold on the cpu or run any other DC app on the same core.

On XP you open 'my computer', right-click-->properties, on the advanced tab click 'environment variables' and create the new FLUSH_INTERVAL variable with the value 768.
On VISTA it works exactly the same, just make sure you click on advanced system settings button on the left after displaying the system properties

EDIT: I recommend restarting your pc afterwards and to verify that it worked: use 'run' and enter 'cmd', a console window will open. Now enter in that console echo %FLUSH_INTERVAL% if everything worked it should give you the value you set before!

Thanks for the quick response.
I have tried this, set the FLUSH_INTERVAL to 768 and see no difference in CPU usage. Still seeing "System" take 3-7% and FahCore_11 still consistently takes 23-27% (usually sticking at least on 25%).

The SMP basically just takes what's left over from the GPU as I set it on idle priority. I havent really experimented with CPU affinity yet.

Will try FLUSH_INTERVAL on 1024 now and let you know how it goes. I don't have any GUI lag yet anyway :thumbsup:

 

[Peter Trend]

Update: I tried 1024, as far as I can see it makes absolutely no difference to anything. GPU still uses up to 32% of the CPU!

 

[Peter Trend]

The SMP does seem to be very marginally faster than it was before, when running both GPU2 & SMP. My total PPD is up by 100 anyway, see for yourself http://i147.photobucket.com/al...llysnowman/4765PPD.jpg
However, it could be a coincidence because I changed WUs.