Welcome to MilkyWay@home

Posts by corysmath

1) Message boards : Number crunching : Stalled computation (Message 73323)
Posted 5 May 2022 by corysmath
Post:
Turns out I almost fixed the stalling problem.

A preventative workaround fix is to set the CPU time usage to 100% in the computing preferences, if set lower than that. After doing this none of the n-body tasks that I have run have stalled on the PC's that previously did stall, which all have Intel i7 CPU's.

As noted in my earlier post If an n-body task has already stalled the only fix I know is to exit BOINC and restart.

Note setting CPU time usage to the maximum 100% will likely increase the CPU temperature. I was able to bring it down by eliminating overclocking and setting performance options to maximize stability and save energy.

Some older PC's with duo and quad CPU's (both Intel and AMD) have never stalled on n-body tasks, so I have left the CPU time usage at the default 75%.

May the 4th be with you.
2) Message boards : Number crunching : Stalled computation (Message 73069)
Posted 22 Apr 2022 by corysmath
Post:
This n-body task stalled at just 0.038% done with 232 days remaining. I give up but will check back later.

Application
Milkyway@home N-Body Simulation 1.82 (mt)
Name
de_nbody_08_31_2021_v176_40k__data__13_1647295263_13271884
State
Project suspended by user
Received
4/18/2022 9:20:16 AM
Report deadline
4/30/2022 9:20:15 AM
Resources
8 CPUs
Estimated computation size
12,267 GFLOPs
CPU time
00:05:00
CPU time since checkpoint
00:03:33
Elapsed time
02:06:50
Estimated time remaining
233d 03:26:21
Fraction done
0.038%
Virtual memory size
11.22 MB
Working set size
5.24 MB
Directory
slots/4
Process ID
13236
Executable
milkyway_nbody_1.82_windows_x86_64__mt.exe
3) Message boards : Number crunching : Stalled computation (Message 73068)
Posted 21 Apr 2022 by corysmath
Post:
I have had several more stalled n-body tasks today. The latest stalled at 14.004% done after running for over an hour, blocking all other BOINC tasks from running, so I will have to abort it and maybe switch to another project.

Here are the stalled task details:

Application
Milkyway@home N-Body Simulation 1.82 (mt)
Name
de_nbody_08_31_2021_v176_40k__data__11_1647295263_13261164
State
Running
Received
4/18/2022 9:20:16 AM
Report deadline
4/30/2022 9:20:15 AM
Resources
8 CPUs
Estimated computation size
12,303 GFLOPs
CPU time
00:08:57
CPU time since checkpoint
00:02:01
Elapsed time
01:27:29
Estimated time remaining
08:57:12
Fraction done
14.005%
Virtual memory size
11.23 MB
Working set size
13.29 MB
Directory
slots/4
Process ID
6096
Progress rate
9.720% per hour
Executable
milkyway_nbody_1.82_windows_x86_64__mt.exe
4) Message boards : Number crunching : Stalled computation (Message 72771)
Posted 14 Apr 2022 by corysmath
Post:
Here is an example of an n-body task that stalled::
task de_nbody_08_31_2021_v176_40k__data__12_1647295263_10374507_0

After it stalled the CPU usage was just a few percent suggesting computation was truly stalled.

I tried a suspend and resume but remained stalled at 20.843% done.

I also tried upping the CPU time usage from 75% to 100% but still remained stalled.

After looking through earlier comments in this thread I tried the following:
I exited from the BOINC manager and restarted it.

This worked; the task progressed normally and ran to completion.

Hope this example may help if someone wants to dig into what's happening more than I can.
5) Message boards : Number crunching : Stalled computation (Message 72766)
Posted 13 Apr 2022 by corysmath
Post:
I'm having problems with some tasks that go on indefinitely. The time remaining goes up rather than down so task never finishes. I have to abort the task so others can run. Happens for several Windows 10 computers. Don't know if it is just n-body or not. Will have to shift to other projects if this problem persists.




©2024 Astroinformatics Group