Allowing work fetch again.

From Unofficial BOINC Wiki

Contents 1 General 2 Version Information 2.1 Alternate Message Formats 3 Example Log(s) 3.1 Allowing Work Fetch Again 3.1.1 Line-By-Line Explanation 4 Other Related Messages 4.1 Work Scheduler Messages (General) 4.2 "Trigger" Messages 4.3 Work Fetch Policy Messages 4.4 Work Schedule Policy Messages 5 Also See

[edit] General

Message Type: Status Message

This Message means that the BOINC Client Software has decided that there is "room" in the Work Buffer that could be filled by a BOINC Powered Project's work when the next Scheduler Request Message is sent to a Project's Scheduling Server.

[edit] Version Information

[edit] Alternate Message Formats

• New work fetch policy: work fetch allowed

Obsolete/Changed in Version: 4.45

[edit] Example Log(s)

[edit] Allowing Work Fetch Again

(1) 2005-06-15 13:05:05 [SETI@home] Sending scheduler request to
                                    http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
(2) 2005-06-15 13:05:05 [SETI@home] Requesting 0 seconds of work, returning 1 results
(3) 2005-06-15 13:05:06 [SETI@home] Scheduler request to
                                    http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
(4) 2005-06-15 14:04:58 [         ] Allowing work fetch again.
(5) 2005-06-15 14:04:58 [         ] Resuming round-robin CPU scheduling.

Line-By-Line Explanation

1. Sending scheduler request to '(url)'
   • We contact the Scheduler.
2. Requesting '(seconds)' seconds of work, returning '(count)' results
   • Because we need to return some Results even though we do not need more work.
3. Scheduler request to '(url)' succeeded
   • And the exchange of a Scheduler Request Message and Scheduler Reply Message was successful.
4. Allowing work fetch again.
   • And because of the return of work, the BOINC Client Software will be allowed to obtain additional work when it contacts a Scheduler because the Work Buffer's contents is has "room" now for more work.
5. Resuming round-robin CPU scheduling.
   • And, with the easing of the "schedule pressure" we can leave the Earliest Deadline First mode of operation.

[edit] Other Related Messages

[edit] Work Scheduler Messages (General)

• request_reschedule_cpus: exit_tasks
• request_reschedule_cpus: files downloaded
• request_reschedule_cpus: process exited
• request_reschedule_cpus: project op
• request_reschedule_cpus: Resuming activities
• request_reschedule_cpus: start failed
• schedule_cpus: time '(x.y)'

[edit] "Trigger" Messages

• Computer is over committed
• Less than 1 day until deadline
• Deadline is before reconnect time

[edit] Work Fetch Policy Messages

• Allowing work fetch again.
• Suspending work fetch because computer is overcommitted.

[edit] Work Schedule Policy Messages

• Resuming round-robin CPU scheduling.
• Using earliest-deadline-first scheduling because computer is overcommitted.

[edit] Also See

• Work Scheduler