Hello every one,

I have problems with two nbody work units (MilkyWay@Home N-Body Simulation 1.72 (mt); 3 core-Cpus):

• de_nbody_10_11_2018_v172_20k__data_2_1538704602_161105
  
• de_nbody_10_11_2018_v172_20k__data_3_1538704602_168146
  

Both started to count the time remaining to calculate every second up.
For example: data 3 was already processed 7 hours and the time remaining was 42 days, 21 minutes and some seconds. But with each second of calculation minutes remaining going up. After restarting the computer this work unit started all over again starting with 0 hours, minutes processed.
data 2 was calculated 2 hours and 19 minutes, but with 1000 days and so on.
I halted both work units.

Is it possible, that I'm not getting any valid result with these ones?
Advice is appreciated.

Computer: Lenovo Laptop, intel core i3 3110M @ 2.40 Ghz, 2 cores, 4 threads, 8 Gbytes DD3 (CPU-Z data), with Win 10 installed on it.

Best Regards,
Diplo
Rechenkraft.net e.V.

I'm having similar problems:


Application
MilkyWay@Home N-Body Simulation 1.72 (mt)
Name de_nbody_10_24_2018_v172_20k__data_1_1540379102_33925
State Running
Received 11/11/2018 10:48:09
Report deadline 23/11/2018 10:48:07
Resources 6 CPUs
Estimated computation size 11,120 GFLOPs
CPU time 08:52:57
CPU time since checkpoint 03:04:39
Elapsed time 5d 02:56:59
Estimated time remaining 1d 06:09:50
Fraction done 80.300%
Virtual memory size 9.46 MB
Working set size 4.84 MB
Directory slots/2
Process ID 580
Executable milkyway_nbody_1.72_windows_x86_64__mt.exe

My pc is a Dell XPS Intel Core i7 3.4GHz 4 core 8 logical processors runint W10 Pro. Boinc and virtualisatoin software are up to date.


Ideas?

David Dewick

I'm having similar problems:


Application
MilkyWay@Home N-Body Simulation 1.72 (mt)
Name de_nbody_10_24_2018_v172_20k__data_1_1540379102_33925
State Running
Received 11/11/2018 10:48:09
Report deadline 23/11/2018 10:48:07
Resources 6 CPUs
Estimated computation size 11,120 GFLOPs
CPU time 08:52:57
CPU time since checkpoint 03:04:39
Elapsed time 5d 02:56:59
Estimated time remaining 1d 06:09:50
Fraction done 80.300%
Virtual memory size 9.46 MB
Working set size 4.84 MB
Directory slots/2
Process ID 580
Executable milkyway_nbody_1.72_windows_x86_64__mt.exe

My pc is a Dell XPS Intel Core i7 3.4GHz 4 core 8 logical processors runint W10 Pro. Boinc and virtualisatoin software are up to date.


Ideas?

David Dewick

The n-body wu's do not work for everyone, that's why there are sooo many revisions all the time, in your settings you can choose not to run the n-body wu's which uses multiple cpu cores for one wu, and instead run one wu per cpu core.

in your settings you can choose not to run the n-body wu's which uses multiple cpu cores for one wu, and instead run one wu per cpu core

I can´t even find these settings... and I would really like to, because my computers simply stop on multiple core tasks. I am forced to abort them.

Thanks in advance,

MOe1934

Look in your MW account page under Milkyway@home Preferences. Uncheck the MilkyWay@Home N-Body Simulation: yes setting to turn it into MilkyWay@Home N-Body Simulation: no by using the Edit MilkyWay@Home preferences option at the bottom of the page.

---