Questions and Answers :
Windows :
Work Units don't finish
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 31 Jan 12 Posts: 2 Credit: 4,007,241 RAC: 1,086 |
Hi! I'm having a problem with some work units. These units reach a high percentage of work but stop advancing. They stopped at that point for many hours/day. An example is this task: de_nbody_orbit_fitting_09_21_2025_v193_OCS_north_MW2014__data__2_1758550502_250610 fixed at 87,597% Does anyone know why this is happening? Thanks Alberto |
|
Send message Joined: 19 Jul 10 Posts: 750 Credit: 20,211,501 RAC: 7,898 |
Do you allow BOINC 100% of CPU time? If not, that's why it's happening.
|
|
Send message Joined: 31 Jan 12 Posts: 2 Credit: 4,007,241 RAC: 1,086 |
Hi! Thank you for the answer. Why does this task need 100% of CPU time if others work with less ? I suspended the task for a few days and today when I resume it, it finished in few seconds. Was there a fix to the app? |
|
Send message Joined: 19 Jul 10 Posts: 750 Credit: 20,211,501 RAC: 7,898 |
The project devs need to fix it. If you have temperature issues when running on all cores 100% of time, use less threads instead. Or even better: limit the boost frequency of your CPU, the last few hundred MHz generate lots of heat for almost nothing. I run my Ryzen 5700G at 4.0 GHz instead of the 4.65 it would like to run at and can keep it below ~75°C at pretty much any load with the stock cooler it came with. Now when running 14x Milkyway and 1x Einstein on iGPU it's even just 52°C since Milkyway generates in general extremely little heat, but when I run WCG or anything else on the CPU cores it's up to 75°C. Around 30-35% lower package power (= heat generation) for 14% lower clock speed and that while the iGPU works significantly harder for some reason. Definitely worth it.
|
©2025 Astroinformatics Group