Hello everyone,

We decided to once again provide support for the milkyway_nbody multi-threaded application. If you discover any issues with the new application, please do not hesitate to contact us so that we may expeditiously resolve them. Thank you all for your continued support.

-Eric

I request that you do one or the other, but not both, for the reasons previously discussed concerning the BOINC scheduler.
(I don't see any way to choose anything yet.)

I have tried 2 of the new jobs, both went off the rails
Am trying third one then will give up and do other projects for a while

---

Could you please clarify what you meant by "went off the rails?" Are they spitting out errors? Is the run-time too long?

Run time for me appears to be never-ending. After a while the percentage done stops advancing and the estimated time remaining starts climbing. Runs that were supposed to finish in 8 hours on 8 CPUs are still running after 2 days with over 1 day estimated time to completion. I've aborted anything estimated at over 5 hours to see if the shorter ones will complete.

One work unit estimated at under 4 hours is still running after 7:17 hours and stuck at 19.729% completed, estimated 1d 05:31 to completion (and climbing).

As far as I can tell my system has not completed a single non-GPU work unit since I restarted processing a week ago.

I have every CPU task finish without problems. CPU tasks seem to switch between multiple single processor and one multi processors without any problems at all on all five workstations as they progress down the task list.

for me the multi-threaded jobs says it will take 1-3 hours with 7 CPUs...however they have a real hard time finishing.. current job has been running 3:44...with an estimated 3:26 to go...however the estimated time is counting up instead of down. I dont have anything else running on my computer except for this browser....I have had to abort a ton of jobs as they pass their deadline. lots of wasted CPU it seems...

From what I'm seeing in my BOINC manager, the multi-threaded nbody application takes about 4 hours to complete on 8 CPUs. The main reason why these simulations take so long is due to two factors:
- We are using 40,000 bodies instead of 20,000. This is the minimum number of bodies we require to ensure the random seed does not drastically affect the final state of the nbody simulation. Our N-body algorithm is O(n log n), which means this change makes runs take 2.14 times longer than before.
- MilkyWay@home is optimizing to ultradense cores about 50% of the time. In order to accurately run a dense collection of bodies in an N-body simulation, you need to have a smaller timestep, otherwise, the collection of bodies explodes outwards. The denser the galaxy, the smaller the timestep needs to be. These dense progenitors take about 4 times longer to run than normal, and when MilkyWay@home optimizes to a dense progenitor, we end up with a population of parameters that each take several hours to compute.

While we cannot improve the number of bodies, we are working on removing runs that converge to these heavily cored progenitors. We apologize for the inconvenience. Thank you for your patience.

-Eric

I am running W10,. If the multi thread tasks are the ones using 6 cpus I am having trouble. The tasks run very slowly, 3% after two days. They also lock up the BOINC software, other tasks do not run or download. When I abort all the 6 cpu tasks the other projects immediately download and run normally.

I've just aborted a work unit. 6+ hours CPU, only 8% complete, deadline later today. Your work units normally execute in a few minutes on here, (4GHz i7 + GPU). All other units aborted also before they start, NNT set. Something is wrong now.

Eric,
My multi-thread work unit runs slow like most of the cases listed here. I noticed on the windows "task manager" (press Ctrl-Alt-Del), on the performance tab, that the work units are only using less then 20% of the CPU time. It is not a setting in my app. All of the other projects use 80-100% of the CPU time.
Michael

I am running W10,. If the multi thread tasks are the ones using 6 cpus I am having trouble. The tasks run very slowly, 3% after two days.

I am running 6 cores on Win7 64-bit. On an i7-4771 they are taking about 4 to 6 hours now (one is estimating 8 hours), but completing OK at this point.

Is there a fix for the 6CPU task problem? I just aborted 19 tasks so the other projects could run. I may have to drop MW and look for another project. Is there a way to download just the single CPU tasks?

Is there a fix for the 6CPU task problem?

They work for me.
https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=737912&offset=0&show_names=0&state=4&appid=
Are you sure it is not your AV interfering?

I'm in the same boat. it crunches the numbers then gets stuck at anywhere from 32.882% to 99.577% it stops there and time remaining starts climbing. I have Windows 10 so I do a restart when I see this and when BOINC comes back the stuck N-Body item is no longer there and a new one has started

When you look up the work unit that gets stuck and disappears, does it say it was completed or does it log it as a computation error?

Seems to be incompatible with using less than 100% of CPU time, stops processing in that case after short time (around 1 minute). Need that to keep my laptop at reasonable noise level.

---

Hi Eric and everyone,

We had some bad experiences joining gridpool with issues on getting paid our due coins daily. We kept loosing all daily earnings for days at a time so I'm back to milkyway (OFF gridpool). Milkyway is the BEST!!!

Due to low light and solar production through the short days I have turned off your GPU tasks and selected only nbody cpu tasks to do for now.

Nbody I run at 76% CPU. I have noticed nbody are touchy with automatic windows 10 updates and updating GPU drivers, causing tasks to slow to a crawl or stop all together. I selected within internet properties 'metered internet connection' so I have a chance to suspend milkyway tasks before any updating. (No automatic updates with metered windows 10 internet connection). Windows asks permission before downloading and updating with a metered internet connection giving me the chance to suspend tasks before updates. That seems to stop all problems with nbody tasks for me.

I hope this makes sense. My brain hurts right now from so much pain in my face. Not thinking as clearly as i'd like.

Sunny regards,

---

100% POWERED BY SOLAR, SUNNY REGARDS

I also think it's absolutely essential we "terminate" operation of every application within windows 10 not essential to BOINC and our GPU.

There are so many trash apps now in windows 10 and many will reload even when uninstalled. I now leave them in but terminate them so there is less going on in the background. I also go through every app permissions in PRIVACY and turn them off.

I like to use the Resource Monitor within Windows Administrative Tools to monitor CPU usage so I can see what is running and if a heartbeat is getting out of hand. Great tool I keep pinned to my taskbar. I've seen heartbeats crash nbody tasks. Some temperature monitor apps really spike the CPU usage every second leaving what looks like a heartbeat in the CPU graph. Bad for milky way tasks when it gets extreme.

I am sure you old timers know all this. It's just for any new bee like me that has problems. It really helps. Reduce background apps!!! Your CPU will like you;-)

---

100% POWERED BY SOLAR, SUNNY REGARDS