My guess on the 1 GB laptop is that it is thrashing because it doesn't have
enough memory. That would cause a lot of disk i/o, and could account for
the behavior you're describing. On cpu-bound tasks, such as what you're
running on boinc, if you exceed physical memory and the OS starts swapping
t
The state file is written mostly when jobs start and end.
(A long time ago it was written on each checkpoint,
but we changed this).
-- David
On 18-Jun-2013 1:29 AM, Heinz-Bernd Eggenstein wrote:
How often is the client_state.xml file updated? It can grow to enormous
sizes if you have a huge num
How much I/O do these machines do when BOINC is not running?
4 GB/hr is about 1 MB/sec.
I can't think of any BOINC activity that would write this much.
We need to look at the system call trace to get more info.
-- David
On 18-Jun-2013 12:03 AM, "Steffen Möller" wrote:
Gesendet: Montag, 17. J
Hi all,
Interesting. I guess it would be useful to run BOINC on a dedicated
partition (e.g. ext hard disk/ USB stick) to isolate BOINC's contribution
to the stats.
How often is the client_state.xml file updated? It can grow to enormous
sizes if you have a huge number of waiting tasks or unr
> Gesendet: Montag, 17. Juni 2013 um 21:29 Uhr
> Von: "David Anderson"
> An: boinc_dev@ssl.berkeley.edu
> Betreff: Re: [boinc_dev] Can we do shared memory with no disk usage?
>
> In situations were BOINC is causing unexpectedly large
> (> 1 GB/hour) disk I/O,
> we need to figure out the source of
