GPU tasking with APP CONFIG

Message boards : Questions and problems : GPU tasking with APP CONFIG
Message board moderation

To post messages, you must log in.

AuthorMessage
MatLioLeC

Send message
Joined: 10 Feb 19
Posts: 1
Canada
Message 89998 - Posted: 11 Feb 2019, 0:46:26 UTC

Hello. i was wondering someone could help me with app config.

I'm using boinc right now to mostly do Milkyway@home. i recently purchased a R9 280x with a decent FP64 rating and i've been messing around with the configurations.

i think i found a very good configuration but it's a bit different

see when i run one task at a time, i get it done in about 35-41 seconds. when i load up 4 at once i can get it done in an average of 32 seconds per task... when i load up 19 at a time, i get an average of 27 seconds per task!

but theirs a catch.. it has to do the work in blocks. right now i'd like to set it to do 14 tasks at a time, it seems somewhat ideal. so 0.07 gpu fractions and i have it at .1 cpu. but to get it to do 14 task and not take on another b4 the 14 are all done. and once the 14 are done, it loads another 14 tasks..

i'm not sure what kinda line i would need to add to the APP_CONFIG. plz help with this little problem, thank you.

<app_config>
<app>
<name>milkyway</name>
<max_concurrent>30</max_concurrent>
<fraction_done_exact/>
<gpu_versions>
<gpu_usage>.07</gpu_usage>
<cpu_usage>.1</cpu_usage>
</gpu_versions>
</app>
</app_config>
ID: 89998 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 90015 - Posted: 11 Feb 2019, 16:04:21 UTC - in response to Message 89998.  

If I understand correctly what you want then no, it can't be done. When one task ends BOINC starts another, it won't wait for all tasks to finish.
ID: 90015 · Report as offensive
mmonnin

Send message
Joined: 1 Jul 16
Posts: 146
United States
Message 90019 - Posted: 11 Feb 2019, 16:33:36 UTC

I thought the completing 14 at once before starting was the issue but they want all 14 to complete before starting another set of 14? As mentioned, that's not how BOINC works and for MW its not as efficient. MW has a bundle of 5 sub tasks that stop and start processing every 20%. That's the need for concurrent tasks. Letting them complete at different intervals is more useful by allowing GPU load to stay high.

I have a 280x myself on MW and only run 4x at once and get around 98% GPU util most of the time. At least when tasks aren't all sync'd up. Maybe a 5th task would help slightly but would just end up using more CPU time. MW has some slightly varied tasks lengths which correlate to their credit. Pls make sure all task lengths are the same when comparing. My ave run time is about the same as yours at 4x.
ID: 90019 · Report as offensive

Message boards : Questions and problems : GPU tasking with APP CONFIG

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.