Posts by _heinz
log in
1) Message boards : News : GPU Issues Mega Thread (Message 65092)
Posted 1 Sep 2016 by _heinz
Thanks for all the feedback so far :)
@_heinz
Your Titans can do quite well on Milkyway. If you want to run it a little, you have to set in the driver that double precision is used. And you have to use the app_config file to run 6 to 8 workunits in parallel per card to get them fully loaded.


Really it run 8 per device in about ~4min
2) Message boards : News : GPU Issues Mega Thread (Message 65085)
Posted 31 Aug 2016 by _heinz
I run 3 Computers with NVIDIA Graphicadapers, till now no problem with the Software here.

30.08.2016 20:49:42 | | CUDA: NVIDIA GPU 0: GeForce GT 540M (driver version 368.81, CUDA version 8.0, compute capability 2.1, 1024MB, 970MB available, 258 GFLOPS peak)
30.08.2016 20:49:42 | | OpenCL: NVIDIA GPU 0: GeForce GT 540M (driver version 368.81, device version OpenCL 1.1 CUDA, 1024MB, 970MB available, 258 GFLOPS peak)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30.08.2016 23:03:12 | | CUDA: NVIDIA GPU 0: GeForce GT 650M (driver version 362.61, CUDA version 8.0, compute capability 3.0, 2048MB, 1681MB available, 730 GFLOPS peak)
30.08.2016 23:03:12 | | OpenCL: NVIDIA GPU 0: GeForce GT 650M (driver version 362.61, device version OpenCL 1.2 CUDA, 2048MB, 1681MB available, 730 GFLOPS peak)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
31.08.2016 21:19:06 | | CUDA: NVIDIA GPU 0: GeForce GTX TITAN (driver version 372.54, CUDA version 8.0, compute capability 3.5, 4096MB, 4010MB available, 4989 GFLOPS peak)
31.08.2016 21:19:06 | | CUDA: NVIDIA GPU 1: GeForce GTX TITAN (driver version 372.54, CUDA version 8.0, compute capability 3.5, 4096MB, 4010MB available, 4989 GFLOPS peak)
31.08.2016 21:19:06 | | CUDA: NVIDIA GPU 2: GeForce GTX TITAN (driver version 372.54, CUDA version 8.0, compute capability 3.5, 4096MB, 4010MB available, 4989 GFLOPS peak)
31.08.2016 21:19:06 | | OpenCL: NVIDIA GPU 0: GeForce GTX TITAN (driver version 372.54, device version OpenCL 1.2 CUDA, 6144MB, 4010MB available, 4989 GFLOPS peak)
31.08.2016 21:19:06 | | OpenCL: NVIDIA GPU 1: GeForce GTX TITAN (driver version 372.54, device version OpenCL 1.2 CUDA, 6144MB, 4010MB available, 4989 GFLOPS peak)
31.08.2016 21:19:06 | | OpenCL: NVIDIA GPU 2: GeForce GTX TITAN (driver version 372.54, device version OpenCL 1.2 CUDA, 6144MB, 4010MB available, 4989 GFLOPS peak)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3) Message boards : Number crunching : app_info.xml Help (Message 65082)
Posted 30 Aug 2016 by _heinz
This works for me. Core I3, Nvidia GT540M Win7 x64
You had to download the different exe files from milkyway downlodsite
milkyway_nbody_1.62_windows_x86_64.exe
milkyway_1.36_windows_x86_64.exe
milkyway_1.36_windows_x86_64__opencl_nvidia_101.exe
milkyway_separation__modified_fit_1.36_windows_x86_64.exe
milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_nvidia_101.exe

no cmdline is used for finetuning (I don' know the parameters)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<app_info>
<app>
<name>milkyway_nbody</name>
<user_friendly_name>Milkyway N-Body Sim.</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_1.62_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>162</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>milkyway_nbody_1.62_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway</name>
<user_friendly_name>Milkyway</user_friendly_name>
</app>
<file_info>
<name>milkyway_1.36_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>milkyway_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_1.36_windows_x86_64__opencl_nvidia_101.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>opencl_nvidia_101</plan_class>
<cmdline></cmdline>
<coproc>
<type>NVIDIA</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>milkyway_1.36_windows_x86_64__opencl_nvidia_101.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_separation__modified_fit</name>
<user_friendly_name>Milkyway Sep. (Mod. Fit)</user_friendly_name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_nvidia_101.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>opencl_nvidia_101</plan_class>
<cmdline></cmdline>
<coproc>
<type>NVIDIA</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_nvidia_101.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
4) Message boards : Number crunching : app_info.xml Help (Message 65079)
Posted 30 Aug 2016 by _heinz
Anybody here who has a app_info for NVIDIA ?
5) Message boards : Number crunching : Milkyway@Home Separation (Modified Fit) v1.28 (opencl_nvidia) crashes on Titan (Message 61514)
Posted 15 Apr 2014 by _heinz
I use [3] NVIDIA GeForce GTX TITAN (4095MB) driver: 335.23 OpenCL: 1.01
and the app crashes continous for every wu.
Have a look here:
my wus
my hostid=571719
Any idea what I can do ?
Or a bug ?

Regards heinz
6) Message boards : Number crunching : GPU Requirements [OLD] (Message 42963)
Posted 19 Oct 2010 by _heinz
Hi Anthony,
You can update your list:
GTX480
GTX470
GTX460
are working with app MW_0.24_CUDA
Thanks to Crunch3r, who compiled it.
heinz
7) Message boards : Number crunching : 2 x GTX470 worked with milkyway 0.24 (cuda23) (Message 42937)
Posted 18 Oct 2010 by _heinz
Hi,
I installed MW_024_CUDA downloaded from Crunch3r's website.
milkyway_windows_intelx86__cuda23.exe
and it runs without any problems on my two GTX470
I run 2 wu's per GPU using <count>0.48</count>
if someone will have a look at my host 51270
Thanks to Crunch3r compiling this app.

heinz
8) Message boards : Number crunching : de_14_3s_free_5... shows no progress on 0.20 CPU client (Message 37301)
Posted 13 Mar 2010 by _heinz
The same for me... resetted project...
nothing helped...
9) Message boards : Number crunching : whats up wiith these apps ? (Message 37300)
Posted 13 Mar 2010 by _heinz
Hi,
on my system HD3870 Ultimate these wu's are hanging around and no progress is shown, they don't start..
I switched to one per GPU, but did not help for me.
Restart of boinc or the complete machine did not help.
So I resetted the project...
Its pitty...
10) Message boards : Number crunching : suspend (Message 37121)
Posted 10 Mar 2010 by _heinz
my preferences was changed....
uhhh..
now it runs again
11) Message boards : Number crunching : suspend (Message 37119)
Posted 10 Mar 2010 by _heinz
any ideas why my wu's suddenly are in suspend state after starting ?
last night my machine made some automatic update, now milkyway app wu's are going in suspend mode.
I have still docking running on cpu with them together.
I did restart boinc already but it did not help.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
any ideas ?
12) Message boards : Number crunching : CUDA and ION (Message 33780)
Posted 26 Nov 2009 by _heinz
thanks crunch3r,
thats it, no double precision
13) Message boards : Number crunching : CUDA and ION (Message 33775)
Posted 26 Nov 2009 by _heinz
this machine R3600 has the ION cuda Platform.
I can run seti_cuda, collatz_cuda, but milkyway did not download the cuda app for this machine.
I run now astronomy_020_SSE3, but this is for cpu.
In my preferences I set both work for gpu and work for cpu.
Any hints to run the cuda app are welcome.
14) Message boards : Number crunching : astronomy_020.ATI_x64 problems (Message 31753)
Posted 30 Sep 2009 by _heinz
15) Message boards : Number crunching : HD5870 (Message 31741)
Posted 30 Sep 2009 by _heinz
wait a bit and the 5870 X2 is available :-)
16) Message boards : Number crunching : astronomy_020.ATI_x64 problems (Message 31740)
Posted 30 Sep 2009 by _heinz
Hi,
thank you all for answering my questions :-)

After running 3 instances for two days it shows some crashs,
I decided to run now still 2 instances.
The 3870 runs with a slight ocing
( GPU core clock: 795 MHz, memory clock: 1126 MHz )
and temperatures ~60-65 grad celsius.
I switched the two 20cm fans of the case on now. Will see of the app is now more stable.
The machine runs under full load 99-100% cpu usage an all 8 cores with seti AKv8.
Normally it is not necessary to switch the 2 fans on, but then I got 70 - 78 grad celsius on the GPU (although this is already a good value)
17) Message boards : Number crunching : astronomy_020.ATI_x64 problems (Message 31670)
Posted 28 Sep 2009 by _heinz
Hi,
what must I do if I want to run 8 cpu tasks additional to the 3 GPU tasks i have now ?
<app_version>
<app_name>milkyway</app_name>
<version_num>20</version_num>
<flops>1.0e11</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<coproc>
<type>ATI</type>
<count>0.33</count>
</coproc>
<cmdline>w1.2</cmdline>
<file_ref>
<file_name>astronomy_0.20_ATI_x64.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>brook64.dll</file_name>
</file_ref>
</app_version>
-----------------------------
any hints are welcome
18) Message boards : Number crunching : astronomy_020.ATI_x64 problems (Message 31573)
Posted 26 Sep 2009 by _heinz
its the GDDR4 model
her you can have a look at CCC
hd3870_600MHz
hd3870_766MHz

:-)
19) Message boards : Number crunching : astronomy_020.ATI_x64 problems (Message 31522)
Posted 25 Sep 2009 by _heinz
if I look at Catalyst Control Center lowest possible memory frequency is 1126 highest 1387

I can not reduce it lower than 1387, thats factory standard
or do I missing something ?
20) Message boards : Number crunching : astronomy_020.ATI_x64 problems (Message 31520)
Posted 25 Sep 2009 by _heinz
[quote]


Summed up, I would suggest that you try these settings:

&lt;coproc&gt; &lt;type&gt;ATI&lt;/type&gt; &lt;count&gt;0.5&lt;/count&gt; &lt;/coproc&gt; &lt;cmdline&gt;w1.15&lt;/cmdline&gt;


To save a a bit on the power consumption, you can reduce the memory frequency, as MW doesn't use a lot. You have to see how important this aspect is for you, but going down to 600MHz or so shouldn't show much of a difference to the runtimes. When you go further to let's say 300MHz (if your card can run that stable), you will start to loose a few seconds calculation time. But you could compensate that with a raised GPU core clock of course ;)

Thank you Custer Physik
tried above settings as you recommended.
600MHZ elapsed 5:26
776MHz elapsed 4:23
both when 2 wu's are running on GPU.
GPU temp shows now 75 grd celsius.
running now <cmdline>w1.2</cmdline>
cpu usage is now 0,19% till 0,39% very low, mostly on CPU7 Node 0
with w1.2 the cpu usage is going against zero, really great sucess
the machine shows 0 or 1% cpu usage !!
very impressive :-)


Next 20

Main page · Your account · Message boards


Copyright © 2017 AstroInformatics Group