I do not have a dedicated computer for BOINC calculations. I use the computer I use every day. Sometimes this computer has little to do. Then the BOINC calculations are done in full swing. It also happens that I load the computer with demanding tasks for several days. There are also times when I don't turn on my computer for a few days.
To avoid overheating of the processor, I use TThrottle program. This program allocates to BOINC tasks from 2 to 100% of CPU power – depending on CPU temperature.
All the above factors mean that BOINC jobs are not computed at a constant rate, with constant access to the same resources. This, in turn, sometimes causes BOINC to misjudge the capabilities of the computer and a job is calculated many days after the deadline. For example, a task is now being calculated that will probably take two more days to complete, and it is already 11 days past the deadline. I do not think these calculations make sense yet.
Of course, I can abort these calculations. However, I believe that such a task should automatically commit suicide if it is past the deadline, causing the results of the calculation to be rejected by the server anyway.
Copyright © 2024 Einstein@Home. All rights reserved.
Grzegorz Skoczylas wrote: I
)
You should probably abort the task anyway and just start on a new one that hasn't expired yet, along with that you might think about going onto the website here and changing your cache settings to something ALOT smaller. That way you can finish tasks on time and not worry about running ones that are already 11 days late, some like 0.01 and 0.25 for the two settings will keep alot fewer tasks stored on your computer and still get some more as you finish the ones you have. Aborting tasks doesn't hurt the Server it just the tasks back into the queue so it's available for someone else who needs a task.