Welcome to MilkyWay@home

Multi-threaded N-body is back


Advanced search

Message boards : News : Multi-threaded N-body is back
Message board moderation

To post messages, you must log in.

AuthorMessage
Eric Mendelsohn
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 21 Aug 18
Posts: 28
Credit: 3,999,229
RAC: 18,332
3 million credit badge1 year member badge
Message 69049 - Posted: 17 Sep 2019, 19:56:29 UTC

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
ID: 69049 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jim1348

Send message
Joined: 9 Jul 17
Posts: 59
Credit: 7,233,199
RAC: 12,713
5 million credit badge2 year member badge
Message 69054 - Posted: 18 Sep 2019, 19:40:07 UTC - in response to Message 69049.  
Last modified: 18 Sep 2019, 19:40:16 UTC

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.)
ID: 69054 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Phoenix
Avatar

Send message
Joined: 5 Feb 11
Posts: 3
Credit: 1,465,713
RAC: 582
1 million credit badge8 year member badge
Message 69107 - Posted: 22 Sep 2019, 19:52:01 UTC

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
ID: 69107 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Eric Mendelsohn
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 21 Aug 18
Posts: 28
Credit: 3,999,229
RAC: 18,332
3 million credit badge1 year member badge
Message 69119 - Posted: 24 Sep 2019, 17:53:44 UTC - in response to Message 69107.  

Could you please clarify what you meant by "went off the rails?" Are they spitting out errors? Is the run-time too long?
ID: 69119 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Bam

Send message
Joined: 2 Dec 16
Posts: 2
Credit: 35,566,818
RAC: 23,958
30 million credit badge3 year member badge
Message 69178 - Posted: 19 Oct 2019, 5:06:16 UTC - in response to Message 69119.  

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.
ID: 69178 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Bam

Send message
Joined: 2 Dec 16
Posts: 2
Credit: 35,566,818
RAC: 23,958
30 million credit badge3 year member badge
Message 69179 - Posted: 20 Oct 2019, 2:43:01 UTC - in response to Message 69178.  

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.
ID: 69179 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profileearthbilly

Send message
Joined: 1 Dec 18
Posts: 1
Credit: 99,235,594
RAC: 215,275
50 million credit badge1 year member badge
Message 69180 - Posted: 21 Oct 2019, 21:22:18 UTC

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.
ID: 69180 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Ken Penland

Send message
Joined: 18 Jun 19
Posts: 1
Credit: 9,504,171
RAC: 48,952
5 million credit badge
Message 69284 - Posted: 22 Nov 2019, 12:28:49 UTC

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...
ID: 69284 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Eric Mendelsohn
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 21 Aug 18
Posts: 28
Credit: 3,999,229
RAC: 18,332
3 million credit badge1 year member badge
Message 69310 - Posted: 26 Nov 2019, 2:18:26 UTC - in response to Message 69284.  

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
ID: 69310 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Steven Case

Send message
Joined: 15 Dec 10
Posts: 2
Credit: 126,800,525
RAC: 1,908
100 million credit badge8 year member badge
Message 69315 - Posted: 28 Nov 2019, 14:22:16 UTC - in response to Message 69049.  

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.
ID: 69315 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profileadrianxw

Send message
Joined: 25 May 14
Posts: 25
Credit: 45,458,504
RAC: 11,497
30 million credit badge5 year member badge
Message 69317 - Posted: 29 Nov 2019, 9:11:39 UTC

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.
ID: 69317 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : News : Multi-threaded N-body is back

©2019 Astroinformatics Group