Posts by TomB

1) Message boards : News : New Release- Nbody version 1.52 (Message 63937) Posted 18 Sep 2015 by TomB Post: I've got one that's seems to be causing problems. This one has been running for 78 hours and it's been at 100% since about 9 hours and it never did save a checkpoint. The original estimate was for about 1.5 hours. BOINC indicates it is using 8 cpus, but the activity monitor shows it is only using 1.3% cpu with 2 threads. I've seen some with the previous version of N-body work like this, so I'll probably watch it for a little while longer to see if it finishes. I'm running a Mac Mini with OS 10.10.5 The work unit is de_nbody_9_09_15_orphan_sim_0_1437561602_56033_0
2) Message boards : News : New Nbody Version 1.50 (Message 63641) Posted 27 May 2015 by TomB Post: The work unit from the previous message finally finished. It took it 50.5 hours (about 50 hours longer than the original estimate), but it is finished. Has to be some sort of bug, but it looks like they will finish eventually, and with no checkpoints you still run the risk of them starting over if the computer is restarted for any reason.
3) Message boards : News : New Nbody Version 1.50 (Message 63633) Posted 25 May 2015 by TomB Post: This doesn't seem to be a windows only problem. I've currently got one on my Mac Mini that should have finished within an hour or so, but is currently been running for over 10 hours with the last 3 hours indicating 100% complete. This is the second time it has tried to run, since it isn't saving a checkpoint the last time the computer was shut down the work unit restarted from 0%. It was running over 24 hours the first time. Also looking at the activity monitor, it doesn't look like it uses more than one processor when it claims it is using all 8. The ones I've watched that do work also seem strange where they will slow down the closer they are to 100%, then will go back near 0% and rapidly count up to completion and finish normally. I'll see how long I can keep this one going to see if it finishes, but if it goes too long I'll have to abort it since no other work units can run.