Welcome to MilkyWay@home

Milkyway@Home doesn't uses all GPU

Message boards : Number crunching : Milkyway@Home doesn't uses all GPU
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Chase Tarson

Send message
Joined: 14 Jun 12
Posts: 13
Credit: 2,295,346
RAC: 0
Message 55124 - Posted: 14 Jul 2012, 5:30:47 UTC

For some reason, Milkyway@home only uses around 50% to 70% of my GPU but, why doesn't it use all 100% percent of it?
ID: 55124 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile mikey
Avatar

Send message
Joined: 8 May 09
Posts: 3321
Credit: 520,521,728
RAC: 27,198
Message 55127 - Posted: 14 Jul 2012, 11:44:16 UTC - in response to Message 55124.  

For some reason, Milkyway@home only uses around 50% to 70% of my GPU but, why doesn't it use all 100% percent of it?


Because using 100% would leave your pc unusable for anything else. Some projects do use more than just a little bit and the Nvidia gpu's tend to use alot more of the gpu then the AMD gpu's do, but there are alot more AMD gpu's out there.
ID: 55127 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Link
Avatar

Send message
Joined: 19 Jul 10
Posts: 594
Credit: 18,961,543
RAC: 5,497
Message 55128 - Posted: 14 Jul 2012, 12:35:18 UTC - in response to Message 55124.  

You can try to adjust it with the cmd parameters, either by using an app_info file or by changing the preferences over the webside. All needed information can be found in the Separation updated to 1.00 thread.

I'd go with the app_info, that way you can run 2 WUs at once. I run my HD3850 at 98-99% and have no noteworthy performance issues except for if I want to watch HD movies.
ID: 55128 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Chase Tarson

Send message
Joined: 14 Jun 12
Posts: 13
Credit: 2,295,346
RAC: 0
Message 55129 - Posted: 14 Jul 2012, 14:02:03 UTC

How would I go about doing 2 at a time with the app_info?
ID: 55129 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
swiftmallard
Avatar

Send message
Joined: 18 Jul 09
Posts: 300
Credit: 303,562,776
RAC: 0
Message 55131 - Posted: 14 Jul 2012, 14:26:37 UTC

This one works well for me:


<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>102</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>ati14ati</plan_class>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<cmdline>--gpu-target-frequency 10 --gpu-disable-checkpointing</cmdline>
<file_ref>
<file_name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>


Just paste it into your projects folder and restart Boinc
ID: 55131 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
frei74

Send message
Joined: 19 Nov 11
Posts: 2
Credit: 155,106
RAC: 0
Message 55241 - Posted: 27 Jul 2012, 1:24:34 UTC - in response to Message 55131.  

This one works well for me:


<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>102</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>ati14ati</plan_class>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<cmdline>--gpu-target-frequency 10 --gpu-disable-checkpointing</cmdline>
<file_ref>
<file_name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>


Just paste it into your projects folder and restart Boinc

How about Nvidia GPU?
ID: 55241 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Karl

Send message
Joined: 11 Feb 10
Posts: 2
Credit: 21,270,032
RAC: 1,895
Message 55409 - Posted: 23 Aug 2012, 22:15:12 UTC

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_x86_64__opencl_nvidia.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>102</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>cuda</plan_class>
<coproc>
<type>NVIDIA</type>
<count>0.5</count>
</coproc>
<cmdline>
</cmdline>
<file_ref>
<file_name>milkyway_separation_1.02_windows_x86_64__opencl_nvidia.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
ID: 55409 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile mikey
Avatar

Send message
Joined: 8 May 09
Posts: 3321
Credit: 520,521,728
RAC: 27,198
Message 55410 - Posted: 24 Aug 2012, 11:49:01 UTC - in response to Message 55409.  

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_x86_64__opencl_nvidia.exe</name>
</app_info>


IT WORKS!!! I am now crunching two units at once, THANKS!!!
ID: 55410 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Karl

Send message
Joined: 11 Feb 10
Posts: 2
Credit: 21,270,032
RAC: 1,895
Message 55413 - Posted: 25 Aug 2012, 5:30:25 UTC - in response to Message 55410.  

No problem.

You can put in 0.25 GPU and do four at a time, or 0.125 and do eight at a time, and play with the number of CPU processors also, but frankly it seems to only slow things down a bit, if anything. I am not even certain running two threads is faster per work unit than one at a time on my Nvidia card. Similarly, increasing the number of CPUs per thread seems to keep the CPUs busier, but without any increase in speed. So just keep cpu avg low ~0.05 and sign up for some other project that will use the cpus (e.g. Einstein).
ID: 55413 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile mikey
Avatar

Send message
Joined: 8 May 09
Posts: 3321
Credit: 520,521,728
RAC: 27,198
Message 55414 - Posted: 25 Aug 2012, 11:24:32 UTC - in response to Message 55413.  

No problem.

You can put in 0.25 GPU and do four at a time, or 0.125 and do eight at a time, and play with the number of CPU processors also, but frankly it seems to only slow things down a bit, if anything. I am not even certain running two threads is faster per work unit than one at a time on my Nvidia card. Similarly, increasing the number of CPUs per thread seems to keep the CPUs busier, but without any increase in speed. So just keep cpu avg low ~0.05 and sign up for some other project that will use the cpus (e.g. Einstein).


Yeah that is what I do, I do NOT crunch with both the cpu and the gpu for the same project, I always separate them.
ID: 55414 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
frei74

Send message
Joined: 19 Nov 11
Posts: 2
Credit: 155,106
RAC: 0
Message 55428 - Posted: 29 Aug 2012, 6:04:37 UTC - in response to Message 55409.  

Thanks, Karl, 4 WU on GTX 680 during ~16min!
ID: 55428 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Milkyway@Home doesn't uses all GPU

©2024 Astroinformatics Group