Processor usage question

Message boards : BOINC client : Processor usage question
Message board moderation

To post messages, you must log in.

AuthorMessage
Jim Wilkins

Send message
Joined: 11 Oct 06
Posts: 77
United States
Message 16046 - Posted: 23 Mar 2008, 15:26:12 UTC

In preferences, I normally have the "on" times set between 0700-2200 every day. I was going to be gone overnight, so I used the day-of-week override to reflect that the computer would be on up to a certain time, when I left the house, and would come back on a certain time after I got back. During the time that the computer was not on, three tasks were due. I thought that BOINC would go into high priority mode for those tasks since the "off" time was going to occur in about 3 hours. However, BOINC acted like nothing had changed. I finally lost my nerve and forced them to complete by suspend all other tasks. So, after this rather wordy intro, how does BOINC use the processor usage information?

Thanks,
Jim
ID: 16046 · Report as offensive
John McLeod VII
Avatar

Send message
Joined: 29 Aug 05
Posts: 147
Message 16066 - Posted: 24 Mar 2008, 21:16:46 UTC

The scheduler does not use the information from the schedule, it uses history to try to determine future actions, and then only based on the fractions of time spent off, not the durations.

BOINC WIKI
ID: 16066 · Report as offensive
Jim Wilkins

Send message
Joined: 11 Oct 06
Posts: 77
United States
Message 16086 - Posted: 26 Mar 2008, 12:10:39 UTC - in response to Message 16066.  

The scheduler does not use the information from the schedule, it uses history to try to determine future actions, and then only based on the fractions of time spent off, not the durations.


So currently, that part of preferences not used?

Jim
Thanks,
Jim
ID: 16086 · Report as offensive
Jim Wilkins

Send message
Joined: 11 Oct 06
Posts: 77
United States
Message 16090 - Posted: 26 Mar 2008, 19:03:56 UTC - in response to Message 16089.  

The scheduler does not use the information from the schedule, it uses history to try to determine future actions, and then only based on the fractions of time spent off, not the durations.


So currently, that part of preferences not used?

Jim


It's used but not the way you think it is used.

You think the scheduler can look at it's future schedule of on/off times and decide what it needs to do now to prepare for or cope with future conditions. The scheduler is not that intelligent and I think it need not be that intelligent.

The scheduler looks at deadlines and attempts to meet them. It keeps a record of the percentage of time the computer has been allowed to crunch in the past and it uses that percentage to decide how much work to download.



You are right about how I thought the scheduler worked. I think I understand your explanation and that explanation essentially says that the preferences governing processor usage are not used in the scheduler. That's great, I think the scheduler is a remarkable piece of software. I'm just pursuing this from an academic point of view.

Jim
ID: 16090 · Report as offensive
John McLeod VII
Avatar

Send message
Joined: 29 Aug 05
Posts: 147
Message 16091 - Posted: 26 Mar 2008, 22:25:58 UTC - in response to Message 16087.  

Any job getting within 24 hours of deadline goes into High Priority, in fact if there is a squeeze it will occur earlier, so not sure for how long you scheduled the machine to be off... > 24 hours?

Not in the current scheduler.

The current scheduler is a bit better than that.

If a task will not finish between now and 90% of the time to report deadline - (Connect every X + task switch interval + safety margin) at the resource fraction of the tasks on hand, it is in danger of being late, and gets the CPU now.

Currently the safety margin is set to 0 (Not my decision).

BOINC WIKI
ID: 16091 · Report as offensive

Message boards : BOINC client : Processor usage question

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.