- Oct 9, 1999
- 4,375
- 2,164
- 146
The 2nd Javelin Throw has been announced:
Start: 12 May 2024 00:00 UTC
End: 13 May 2024 00:00 UTC
NFS@Home
Start: 12 May 2024 00:00 UTC
End: 13 May 2024 00:00 UTC
NFS@Home
I did. I agree to cancel sidock as the steeplechase and make it 5 days.
Isn't milkyway@home GPU ?Not having a GPU heavy project in the mix is....disappointing.
see how up to date I am.....MilkyWay is CPU only since last June.
https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=5010
https://forums.anandtech.com/threads/milkyway-home-separation-project.2613122/
I caught some which take 1...3 days when running singlethreaded on my lower clocked server CPUs. This is not visible before you actually run them because the initial estimation of task duration is useless. Thus, running multithreaded with a moderate thread count might be the better idea.At your MilkyWay@home preferences page, you can select whether to run the application with 1 thread or on several threads per task. Right now the workunit sizes are small enough to simply run the tasks singlethreaded.
Are those task actually progressing in the progress bar? I still have a few stragglers that seem to stall. Goes to X% then doesn't seem to advance any. Maybe due to underclocking/volting? My little n100 machine has been doing MW for months without a single stalled task, but it runs at stock speedsI caught some which take 1...3 days when running singlethreaded on my lower clocked server CPUs. This is not visible before you actually run them because the initial estimation of task duration is useless. Thus, running multithreaded with a moderate thread count might be the better idea.