There have been many cases where the BOINC client caused a problem,
such as running too many VMs and bogging down the system.
Volunteers then ask for a preference that lets them manually fix the problem.
In such cases it's better to figure out the root cause of the original problem
(e.g. that VM memory usage isn't being accounted correctly)
and change BOINC so it doesn't happen.
BOINC should compute invisibly without fiddling with preferences.
Also, job scheduling and work fetch are intertwined.
The work fetch algorithm does a simulation of job scheduling
in deciding how much work to request for the various resources (CPU, GPU).
Changes to the job scheduling policy (e.g. by new prefs)
typically lead to problems with work fetch (e.g. starved resources).
-- D
-------- Forwarded Message --------
Subject: Re: [BOINC/boinc] project preference to set number of used
cpu's (#1414)
Date: Thu, 17 Aug 2017 21:43:57 +0000 (UTC)
From: Jord <[email protected]>
Reply-To: BOINC/boinc
<reply+000f0a813415d8805fe99d8915ba53d1ed110fd0e62c046b92cf0000000115add01d92a169ce06b1c...@reply.github.com>
To: BOINC/boinc <[email protected]>
CC: Subscribed <[email protected]>
Is this still being asked for?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/BOINC/boinc/issues/1414#issuecomment-323202764>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AA8KgUnryQefSwnmghCeRfv2KGCDJSTpks5sZLQdgaJpZM4GR9XU>.
_______________________________________________
boinc_dev mailing list
[email protected]
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
