Hello,
I've some not SOOOO fast computers running BOINC. Some of them share CP and SETI, e.g..
When BOINC switches between projects it restarts the paused project at some sort of checkpoint. Especially I've seen this in CP, there it restarts at 00:00 1 or 2 days before the last result. Example of output:

3lmv_100189695 - PH 1 TS 010565 - 11/07/1811 02:30 - H:M:S=0050:05:11 AVG=17.07 DLT= 6.91
3lmv_100189695 - PH 1 TS 010566 - 11/07/1811 03:00 - H:M:S=0050:05:18 AVG=17.07 DLT= 7.85
3lmv_100189695 - PH 1 TS 010567 - 11/07/1811 03:30 - H:M:S=0050:05:26 AVG=17.07 DLT= 7.96
2005-02-07 01:33:28 [climateprediction.net] Pausing result 3lmv_100189695_1 (removed from memory)
2005-02-07 01:33:28 [SETI@home] Restarting result 07ap04aa.1298.25888.890912.92_3 using setiathome version 4.02
CPDN Monitor got quit request...
Detaching shared memory...
2005-02-07 02:33:29 [climateprediction.net] Restarting result 3lmv_100189695_1 using hadsm3 version 4.04
2005-02-07 02:33:29 [SETI@home] Pausing result 07ap04aa.1298.25888.890912.92_3 (removed from memory)
Starting model in /drives/e2fs/hda5/boinc/projects/climateprediction.net...
Created shared memory region key = 26810
Env Used=LD_LIBRARY_PATH=/drives/e2fs/hda5/boinc/projects/climateprediction.net:/usr/local/lib:/usr/lib:/lib
Starting model ID 3lmv_100189695 Phase 1
Waiting for model startup, this may take a minute...
Stack size=48.00 MB
3lmv_100189695 - PH 1 TS 010513 - 00/00/0000 00:00 - H:M:S=0049:50:06 AVG=17.07 DLT= 0.00
3lmv_100189695 - PH 1 TS 010514 - 10/07/1811 01:00 - H:M:S=0049:51:09 AVG=17.07 DLT=63.35
3lmv_100189695 - PH 1 TS 010515 - 10/07/1811 01:30 - H:M:S=0049:51:17 AVG=17.07 DLT= 7.92
3lmv_100189695 - PH 1 TS 010516 - 10/07/1811 02:00 - H:M:S=0049:51:25 AVG=17.07 DLT= 7.90
3lmv_100189695 - PH 1 TS 010517 - 10/07/1811 02:30 - H:M:S=0049:51:33 AVG=17.07 DLT= 7.89

So BOINC loses some time already used for the calculation of same data (in the example above: 15 minutes of overlapping calculation).

Can I avoid or reduce this? The preference "Write to disk at most every XX seconds" has no influence.

I'm using BOINC 4.19. I've seen this in Linux and Windows build of BOINC.

Thank you!

Bye
Stefan

---

If you set keep in memory while suspended to yes, this should remove the problem. If the memory is needed to run SETI or other programs the operating system will shunt the memory to the hard disk so that this does not adversely affect performance.

---

Visit BOINC WIKI for help

And join BOINC Synergy for all the news in one place.

Run only one project per Computer, or upgrade them......

---

<a href=\"http://boinc-doc.net/boinc-wiki/index.php?title=Main_Page\">Link to Unofficial Wiki for BOINC, by Paul and Friends</a>

&gt; If you set keep in memory while suspended to yes, this should remove the
&gt; problem. If the memory is needed to run SETI or other programs the operating
&gt; system will shunt the memory to the hard disk so that this does not adversely
&gt; affect performance.
&gt;

Thank you! This was very helpful! I ignored this parameter until now... :-))

Bye
Stefan

---

&gt; Run only one project per Computer, or upgrade them......
&gt;
I'm using the newest version of CPDN and BOINC already, but there was no difference. But I thank you for your recommendation!

Bye
Stefan

---