What uplinger does not say is that these priority changes are not related to the value of the project (he will correct me if I am wrong) but to particular operational reasons. For example,
- Rice is in slow mode because the Researchers are currently upgrading their disk space capacity for receiving results
- The CE Project is still in launching/debugging mode
- the DDDT lab has just started again to send work to WCG after having been hit by hurricane Ike.

When these situations have been cleared maybe they will be pushed higher than the other ones if they are behind their anticipated schedule.

Cheers. Jean.

... and of course a project scientist, one or the other who's having a fit for not having this critical batch complete to work on the next experiment. There's the phone that rings and knreed with the golden key to the rush hopper.



hi di hi

Normally there is nothing to do: tasks are taking checkpoints periodically, and when you restart your computer they resume at the latest checkpoint.
You will have to tell us more about
- your hardware
- the projects that you are running
- how long are your sessions in average, between the start of Boinc and the next shutdown
- your Boinc settings (% of processor time, particular running preferences if any, etc...).

If there is nothing wrong in your machine except that your sessions are too short for reaching the next checkpoint we will tell you which projects to choose for the most efficient use of your client.

Cheers. Jean.

You must be running with hyperthreading enabled. Suggest you might want to disable it. You will only be able to run one task at atime, but it will finish about 55% quicker than if you have two tasks running with hyperthreading. You may sacrifice a little efficiency, but should gain some stability.

Cheers