climateprediction.net (CPDN) home page
Thread 'Preempted Prevention'

Thread 'Preempted Prevention'

Questions and Answers : Wish list : Preempted Prevention
Message board moderation

To post messages, you must log in.

AuthorMessage
old_user1940

Send message
Joined: 27 Aug 04
Posts: 9
Credit: 524,774
RAC: 0
Message 2455 - Posted: 1 Sep 2004, 4:55:47 UTC

While it is all well and good that Boinc is smart enough to actively monitor its varied workload; But I still desire the ability to designate specific project instances as \"Un-Preemptable\"

I am certain that there are many others who also wish for this feature, and the need for such an option will only grow as the number of boinc based project increases...
ID: 2455 · Report as offensive     Reply Quote
old_user355

Send message
Joined: 7 Aug 04
Posts: 187
Credit: 44,163
RAC: 0
Message 2624 - Posted: 2 Sep 2004, 2:39:47 UTC

That would in effect "break" the schedulers even more...

<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=355"><img border="0" height="80" src="http://355.cpdn.sig.boinc.dk?188"></a>
ID: 2624 · Report as offensive     Reply Quote
old_user1940

Send message
Joined: 27 Aug 04
Posts: 9
Credit: 524,774
RAC: 0
Message 2721 - Posted: 2 Sep 2004, 16:09:52 UTC
Last modified: 3 Sep 2004, 5:36:06 UTC

Heffed:

1st off, how do I place one of those status boxes on my posts? -Thank you. (9/3/04)

How would a client side option "break" the schedulers at all, much less the "even more" that you imply. Perhaps I am missing the boat, but from my understanding of boinc the schedulers are computers who work day round to generate w/u s so they can be downloaded by the client. Please explain this if my understanding is flawed.

Perhaps my question was not precise enough, so I shall now reformulate it to refelect my personal "beef" with boinc.

On my 3.06 HT P4 I allow both SETI and CPDN to run concurrently, each with 50% resources, I have whittled the "amount of work to be downloaded to between 0.4 and 0.5 days for SETI. And even with these settings SETI continues to preempt CPDN whenever it feels like...

I want my CPDN w/u to run in peace so my P4 HT can finish its first CPDN by October'04. As a boinc participant I feel that this is a reasonable request.

This concern should be addressed in some manner before the boinc platform becomes more populated with other DC projects.

While this is only an issue for people who participate in multiple processes on computer who have multiple processors (or CPU's with HT) so this may affect a limited number of users for the moment, but as more people buy CPUs with HT the number affected will grow as well... this does not even factor in how boinc will preceive Dual Core CPU's which should become standard by '06
ID: 2721 · Report as offensive     Reply Quote
old_user355

Send message
Joined: 7 Aug 04
Posts: 187
Credit: 44,163
RAC: 0
Message 2735 - Posted: 2 Sep 2004, 17:49:41 UTC - in response to Message 2721.  
Last modified: 2 Sep 2004, 17:51:41 UTC

&gt; 1st off, how do I place one of those status boxes on my posts?

<a href="http://www.boinc.dk/index.php?page=signatures">Here.</a>

&gt; How would a client side option "break" the schedulers at all, much less the
&gt; "even more" that you imply. Perhaps I am missing the boat, but from my
&gt; understanding of boinc the schedulers are computers who work day round to
&gt; generate w/u s so they can be downloaded by the client. Please explain this if
&gt; my understanding is flawed.

The schedulers try to determine based on several criteria such as CPU speed, disk space available, how many WUs you already have, etc... how much work to give each host.

In order to have any idea at all how much work to dole out, cache settings must be "global". Meaning, you change a cache setting on one project, those new settings will migrate to every BOINC project you are attached to. If you started having different cache settings per project, BOINC can no longer keep a very good handle on how much to give you.

The old system wasn't perfect, but it generally wouldn't give you more work than you could finish by the deadline unless you messed with it.

The new system is however even more "broken". It is entirely possible now to blow past deadlines due to the preempting schedule. Apparently deadlines are no longer taken into consideration. (hopefully fixed soon)

So basically, if you could tell a project not to preempt, (CPDN for example) the scheduler would be even the worse for trying to figure out what to give you. It would now need to somehow know that it shouldn't give you work for <i>any</i> project until your CPDN unit is nearly complete.

To make any sort of sense, it would have to be all preempt, or no preempt. A mix simply wouldn't cut it.

<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=355"><img border="0" height="80" src="http://355.cpdn.sig.boinc.dk?188"></a>
ID: 2735 · Report as offensive     Reply Quote
old_user1940

Send message
Joined: 27 Aug 04
Posts: 9
Credit: 524,774
RAC: 0
Message 2799 - Posted: 3 Sep 2004, 5:36:39 UTC - in response to Message 2721.  

Test
<a href="http://www.boinc.dk/index.php?page=user_statistics&amp;project=cpdn&amp;userid=1940"><img border="0" height="80" src="http://1940.cpdn.sig.boinc.dk?188"></a>
ID: 2799 · Report as offensive     Reply Quote

Questions and Answers : Wish list : Preempted Prevention

©2024 cpdn.org