Welcome to MilkyWay@home

Posts by Anthony Waters

41) Message boards : Number crunching : Temporary Availability of the ATI application through BOINC (Message 30591)
Posted 12 Sep 2009 by Anthony Waters
Post:
There were no server side issues deploying the 32 bit Windows application therefore the 64 bit Windows application has also been deployed.
42) Message boards : Number crunching : Temporary Availability of the ATI application through BOINC (Message 30583)
Posted 12 Sep 2009 by Anthony Waters
Post:
It is live now, I personally don't have any way to verify if it will work so please report any issues and include the BOINC version, Catalyst Version, Operating System, and what video card.

Edit: It will appear as version 19 and is only available for 32 bit Windows and uses version 0.19g SSE2 from Cluster Physik
43) Message boards : Application Code Discussion : CUDA for Milkyway@Home (Message 30525)
Posted 12 Sep 2009 by Anthony Waters
Post:
The latest source code for CUDA is now up at http://milkyway.cs.rpi.edu/milkyway/download/code_release/mw_gpu_v.zip
44) Message boards : Number crunching : Temporary Availability of the ATI application through BOINC (Message 30501)
Posted 11 Sep 2009 by Anthony Waters
Post:
On 9/12/2009 from noon until 2pm EDT that ATI application will be available on BOINC in order to assist the BOINC developers with any issues relating to the new 6.10 client that will have ATI support.

Thank you for your cooperation during this time period.
45) Message boards : Number crunching : 3rd.in - optimized apps (Message 30002)
Posted 31 Aug 2009 by Anthony Waters
Post:
They should work together okay
46) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 30001)
Posted 31 Aug 2009 by Anthony Waters
Post:
I noticed that no progress bar is showing with the new application version from Aug 30. Everythings else - credit, runtime etc - is the same as with the old version.

Anyone else noticing the same behaviour?


Yes, I've uploaded a new version about an hour ago to fix the issue, thanks for reporting this.
47) Message boards : Number crunching : cannot identify GPU task from CPU task (Message 29922)
Posted 30 Aug 2009 by Anthony Waters
Post:
I have a new version ready, after the weekend I'll put it up on BOINC.
48) Message boards : Number crunching : 6.10.1 Posted. (Message 29883)
Posted 28 Aug 2009 by Anthony Waters
Post:
I've sent an email to the boinc_projects mailing list about the issue of not receiving CPU work, referenced in the thread Ice posted earlier. The response that I received is as follows

"If a client is requesting only GPU jobs at a point where it has no CPU jobs,
that's a client bug. Please ask them to set the <work_fetch_debug> flag in their cc_config.xml, and send me the resulting message log."

If possible attach a log of this happening so it can be resolved.
49) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29829)
Posted 28 Aug 2009 by Anthony Waters
Post:
Ok, after few restarts it works!!!!

But I install driver 190.62, BOINC 6.10.1 and detached + atached to projest and set only GPU...

It works witch AQUA@HOME CPU.

Win7 64 bit.

On GTX260 (625Mhz GPU 1348 Shader) = 11 m. 25 s. = 685s. 74.24 credits so 1 credit in 9.23s.

GPUGRID pays better..... (1 credit at 4-7sec.)

But MW app is "young" and I hope soon it will be improved to have better performance :)


GPUGRID uses single precision math which is 8 times faster than the double precision math that Milkyway@Home requires. For reference, the single precision version of the Milkyway@Home CUDA app can do a WU in 15 seconds, while the double precision version takes upwards around 85 seconds. Granted the WU were smaller than the ones on BOINC, but it clearly shows the performance between single and double precision.
50) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29828)
Posted 28 Aug 2009 by Anthony Waters
Post:
When my CPU (i7) is working full with other BOINC projects, calculation time for Milkyway/CUDA is 9.5 minutes. When my CPU is idle, calculation time is 5.5 minutes. Close to two times difference !

Edit: confirmed on my second computer.

The GTX 285 that I have takes about 5:24 per WU with no load on the CPU and leaving the computer idle, this is with the WU that begin with gs_s222_3s.

@Anthony:

I sent you a solution to this problem by PM!


Thanks a lot, I'm implementing it now so the new version should be up within the hour.

Edit: The newest version is now on BOINC, the completion times should be more stable around 5-6 minutes, thanks to Cluster Physik.
51) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29814)
Posted 27 Aug 2009 by Anthony Waters
Post:
The GTX 285 that I have takes about 5:24 per WU with no load on the CPU and leaving the computer idle, this is with the WU that begin with gs_s222_3s.
52) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29797)
Posted 27 Aug 2009 by Anthony Waters
Post:
Anthony, I found something wrong. When my CPU (i7) is working full with other BOINC projects, calculation time for Milkyway/CUDA is 9.5 minutes. When my CPU is idle, calculation time is 5.5 minutes. Close to two times difference !

Edit: confirmed on my second computer.


The estimated calculation time? If so I'm not sure how that is calculated, the progress bar is the best estimate for how things are progressing.
53) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29793)
Posted 27 Aug 2009 by Anthony Waters
Post:
I've made a post to the boinc_projects mailing list about the issue.
54) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29791)
Posted 27 Aug 2009 by Anthony Waters
Post:
Thank You for the reply. I re-read the first post/message and found the
preference for the project. I have the GPU selected as NO.

Use GPUs for Computation? no
Use CPU for Computation? yes

The problem is that it does not work. I ran update for the project and it still trys to get work for GPU and does not try to get CPU work. So that means I will run out of work very shortly.

Thanks again. Jim


Is the client out of CPU work?
55) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29785)
Posted 27 Aug 2009 by Anthony Waters
Post:
:-( My new gpu is a gts 250 . it looked good in comparison with the gtx 260 in gpu grid's chart, close in bang for half the cost. almost bought a 260 today (cheaper now)but ended up getting a hub, some mice, keyboards, cables, kvm etc. woulda put it in a 64 bit linux box though (too cheap to buy windoze, can't stand it nywayz) as ThierryH says tho, #1 is best 4 Me cuz i don't need to use the pc.

why the 32 bit BOINC ?
my server2003 64 bit 'doze wont run that. (disingenuous (ungenuine) of course ;-)
is there a 64bit 'nix app in the pipeline ?



Server 2003 64 bit should be able to execute the application, my personal setup is using Windows XP x64 Professional Edition (which is based off of Server 2003) with a 32 bit BOINC install and it receives the 32 bit GPU application and the 64 bit CPU applications.

The application keeps segfaulting when executed through BOINC on Linux/GNU. It successfully runs as a standalone application, but once BOINC tries to execute it, it fails. Please see here [1] for more information.

[1] http://forums.nvidia.com/index.php?showtopic=105178
56) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29773)
Posted 27 Aug 2009 by Anthony Waters
Post:
Not sure where to put this. Not cuda related per say, I have only been getting 5 wu at a time today. Did this change from 6, or just my luck?


The server side software was upgraded recently so it might have been that, I'm not well versed in the workings of BOINC to be able to answer that question correctly.
57) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29771)
Posted 27 Aug 2009 by Anthony Waters
Post:
I'm not quite sure how BOINC decides which platform to request tasks for (GPU or CPU) but I will try BOINC 6.10 over the next day to see if that is the source of the issue.

I tried to downgrade to 6.6.36, but got an error and the BOINC manager wouldn't run, so had to go back to 6.10.1



I sent you a PM based on my analysis, if other users start reporting similar issues I'll post a public message without any private information.
58) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29768)
Posted 27 Aug 2009 by Anthony Waters
Post:
I'm not quite sure how BOINC decides which platform to request tasks for (GPU or CPU) but I will try BOINC 6.10 over the next day to see if that is the source of the issue.

Edit:
Just saw your update with respect to your CUDA card, the server is set to reject sending the GPU application to users without a compatible card. It is possible that I messed up that part of the source code. Since I do have an 8800 GTX as well I'll put that in tomorrow afternoon to see if I can reproduce the situation.
59) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29765)
Posted 27 Aug 2009 by Anthony Waters
Post:
I've set GPU to no, but it it's trying for it anyway, and I'm not getting any work at all:

Use GPUs for Computation? no
Use CPU for Computation? yes


27/08/2009 01:03:07 Milkyway@home Requesting new tasks for GPU
27/08/2009 01:03:13 Milkyway@home Scheduler request completed: got 0 new tasks
27/08/2009 01:03:13 Milkyway@home Message from server: No work sent

I'm using BOINC 6.10.1



Does this still happen with subsequent scheduler updates? When I had the Use GPUs for Computation set to no it would return a message saying something like "Preferences set to not accept GPU work, but work is available". Sometimes I would receive the same message "Scheduler request completed: got 0 new tasks" but once the next scheduler update came it disappeared and switched back to saying "Requesting new tasks for CPU".

Edit:
With BOINC 6.6.36 I see something like so

(no to GPU computation, no to CPU computation)
8/26/2009 8:22:12 PM Milkyway@home Resetting project
8/26/2009 8:22:17 PM Milkyway@home Sending scheduler request: To fetch work.
8/26/2009 8:22:17 PM Milkyway@home Requesting new tasks for GPU
8/26/2009 8:22:22 PM Milkyway@home Scheduler request completed: got 0 new tasks
8/26/2009 8:22:22 PM Milkyway@home Message from server: Not sending work - last request too recent: 15 sec
8/26/2009 8:23:27 PM Milkyway@home Sending scheduler request: To fetch work.
8/26/2009 8:23:27 PM Milkyway@home Requesting new tasks for GPU
8/26/2009 8:23:32 PM Milkyway@home Scheduler request completed: got 0 new tasks
8/26/2009 8:23:32 PM Milkyway@home Message from server: No work sent
8/26/2009 8:23:32 PM Milkyway@home Message from server: GPU jobs are available, but your preferences are set to not accept them
8/26/2009 8:24:37 PM Milkyway@home Sending scheduler request: To fetch work.
8/26/2009 8:24:37 PM Milkyway@home Requesting new tasks for CPU
8/26/2009 8:24:42 PM Milkyway@home Scheduler request completed: got 0 new tasks
8/26/2009 8:24:42 PM Milkyway@home Message from server: No work sent
8/26/2009 8:24:42 PM Milkyway@home Message from server: CPU jobs are available, but your preferences are set to not accept them
(no to gpu computation, yes to cpu computation)
8/26/2009 8:25:47 PM Milkyway@home Sending scheduler request: To fetch work.
8/26/2009 8:25:47 PM Milkyway@home Requesting new tasks for GPU
8/26/2009 8:25:52 PM Milkyway@home Scheduler request completed: got 0 new tasks
8/26/2009 8:25:52 PM Milkyway@home Message from server: No work sent
8/26/2009 8:25:52 PM Milkyway@home Message from server: GPU jobs are available, but your preferences are set to not accept them
8/26/2009 8:26:57 PM Milkyway@home Sending scheduler request: To fetch work.
8/26/2009 8:26:57 PM Milkyway@home Requesting new tasks for GPU
8/26/2009 8:27:02 PM Milkyway@home Scheduler request completed: got 0 new tasks
8/26/2009 8:27:02 PM Milkyway@home Message from server: No work sent
8/26/2009 8:27:02 PM Milkyway@home Message from server: GPU jobs are available, but your preferences are set to not accept them
8/26/2009 8:28:07 PM Milkyway@home Sending scheduler request: To fetch work.
8/26/2009 8:28:07 PM Milkyway@home Requesting new tasks for CPU
8/26/2009 8:28:12 PM Milkyway@home Scheduler request completed: got 2 new tasks
8/26/2009 8:28:14 PM Milkyway@home Started download of milkyway_0.19_windows_x86_64.exe
8/26/2009 8:28:14 PM Milkyway@home Started download of ps_s222_3s_02w_03r_21_search_parameters_3880771_1251332799
8/26/2009 8:28:15 PM Milkyway@home Finished download of ps_s222_3s_02w_03r_21_search_parameters_3880771_1251332799
8/26/2009 8:28:15 PM Milkyway@home Started download of ps_s222_3s_02w_03r_21_search_parameters_3880772_1251332799
8/26/2009 8:28:17 PM Milkyway@home Finished download of milkyway_0.19_windows_x86_64.exe
8/26/2009 8:28:17 PM Milkyway@home Finished download of ps_s222_3s_02w_03r_21_search_parameters_3880772_1251332799
8/26/2009 8:28:18 PM Milkyway@home Starting ps_s222_3s_02w_03r_21_3880771_1251332799_0
8/26/2009 8:28:18 PM Milkyway@home Starting task ps_s222_3s_02w_03r_21_3880771_1251332799_0 using milkyway version 19
8/26/2009 8:28:18 PM Milkyway@home Starting ps_s222_3s_02w_03r_21_3880772_1251332799_0
8/26/2009 8:28:18 PM Milkyway@home Starting task ps_s222_3s_02w_03r_21_3880772_1251332799_0 using milkyway version 19
8/26/2009 8:28:26 PM Suspending computation - user request
60) Message boards : Number crunching : CUDA Application for 32 bit Windows (Message 29762)
Posted 26 Aug 2009 by Anthony Waters
Post:
A new preference has been added to the Milkyway@Home preferences page that specifies whether the project is allowed to use your GPU for computation, this has to be enabled in order to receive work from the CUDA application.



how about a new preference for not running CPU work for any of us that want to run GPU only?


I've added it to the project specific preferences page and I'm almost 100% positive I've made it so that the default is to use the CPU.


Previous 20 · Next 20

©2024 Astroinformatics Group