I am running QMC@home and ABC@home simultaneously with 50%/50% ratio, switching between applications every 60 min. I have a workunit from ABC which has hung at 81.4% and 60 min are insufficient to make any progress. So what happens is that when the ABC project starts, it calculates 60 min beginning from about 1 min CPU time, no progress is made and, I guess, no intermediate results get stored, when CPU time becomes 1h:1m, the other application starts working. In one hour the same situation appears. In this way, I will never send a completed workunit.

Is there a way to change this? Obviously I can dedicate the entire box to ABC, or increase the time between switches, or increase the ratio in favor of ABC, bu, suppose I do not want to do so. Is there a way to prepare the workuints in such a way that progress is made more frequently? (I assume the method of how intermediate results get stored is a feature in BOINC and not the abc application, right?)
____________

PhiAlpha,

Your complaint is quite common. What most crunchers do is increase the amount of time BOINC spends on each project. You're switching every 60 minutes now but you can increase that. I find a 240 minute interval works well, others prefer 360. You can change the interval in your preferences under Your Account found on the project's home page. The interval propagates to all the projects you are attached to.

EDIT: Added... Actually the intermediate results you refer to are called checkpoints and they are entirely up to the project's application. BOINC cannot control the checkpoints. It's often difficult for the programmers to make the application checkpoint at an interval that is convenient for the cruncher so we have to learn to love it and make it work by increasing the interval between project switches.

Thanks Dagorath, I will do as you suggest.
____________

I am running QMC@home and ABC@home simultaneously with 50%/50% ratio, switching between applications every 60 min. I have a workunit from ABC which has hung at 81.4% and 60 min are insufficient to make any progress. So what happens is that when the ABC project starts, it calculates 60 min beginning from about 1 min CPU time, no progress is made and, I guess, no intermediate results get stored, when CPU time becomes 1h:1m, the other application starts working. In one hour the same situation appears. In this way, I will never send a completed workunit.

Is there a way to change this? Obviously I can dedicate the entire box to ABC, or increase the time between switches, or increase the ratio in favor of ABC, bu, suppose I do not want to do so. Is there a way to prepare the workuints in such a way that progress is made more frequently? (I assume the method of how intermediate results get stored is a feature in BOINC and not the abc application, right?)