LHC@home

You know what is fun? Go into the client_state.xml file and delete the negative signs from the debt values and then watch the scheduler freak out for a while as it tries to make all the values add up to zero again.

:)

I like that... Might be fun to enter some huge numbers too... Probably won't hurt anything that reformatting the hard drive won't cure ;)

---

Immediately, the caches filled again upto normal values (and for the record "Connect to Network every X days" equals "Set local Cache size to X days worth of work" (which more or less will work out, depending on how accurate BOINC guesstimated the machine's performance)

I guess it depends on what you mean "more or less". It doesn't seem to work the other way though. when you initally get work, all seems to work as you describe. But, after a time, some of the work has been done... the local cache doesn't get replenished until the next scheduled connect. There has been lots of discussion on various message boards about the need of separating the two functions. I seem to remember a long time ago that there were two settings, but I could be wrong. In the scheme of things, I think it's not worth worrying about -- it works pretty well now.

Looks like I'll just wait until manually seeing LHC alive again, then temporarily switching LHC back on.

That's what I do. I do it mostly to keep from getting those messages "no new work... backing off for 1 minute" though.

---

what is the downside of just setting the "connect to time" to 10 days and letting things run?

---

That makes as much sense as anything.

Because it definitely is wrong. My switch time is 120 mins and my LTD are bigger than +-7200. I think Steve mixed LTD and STD. LTD has no influence in how much work is asked for but only in the decision if work is asked for. And to keep track of "long term debt" it must keep bigger values.

Norbert

If you force it to get more work and cause boinc to go into EDF, yes it can go beyond the the values that I stated. But if you leave it alone then what i said is true.

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

That makes as much sense as anything.

Because it definitely is wrong. My switch time is 120 mins and my LTD are bigger than +-7200. I think Steve mixed LTD and STD. LTD has no influence in how much work is asked for but only in the decision if work is asked for. And to keep track of "long term debt" it must keep bigger values.

Norbert

If you force it to get more work and cause boinc to go into EDF, yes it can go beyond the the values that I stated. But if you leave it alone then what i said is true.

I don't get it - I have much larger values...
see below - from BoincDV

PRJ: ROSETTA@HO STD: -86400.000000 LTD: -291355.970175 RSRC: 1 -------------------------------
PRJ: EINSTEIN@H STD: 0.000000 LTD: -291177.619805 RSRC: 1 -------------------------------
PRJ: LHC@HOME STD: 0.000000 LTD: 260828.410659 RSRC: 10000000 -------------------------------
PRJ: SZTAKIDESK STD: 86400.000000 LTD: 286210.923153 RSRC: 100000 -------------------------------
PRJ: PRIMEGRID STD: 0.000000 LTD: 35494.256168 RSRC: 1 -------------------------------

---

If you force it to get more work and cause boinc to go into EDF, yes it can go beyond the the values that I stated. But if you leave it alone then what i said is true.

The bug of the server side scheduler forces Boinc into EDF all by itself. (The bug is, that the clients asks for work in wall time, e.g "I need work for one day", and the server sends work in CPU time "I give you 24 hours of work [12 hours if the computer runs only half time for Boinc]" ignoring the ressource share of the other projects.)

Norbert

---