Gentlemen, I have a problem... my BOINC doesn't jump between seti and climateprediction or einstein... in preferences, I scheduled this jump every 60 minutes,(default) but nothing. Somebody have experience about it? thanks in advance!

---

Please exit BOINC, then restart it. Then copy your messages from the Messages tab in Boinc Manager and post them here.
Or check for yourself if you see any line like "running in earliest deadline first mode because your computer is overcommitted".

---

Please exit BOINC, then restart it. Then copy your messages from the Messages tab in Boinc Manager and post them here.
Or check for yourself if you see any line like "running in earliest deadline first mode because your computer is overcommitted".

23/01/06 22:38:07||Starting BOINC client version 4.45 for windows_intelx86
23/01/06 22:38:07||Data directory: C:\\ARCHIVOS DE PROGRAMA\\BOINC
23/01/06 22:38:08|SETI@home|Computer ID: 1768077; location: home; project prefs: home
23/01/06 22:38:08|Predictor @ Home|Computer ID: 211648; location: home; project prefs: default
23/01/06 22:38:08|Einstein@Home|Computer ID: 519492; location: home; project prefs: default
23/01/06 22:38:08||General prefs: from SETI@home (last modified 2006-01-22 22:35:39)
23/01/06 22:38:08||General prefs: no separate prefs for home; using your defaults
23/01/06 22:38:08||Remote control not allowed; using loopback address
23/01/06 22:38:08|Predictor @ Home|Resuming computation for result h0015B_1_25273_2 using mfoldB125 version 4.28
23/01/06 22:38:09||Suspending work fetch because computer is overcommitted.
23/01/06 22:38:09||Using earliest-deadline-first scheduling because computer is overcommitted.
23/01/06 22:38:09|SETI@home|Deferring communication with project for 7 minutes and 36 seconds

Must I understand that I have too many jobs in my old computer?? :-((

thanks

---

Must I understand that I have too many jobs in my old computer?? :-((

In a way, yes. But nothing to worry. It's a feature, not a fault. With EDF BOINC tries to finish any WU within deadline.

Read about the EDF function in the BOINC-Wiki.

BTW: BOINC often only thinks it has to panic, as the remaining crunching time still is not very preciely measured. So, after some time, it may easily decide that the risk of missing a deadline is over, and goes back to normal.

:-)= Greybeard

---

All about BOINC: BOINC-Wiki (by Paul D. Buck)

Thanks a lot!!!

I'm a beginner in this bussiness, and there are thousands of thinks tolearn in BOINC-WIKI!

Best regards, Albert

---

I must say...

BTW: BOINC often only thinks it has to panic, as the remaining crunching time still is not very preciely measured. So, after some time, it may easily decide that the risk of missing a deadline is over, and goes back to normal.

BOINC version 4.45 does not do this. It doesn't "learn" from previously run work units how long they run. If you can, please update to Boinc 5.2.13 to get this behaviour.

---

please update to Boinc 5.2.13 to get this behaviour. [/quote]

OK. I will try asp!

Thanks and regards, Albert

---

I must say...

No problem, you're perfectly right (as usual :-)= ).

What I meant, however, was not the 'learning' function of BOINC, but the fact that at a certain point BOINC calculates swiftly dwindling 'time to completion' (older versions even more than 5.2.x), such as did SetiQue in Classic. And when this value drops below the 'critical time', BOINC returns to normal.

:-)= Greybeard

---

All about BOINC: BOINC-Wiki (by Paul D. Buck)

You're perfectly right as well. Either there were two ways of reading the first statement, or I misread it completely. I bet I know which it was. ;)

---