LHC@home

Don't know what you mean by:

(Don't make me add this as a check for EDF).

But I do know that Boinc is smart enough to switch to another project to make sure it gets done on time.

1) John means that he's the one writing the panic mode code
2) Someone correct me if I'm wrong, but I think the problem with a 24-hour value for 'switch every' would help DEFEAT the panic mode code. If what I remember is right, the EDF scheduler only kicks in when results are switched, i.e. at the end of the 'switch every' timer. So by going to a 24-hour value, the panic mode could only possible kick in A) every 24 hours or B) every time a work unit is done (or C) every time you hit Update manually). If you have a slow system crunching that takes more than 24 hours to crunch a result, then you would very likely miss deadlines.

Granted, this is founded on the ideas that: 1) you have a slower machine or large results, and 2) that I'm right about EDF and how it kicks in.

Can anyone affirm or correct this for me?

(j)
James

1) John means that he's the one writing the panic mode code

Not only the panic-mode; as far as I know he has developed the complete actual version of the local scheduler:

• Respecting the ResourceShare
  
• Keep WUs in Time before Deadline
  
• Calculate the best crunching-priority for users with dial-up-systems
  

To get all this things working he needed the panic-mode, but panic-mode is only a small aspect of his complete work

---

Supporting BOINC, a great concept !

1) John means that he's the one writing the panic mode code

Not only the panic-mode; as far as I know he has developed the complete actual version of the local scheduler:

• Respecting the ResourceShare
  
• Keep WUs in Time before Deadline
  
• Calculate the best crunching-priority for users with dial-up-systems
  

To get all this things working he needed the panic-mode, but panic-mode is only a small aspect of his complete work

Correct. I didn't mean that EDF was John's only contribution. I just slid past the rest for brevity's sake... 8)

(j)
James

Don't know what you mean by:

(Don't make me add this as a check for EDF).

But I do know that Boinc is smart enough to switch to another project to make sure it gets done on time.

1) John means that he's the one writing the panic mode code
2) Someone correct me if I'm wrong, but I think the problem with a 24-hour value for 'switch every' would help DEFEAT the panic mode code. If what I remember is right, the EDF scheduler only kicks in when results are switched, i.e. at the end of the 'switch every' timer. So by going to a 24-hour value, the panic mode could only possible kick in A) every 24 hours or B) every time a work unit is done (or C) every time you hit Update manually). If you have a slow system crunching that takes more than 24 hours to crunch a result, then you would very likely miss deadlines.

Granted, this is founded on the ideas that: 1) you have a slower machine or large results, and 2) that I'm right about EDF and how it kicks in.

Can anyone affirm or correct this for me?

(j)
James

Confirmed.

---

BOINC WIKI

ok put it back to 2 hours
thanks for the feedback

---

-----------------------
Click to see my tag
My tag
SNAFU'ed? Turn the Page! :D