Welcome to MilkyWay@home

Nbody release v1.74


Advanced search

Message boards : News : Nbody release v1.74
Message board moderation

To post messages, you must log in.

AuthorMessage
Sidd
Project developer
Project tester
Project scientist

Send message
Joined: 19 May 14
Posts: 73
Credit: 356,131
RAC: 0
100 thousand credit badge5 year member badge
Message 67949 - Posted: 19 Dec 2018, 18:52:14 UTC

Hey All,

I just released a new version of nbody, v1.74. This is a minor release which is backward compatible. Please let me know if there are any issues.

Thanks again,
Sidd
ID: 67949 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jeffery M. Thompson
Volunteer moderator
Project developer
Project tester
Project scientist
Avatar

Send message
Joined: 23 Sep 12
Posts: 156
Credit: 12,997,107
RAC: 0
10 million credit badge6 year member badge
Message 67953 - Posted: 20 Dec 2018, 2:16:08 UTC - in response to Message 67949.  

There appears to be an error in the generation of the work units associated with this release. We are working on fixing that currently I will post updates here.

Cheers,
Jeff
ID: 67953 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist

Send message
Joined: 25 Feb 13
Posts: 580
Credit: 68,641,828
RAC: 384,686
50 million credit badge6 year member badgeextraordinary contributions badge
Message 67954 - Posted: 20 Dec 2018, 3:17:03 UTC

Looks like everything is all fixed.

Give us an update if you see any issues throughout the next day or two.

Thank you for your patience,

Jake
ID: 67954 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileRichard Whitehurst

Send message
Joined: 23 Dec 13
Posts: 1
Credit: 27,638,990
RAC: 2,616
20 million credit badge5 year member badge
Message 67984 - Posted: 4 Jan 2019, 20:10:29 UTC

I'm having nothing but trouble with V1.74

I get one the is fine, finishes in 35 mins the next one that's running 12 cpu cores and takes 36hrs.

Been happening now for the past week or so.
ID: 67984 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Link
Avatar

Send message
Joined: 19 Jul 10
Posts: 356
Credit: 16,317,754
RAC: 2
10 million credit badge8 year member badge
Message 67985 - Posted: 5 Jan 2019, 10:12:09 UTC - in response to Message 67984.  
Last modified: 5 Jan 2019, 10:15:32 UTC

I get one the is fine, finishes in 35 mins the next one that's running 12 cpu cores and takes 36hrs.

Very different run times are normal for n-Body, just don't abort them and eventually decrease your cache size since you have some "Not started by deadline - canceled" WUs. You have an average turnaround time of over 7 days, for some of the applications even almost 10 days, that's way to high for Milkyway.
.
ID: 67985 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Michael E.

Send message
Joined: 27 Jan 10
Posts: 1
Credit: 1,862,086
RAC: 1,242
1 million credit badge9 year member badge
Message 68165 - Posted: 17 Feb 2019, 2:32:38 UTC - in response to Message 67985.  

I just started using N-body work units again after a few years.

A work unit that originally said it would complete in 18 hours on a 2-CPU system (50% of 4 CPUs) has taken almost three days so far and is about half finished (Host name: DESKTOP-QKT2DLD has BOINC Versiom 7.14.2). I suspect at least one or both CPU threads are stalled maybe waiting for a join based on very low CPU usage.

I just turned off N-body apps in Milkyway Preferences temporarily because one system is a laptop and I prefer shorter work units. That laptop only allows one CPU (25% or 4 CPUs) so I was not expecting it to get N-body work units assigned!

If I can help, please send me a private note. I am familiar with parallel processing and native code app performance analysis, so I am curious what is happening.

Michael E.
ID: 68165 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : News : Nbody release v1.74

©2019 Astroinformatics Group