Multiple task per GPU

Message boards : Number crunching : Multiple task per GPU
Message board moderation

To post messages, you must log in.

AuthorMessage
Alex2
Volunteer tester

Send message
Joined: 2 Nov 12
Posts: 24
Credit: 11,798,226
RAC: 0
Canada
Message 1361031 - Posted: 25 Apr 2013, 12:28:13 UTC

Do someone succeded at using app_config.xml to run multiple tasks per GPU to increse GPU usage IN SETI?
http://boinc.berkeley.edu/wiki/Client_configuration#Application_configuration

I tried without success:

Boinc 7.0.64, 64bits
app_config.xml in Project directory and Boinc reloded:

<app_config>
<app>
<name>setiathome_enhanced</name>
<max_concurrent>4</max_concurrent>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
</gpu_versions>
</app>
</app_config>[url][/url]
ID: 1361031 · Report as offensive
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 1361035 - Posted: 25 Apr 2013, 12:32:33 UTC - in response to Message 1361031.  
Last modified: 25 Apr 2013, 12:33:57 UTC

what you are trying to create is an app_info.

and it would probably be easier to use the Lunatics app_info and modify it to the stock seti app if that is what you are attempting to do.

However, by creating this file you also need to mention the CPU app otherwise it will not do any work.

Also, Most GPU's cant handle 4 WU's at a time.

From looking at your list of PC's I see you have 2 630's and a 650
You might be able to run 3 WU's on the 650 but definitely not on the 630's they can only handle 1 at a time


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 1361035 · Report as offensive
Profile William
Volunteer tester
Avatar

Send message
Joined: 14 Feb 13
Posts: 2037
Credit: 17,689,662
RAC: 0
Message 1361042 - Posted: 25 Apr 2013, 12:45:22 UTC
Last modified: 25 Apr 2013, 12:50:23 UTC

Skildude, Alex2 knows exactly what he's trying to do and that is an app_config.xml file to run more than one instance of _stock_ as the Lunatics installer is unavailable. That's quite a bit easier than trying to create app_info.xml from scratch for stock + x41zc.

Looks good to me - I'll try and figure out what went wrong - any clues in the Eventlog?

edit: you're missing <cpu_usage>0.02</cpu_usage> - maybe it needs that tag as well.

edit 2: with a max_concurrent of 4 you are limiting to 2 tasks on GPU plus 2 tasks on CPU (provided enough GPU work else more CPU tasks can run), is that what you want?
A person who won't read has no advantage over one who can't read. (Mark Twain)
ID: 1361042 · Report as offensive
Profile Fred E.
Volunteer tester

Send message
Joined: 22 Jul 99
Posts: 768
Credit: 24,140,697
RAC: 0
United States
Message 1361049 - Posted: 25 Apr 2013, 13:27:12 UTC

Should the application name be SETI@home_Enhanced instead of setiathome_enhanced? I don't run the stock app, so I can't confirm, but it is showing with the @ sign in the stderr's (I substituted the underscore for the blank and case is not important). Check the event log for a task startup to see what app name is used.

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.
ID: 1361049 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1361054 - Posted: 25 Apr 2013, 13:40:01 UTC - in response to Message 1361049.  
Last modified: 25 Apr 2013, 13:41:31 UTC

Should the application name be SETI@home_Enhanced instead of setiathome_enhanced? I don't run the stock app, so I can't confirm, but it is showing with the @ sign in the stderr's (I substituted the underscore for the blank and case is not important). Check the event log for a task startup to see what app name is used.

The application names for this project are setiathome_enhanced and astropulse_v6, that is what the scheduler sends out, that is what is put in the app_info.xml, changing it to something else won't work.

I've used the following to limit my number of tasks running here:

<app_config>
<app>
<name>setiathome_enhanced</name>
<max_concurrent>3</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v6</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
</app_config>

Claggy
ID: 1361054 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14644
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1361056 - Posted: 25 Apr 2013, 13:48:10 UTC - in response to Message 1361042.  

Skildude, Alex2 knows exactly what he's trying to do and that is an app_config.xml file to run more than one instance of _stock_ as the Lunatics installer is unavailable. That's quite a bit easier than trying to create app_info.xml from scratch for stock + x41zc.

Looks good to me - I'll try and figure out what went wrong - any clues in the Eventlog?

edit: you're missing <cpu_usage>0.02</cpu_usage> - maybe it needs that tag as well.

edit 2: with a max_concurrent of 4 you are limiting to 2 tasks on GPU plus 2 tasks on CPU (provided enough GPU work else more CPU tasks can run), is that what you want?

The max_concurrent line is (in practice) optional - I'd leave it out completely when using app_config.xml for this purpose.

Other things to check:
1) That the file is properly named app_config.xml, and hasn't been turned into app_config.xml.txt by your editor.
2) That you've put it correctly in the project directory.

@ skildude - I refer you to http://boinc.berkeley.edu/dev/forum_thread.php?id=8332
ID: 1361056 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14644
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1361058 - Posted: 25 Apr 2013, 13:54:23 UTC

Also, check the event log after either a BOINC restart, or (easier) a 'Read config file'. If the file is recognised, you should see

25/04/2013 14:51:02 | SETI@home | Found app_config.xml

ID: 1361058 · Report as offensive
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 1361078 - Posted: 25 Apr 2013, 15:31:07 UTC - in response to Message 1361056.  

Skildude, Alex2 knows exactly what he's trying to do and that is an app_config.xml file to run more than one instance of _stock_ as the Lunatics installer is unavailable. That's quite a bit easier than trying to create app_info.xml from scratch for stock + x41zc.

Looks good to me - I'll try and figure out what went wrong - any clues in the Eventlog?

edit: you're missing <cpu_usage>0.02</cpu_usage> - maybe it needs that tag as well.

edit 2: with a max_concurrent of 4 you are limiting to 2 tasks on GPU plus 2 tasks on CPU (provided enough GPU work else more CPU tasks can run), is that what you want?

The max_concurrent line is (in practice) optional - I'd leave it out completely when using app_config.xml for this purpose.

Other things to check:
1) That the file is properly named app_config.xml, and hasn't been turned into app_config.xml.txt by your editor.
2) That you've put it correctly in the project directory.

@ skildude - I refer you to http://boinc.berkeley.edu/dev/forum_thread.php?id=8332

nice


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 1361078 · Report as offensive
Alex2
Volunteer tester

Send message
Joined: 2 Nov 12
Posts: 24
Credit: 11,798,226
RAC: 0
Canada
Message 1361081 - Posted: 25 Apr 2013, 15:35:23 UTC

THANKS ALL!
I followed all advices and made it work!

I did some testing and found that the optimal is:
On my EVGA GeForce GT630 1GB on Intel E5400 2.7 (2):
3 tasks on GPU + 2 on CPU: 92% GPU load, 800mbGPU used 69C
From initial:
1 tasks on GPU + 2 on CPU: 73% GPU load 450mbGPU used

With:
<app_config>

<app>
<name>setiathome_enhanced</name>
<max_concurrent>5</max_concurrent>
<gpu_versions>
<gpu_usage>0.33</gpu_usage>
<cpu_usage>0.2</cpu_usage>
</gpu_versions>
</app>

<app>
<name>astropulse_v6</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>0.33</gpu_usage>
<cpu_usage>0.2</cpu_usage>
</gpu_versions>
</app>

</app_config>
ID: 1361081 · Report as offensive
Profile Tylendol

Send message
Joined: 8 Nov 11
Posts: 4
Credit: 6,368,471
RAC: 12
United States
Message 1361523 - Posted: 26 Apr 2013, 17:32:58 UTC - in response to Message 1361081.  

Hey All...

After a lot of hair pulling, and article searching - I followed the example below, and got my system working also; but, am wondering if I should retune for the settings for my system? Could someone please advise me on what might be good settings to use?

I'm running GPUGRID, MilkyWay, SETI@HOME, and World Community Grid. SETI@HOME was the only one giving me fits, and the only one that I tuned using the app_config with the settings; but, I think I could probably tune it slightly differently, as I have the GeForce GTX 690, which is a dual-GPU card, and was causing the cuda_fermi to have fits before the tuning.

It only appears to run a single task at a time; but, it doesn't give Computation Errors anymore though. I had also tried the Environment variable tweak listed in another thread.

I am running the new client also (7.0.64). Any thoughts/suggestions on more efficient running of the WUs would be appreciated.

Thanks!
Paul


THANKS ALL!
I followed all advices and made it work!

I did some testing and found that the optimal is:
On my EVGA GeForce GT630 1GB on Intel E5400 2.7 (2):
3 tasks on GPU + 2 on CPU: 92% GPU load, 800mbGPU used 69C
From initial:
1 tasks on GPU + 2 on CPU: 73% GPU load 450mbGPU used

With:
<app_config>

<app>
<name>setiathome_enhanced</name>
<max_concurrent>5</max_concurrent>
<gpu_versions>
<gpu_usage>0.33</gpu_usage>
<cpu_usage>0.2</cpu_usage>
</gpu_versions>
</app>

<app>
<name>astropulse_v6</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>0.33</gpu_usage>
<cpu_usage>0.2</cpu_usage>
</gpu_versions>
</app>

</app_config>

ID: 1361523 · Report as offensive

Message boards : Number crunching : Multiple task per GPU


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.