What's wrong with rereading the configuration? Works for me.

Boinc Manager > Options > Read configuration. I suppose that's the item in English, my Manager spells them in Dutch.

Because it doesn't work!

Did that got the T shirt. The only way to sort the problem out is either reset the project, and dump your cache, OR do what I did and edit client state files.

---

Regards,
Cliff.
--
Been there Done That, still no Damn T-Shirt

Hi Mikey,
yeah, makes sense, but I just wish someone in the programming dept at BOINC would makes those sorts of changes immediate.. Save a lot of faffing about to sort out a problem, particularly if you have a large[ish] cache of WU.

Regards

I believe this is a MW 'tweak' they made to their Server software, it isn't true at all the other projects.

Just for fun :) HD6970

Hey Everyone,

Just noticed this awesome thread and decided to make it sticky since it is very useful. Thank you all for this.

Jake

1WU ~18s/WU: ~128300 credit/day


4WUs ~12.5s/WU: ~184800 credit/day



It is +44% , less than i expected. (~74%)

13.1 driver, maybe the new is better...

12.10 good old driver is the best till now,~200.000 credits/day with my HD6970 when 2WU run.

Maybe it would be helpful to make an overview (new/other sticky thread) how much WUs/GPU simultaneously give the highest output referred to the VGA cards?


I start with...

After a few fast tests - more will follow - the current result:

On my AMD Radeon R9 Fury X's I let run 3 WUs/GPU with:

<app_config>
<app_version>
<app_name>milkyway</app_name>
<plan_class>opencl_ati_101</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<ngpus>0.33</ngpus>
<cmdline>--non-responsive --gpu-target-frequency 1 --gpu-polling-mode -1 --gpu-wait-factor 0 --process-priority 4 --gpu-disable-checkpointing</cmdline>
</app_version>
<app_version>
<app_name>milkyway_separation_modified__fit</app_name>
<plan_class>opencl_ati_101</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<ngpus>0.33</ngpus>
<cmdline>--non-responsive --gpu-target-frequency 1 --gpu-polling-mode -1 --gpu-wait-factor 0 --process-priority 4 --gpu-disable-checkpointing</cmdline>
</app_version>
</app_config>


On my NVIDIA GeForce GT 730 I let run 2 WUs/GPU with:

<app_config>
<app_version>
<app_name>milkyway</app_name>
<plan_class>opencl_nvidia_101</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<ngpus>0.5</ngpus>
<cmdline>--non-responsive --gpu-target-frequency 1 --gpu-polling-mode 0 --gpu-wait-factor 0 --process-priority 4</cmdline>
</app_version>
<app_version>
<app_name>milkyway_separation_modified__fit</app_name>
<plan_class>opencl_nvidia_101</plan_class>
<avg_ncpus>0.01</avg_ncpus>
<ngpus>0.5</ngpus>
<cmdline>--non-responsive --gpu-target-frequency 1 --gpu-polling-mode 0 --gpu-wait-factor 0 --process-priority 4</cmdline>
</app_version>
</app_config>


(strange, (pre) and (code) don't work properly - is the website broken?)


On both PCs no idle CPU-Cores, CPUs fully loaded with CPU WUs.

---

How about an a Gtx 980 OC. How many GPU tasks should I be able to run and what what would be the proper edit. On SETI I usually have 3 going to use 99% of the GPU cuda. Thanks.

I just experimented with my Radeon R9 290.

One at a time, it does a WU in 15 seconds.
Two at a time, it does two WUs in 25 seconds.
Three at a time, it does three WUs in 35 seconds.

So there is a speed advantage, but after running three for about 5 minutes, my screens all went off for a second, and all the WUs stopped. I restarted BOINC and they still stayed partially completed. I aborted the WUs and it carried on ok with the next ones.

I'll stick to one at a time.

I also noticed it did three together, starting and stopping them all at the same time, so I wasn't removing the gap between GPU 100% usage completely, just making it happen less often.

Maybe they should be giving out bigger WUs? Even my CPU cores can do them in 15 minutes. Or maybe only the GPU units could be bigger? Not sure what's possible at the Milkyway server end.

I also noticed it did three together, starting and stopping them all at the same time, so I wasn't removing the gap between GPU 100% usage completely, just making it happen less often

Well, in first run all workunits will start and finish almost simultaneously. But soon enough, they'll start diverging, creating a more balanced load. After a few runs and with 3 or 4 workunits running together, chances that they will all finish at the same time are rather small and your GPU load will almost never be zero.

I waited for 15 minutes, but they seemed to converge rather than diverge. With three at once, one of them was 5 seconds off, but it soon became equal. Then it crashed.

I have 4 GPUs each running 4 WUs, this is how they look in my BOINC. No two progress bars are the same:

http://www.upslike.net/images/2016/10/17/87e38f55b1922c5461bb4457ccb8a573.jpg

^^ Top computer in MW.

Try pausing a task for a second or 2 to offset one of them. Running 3 at once I would sometimes get 2 WUs at 100% so I moved it to 4x as well.

They seem to converge anyway if they're offset. Besides, I'm sticking to one to prevent it from crashing. I have three monitors on the card aswell, maybe it gets all confused with 6 things to do. The increase isn't x3 anyway, more like x1.3, not worth locking it up and losing loads of computing time.

So after some testing there is no real benefit to running multiple WU on the GTX980. With a max setting in the config file for 20 wu, it takes 12 minutes to process avg, all the tasks. 1 wu setting, takes 40seconds avg. Power % of the GPU never exceeds 58 even at 20 tasks at once. So simple math, I can do 20wu in 12 minutes or 1 in 40 seconds yielding 30 tasks avg complete over the same 12 minutes.

Doesn't matter if you can run 1 or 20 WUs if this project can't properly optimise the DB, scheduling, connections, etc.

Extreme mishandling and excessive server load.

What problems? I get plenty WUs.

As per the original post, this works to double up GPU WUs:

<app_config>
<app>
<name>milkyway</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>

But how do I make this work for the CPU requirements? I want certain projects to leave more CPU cores free when running GPU apps, as they need them. Specifically Einstein. I put "2" in the cpu usage, but it doesn't take effect. I still see "0.5C + 1 AMD/ATI GPU in the task list. Is <name>milkyway</name> important? I just substituted "einstein".

I use this app_config for Einstein AMD uses %11-14 and NVIDIA %3-7 for BRP4G

<app_config>
<app>
<name>einsteinbinary_BRP4G</name>
<max_concurrent>2</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.4</cpu_usage>
</gpu_versions>
</app>
</app_config>

---

Thanks, that worked. I put "1" into CPU usage, and it now takes a CPU core away from CPU WUs if Einstein is on the GPU.

Where did you get "einsteinbinary_BRP4G" from? Is it just the first bit of the "executable" in properties for the task?