Forum > Windows

Please, help to balance CPU MB + ATI GPU MW on host under BOINC 6.6.36

<< < (9/9)

Raistmer:

--- Quote from: arkayn on 13 Jul 2009, 09:44:45 pm ---
The only time I have an idle GPU is when I am uploading work and getting new.

I am going to experiment with 700/300

--- End quote ---
Well, sometimes my config starts to work in that mode too.
I.e. reciving work from server only after all MW work is uploaded and reporting. It surely decrease effectiveness.
Yesterday, after extended brook AP benchmarking NW server started refuse fetch requests with messages like "BOINC running 90% of time, computationa enabled 100% of that, not completed in time." How it could not be completed in time if MW has bigger share, SETI has no debt and each MW task took (even from BOINC's own point of view) less than 1,5h - it's beyond my understanding  :-\

I switched to 6 ncpus and 1,51+0,01 avg_cpus - MW tasks were not started at all. Then I switched to 1,5+0.01 - situation resemble that was before: 4 SETI tasks running + ~20 MW tasks, some of them in high priority mode.


At evening I changed project sheres to 10000(SETI)+9500(MW) in hope that will reduce MW debt and number of running MW tasks.
STD of MW now (after whole night crunching) in ~86k sec, almost all available MW tasks in running state.
Apparently I should decrease MW share even more, but I don't quite understand why debt still increases.
How STD is calculated? I have project with lower share, it runs bigger number of tasks (i.e. consumes more elapsed time) than project with higher share, but still BOINC things that lower share project needs to work more. How is this possible? Or SDT calculations based not on elapsed time bu CPU time instead (in this case avg_cpu == 0.01 setting will tell BOINC that almost no work done by MW, correct? )

sunu:

--- Quote from: Raistmer on 14 Jul 2009, 02:52:54 am ---I switched to 6 ncpus and 1,51+0,01 avg_cpus - MW tasks were not started at all. Then I switched to 1,5+0.01 - situation resemble that was before: 4 SETI tasks running + ~20 MW tasks, some of them in high priority mode.

--- End quote ---

Well if it starts 20 MW tasks with 0.01 avg_cpus  then increase avg_cpus.

You might get a better feeling of all the dynamics involved by leveling things of. Zero your debt and put ncpus=8 and avg-max-cpus=1.0000 to both seti and MW. Playing with resource share you should be able to get the desired 4+4 effect. Then try to replicate that with ncpus=4.

Navigation

[0] Message Index

[*] Previous page