Welcome to MilkyWay@home

Posts by WMD

1) Message boards : News : New Poll Regarding GPU Application of N-Body (Message 71018)
Posted 23 Jul 2021 by WMD
Post:
I've been waiting for this for years! I only run MilkyWay on GPU, as the CPU is used for other things - generally, projects that don't have a GPU version. And I do have a Titan V, so, I imagine the performance will be quite good. :) The performance differential between CPU and GPU won't matter so much to me, though, since GPU is all I do here. Would just be nice to be able to contribute to both applications!

As an aside, if the workunits do take longer, it'll at least be able to help with the never-fixed problem this project has with sending workunits - namely, the one where you get 300 tasks, it runs through them all without receiving any more, and then it sits for almost 15 minutes with nothing to do (since the server has a bad setting somewhere related to intervals between sending units, and the BOINC client backs off for ~10 minutes upon hitting up against that). Was tolerable with my old video card, but when your Titan V can do 300 tasks in about 35 minutes, it becomes kind of a pain. I've set up some backup projects with a work share of 0 to keep the system busy during that time, but... when you spend the money on an FP64 card, you want to do FP64 work! :)
2) Message boards : Application Code Discussion : N-Body on GPU? (Message 68233)
Posted 8 Mar 2019 by WMD
Post:
I second this. I only run MW@H on my GPU, the CPU is reserved for WCG. And there seems to be a lot more development these days on n-body, so I assume it's more interesting to the project. I'd certainly like to contribute if such a client is feasible.
3) Message boards : News : Mac OS X Support For Separation (Message 66465)
Posted 26 May 2017 by WMD
Post:
Yay! My D700 is BACK! :)

It seems that the new work units take considerably longer to run (and have longer estimated times). Do they contain more work? (Old time: 16 seconds, new time: 66 seconds).
4) Message boards : Number crunching : Mac GPU apps - any plans? (Message 66000)
Posted 11 Dec 2016 by WMD
Post:
There used to be such apps, but I think Jake said the Mac they used for builds died. So the new versions for Mac are delayed.
5) Message boards : News : Updated Server Daemons and Libraries (Message 65370)
Posted 2 Oct 2016 by WMD
Post:
To follow up on my previous post...I have fixed my problem, sort of. It turns out that my project prefs had everything disabled except for Separation (Modified Fit). I honestly don't remember why I did that...so, I turned the basic app back on (leaving n-body off), and I began to receive some work units. At first, it seemed like I could only make that happen without my custom app_info.xml (which means Jake got it to read newer GPUs after all! :) ) but after that I put the app_info.xml back, and it's still working. Which is good, because that way I can crunch 3 WUs at a time :)

In spite of this, new WUs are still sporatic. Some updates don't give me anything, and then a minute later, I'll get a few. I'm not getting anything from Separation still.
6) Message boards : News : Updated Server Daemons and Libraries (Message 65346)
Posted 29 Sep 2016 by WMD
Post:
I'm not getting any work units either, on the Mac version. Here is a log of one attempt:

Wed Sep 28 20:17:27 2016 | Milkyway@Home | Sending scheduler request: To fetch work.
Wed Sep 28 20:17:27 2016 | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
Wed Sep 28 20:17:29 2016 | Milkyway@Home | Scheduler request completed: got 0 new tasks
Wed Sep 28 20:17:29 2016 | Milkyway@Home | No tasks sent
Wed Sep 28 20:17:29 2016 | Milkyway@Home | No tasks are available for Milkyway@Home Separation (Modified Fit)
Wed Sep 28 20:17:29 2016 | Milkyway@Home | Message from server: Your app_info.xml file doesn't have a usable version of MilkyWay@Home N-Body Simulation.
Wed Sep 28 20:17:29 2016 | Milkyway@Home | Tasks for CPU are available, but your preferences are set to not accept them
Wed Sep 28 20:17:29 2016 | Milkyway@Home | Tasks for NVIDIA GPU are available, but your preferences are set to not accept them

That error from N-Body is from my custom app_info.xml; I'm simply too lazy to fix it. ;) Otherwise I'm using the regular 1.37 binary for Mac ATI opencl. I figured maybe this was the cause, so I temporarily renamed the app_info.xml and started up without it, but this had no effect (other than removing my self-inflicted n-body error, of course).




©2021 Astroinformatics Group