Last nigth i upgraded from 5.10.13 to 5.10.20 (recomended).

Since that i have a problem... The completed WU's are uploaded correctly, but don't reported automatically as with the 5.10.13. The WU's are stay in 'ready to report' until I press manually the 'update' button.

They have changed to report rules . It is in the changelogs a couple of posts down. It can now take up to a day before a result is reported.

I see in the change log:

- client: allow up to a day (rather than work_buf_min()) to elapsed between completing a result and reporting it.

What determines the "up to a day" value of the delay?

---

What determines the "up to a day" value of the delay?

There are 4 or 5 reasons why the client will contact the server (to get more work, for example). If none of those reasons occurs, then the client will wait up to a maximum of 24 hours before reporting.

This change occurred with 5.10.14. With 5.10.13 and earlier, setting your connect time to 0 provides the same behavior as Return Results Immediately.

---

Dublin, California
Team: SETI.USA

What determines the "up to a day" value of the delay?

There are 4 or 5 reasons why the client will contact the server (to get more work, for example). If none of those reasons occurs, then the client will wait up to a maximum of 24 hours before reporting.

This change occurred with 5.10.14. With 5.10.13 and earlier, setting your connect time to 0 provides the same behavior as Return Results Immediately.

I have this parameter set to 0. If I'm not wrong, if you don't return results, no more work is allowed to you until then... And that means what who has set to 0 this parameter only can have new WU's every 24 hours... isn't it?

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

What determines the "up to a day" value of the delay?

There are 4 or 5 reasons why the client will contact the server (to get more work, for example). If none of those reasons occurs, then the client will wait up to a maximum of 24 hours before reporting.

This change occurred with 5.10.14. With 5.10.13 and earlier, setting your connect time to 0 provides the same behavior as Return Results Immediately.

I have this parameter set to 0. If I'm not wrong, if you don't return results, no more work is allowed to you until then... And that means what who has set to 0 this parameter only can have new WU's every 24 hours... isn't it?

If you set connect time to 0, then you should also set "Maintain enough work for an additional" to manage the amount of work downloaded in your queue. I generally use .1 or .2 days.

---

Dublin, California
Team: SETI.USA

What determines the "up to a day" value of the delay?

There are 4 or 5 reasons why the client will contact the server (to get more work, for example). If none of those reasons occurs, then the client will wait up to a maximum of 24 hours before reporting.

This change occurred with 5.10.14. With 5.10.13 and earlier, setting your connect time to 0 provides the same behavior as Return Results Immediately.

I have this parameter set to 0. If I'm not wrong, if you don't return results, no more work is allowed to you until then... And that means what who has set to 0 this parameter only can have new WU's every 24 hours... isn't it?

If you set connect time to 0, then you should also set "Maintain enough work for an additional" to manage the amount of work downloaded in your queue. I generally use .1 or .2 days.

I know. I have a few days of work on my cache... I was thinking, if you have only .1 or .2 extra days and your WU's are procesed faster than expected, in a few hours (or minutes) by diferent circumstances (as usual), you don't have more work until 24 hours later... I think in the 'set and forget' users...

I think that give to them a lot of time without work to process... A waste of time for the science... Don't believe...?

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

What determines the "up to a day" value of the delay?

There are 4 or 5 reasons why the client will contact the server (to get more work, for example). If none of those reasons occurs, then the client will wait up to a maximum of 24 hours before reporting.

This change occurred with 5.10.14. With 5.10.13 and earlier, setting your connect time to 0 provides the same behavior as Return Results Immediately.

I have this parameter set to 0. If I'm not wrong, if you don't return results, no more work is allowed to you until then... And that means what who has set to 0 this parameter only can have new WU's every 24 hours... isn't it?

If you set connect time to 0, then you should also set "Maintain enough work for an additional" to manage the amount of work downloaded in your queue. I generally use .1 or .2 days.

I know. I have a few days of work on my cache... I was thinking, if you have only .1 or .2 extra days and your WU's are procesed faster than expected, in a few hours (or minutes) by diferent circumstances (as usual), you don't have more work until 24 hours later... I think in the 'set and forget' users...

I think that give to them a lot of time without work to process... A waste of time for the science... Don't believe...?

Boinc will try to contact the server for more work as your cache runs down, it will not wait for 24 hours if you need work and your connect time is set to a very low value.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

What determines the "up to a day" value of the delay?

There are 4 or 5 reasons why the client will contact the server (to get more work, for example). If none of those reasons occurs, then the client will wait up to a maximum of 24 hours before reporting.

This change occurred with 5.10.14. With 5.10.13 and earlier, setting your connect time to 0 provides the same behavior as Return Results Immediately.

I have this parameter set to 0. If I'm not wrong, if you don't return results, no more work is allowed to you until then... And that means what who has set to 0 this parameter only can have new WU's every 24 hours... isn't it?

If you set connect time to 0, then you should also set "Maintain enough work for an additional" to manage the amount of work downloaded in your queue. I generally use .1 or .2 days.

I know. I have a few days of work on my cache... I was thinking, if you have only .1 or .2 extra days and your WU's are procesed faster than expected, in a few hours (or minutes) by diferent circumstances (as usual), you don't have more work until 24 hours later... I think in the 'set and forget' users...

I think that give to them a lot of time without work to process... A waste of time for the science... Don't believe...?

Boinc will try to contact the server for more work as your cache runs down, it will not wait for 24 hours if you need work and your connect time is set to a very low value.

Hi Msattler!

I think, in the new 5.10.20 version, BOINC wait 24 hours...

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

What determines the "up to a day" value of the delay?

There are 4 or 5 reasons why the client will contact the server (to get more work, for example). If none of those reasons occurs, then the client will wait up to a maximum of 24 hours before reporting.

This change occurred with 5.10.14. With 5.10.13 and earlier, setting your connect time to 0 provides the same behavior as Return Results Immediately.

I have this parameter set to 0. If I'm not wrong, if you don't return results, no more work is allowed to you until then... And that means what who has set to 0 this parameter only can have new WU's every 24 hours... isn't it?

If you set connect time to 0, then you should also set "Maintain enough work for an additional" to manage the amount of work downloaded in your queue. I generally use .1 or .2 days.

I know. I have a few days of work on my cache... I was thinking, if you have only .1 or .2 extra days and your WU's are procesed faster than expected, in a few hours (or minutes) by diferent circumstances (as usual), you don't have more work until 24 hours later... I think in the 'set and forget' users...

I think that give to them a lot of time without work to process... A waste of time for the science... Don't believe...?

Ah, I misunderstood your question. No, BOINC will not wait 24 hours to get more work when it runs out. This is true for both .13- and .14+ versions.

---

Dublin, California
Team: SETI.USA

What determines the "up to a day" value of the delay?

There are 4 or 5 reasons why the client will contact the server (to get more work, for example). If none of those reasons occurs, then the client will wait up to a maximum of 24 hours before reporting.

This change occurred with 5.10.14. With 5.10.13 and earlier, setting your connect time to 0 provides the same behavior as Return Results Immediately.

I have this parameter set to 0. If I'm not wrong, if you don't return results, no more work is allowed to you until then... And that means what who has set to 0 this parameter only can have new WU's every 24 hours... isn't it?

If you set connect time to 0, then you should also set "Maintain enough work for an additional" to manage the amount of work downloaded in your queue. I generally use .1 or .2 days.

I know. I have a few days of work on my cache... I was thinking, if you have only .1 or .2 extra days and your WU's are procesed faster than expected, in a few hours (or minutes) by diferent circumstances (as usual), you don't have more work until 24 hours later... I think in the 'set and forget' users...

I think that give to them a lot of time without work to process... A waste of time for the science... Don't believe...?

Ah, I misunderstood your question. No, BOINC will not wait 24 hours to get more work when it runs out. This is true for both .13- and .14+ versions.

Aaah... I was thinking (reading the changelog) this feature was implemented in the 5.10.20 too... Sorry...

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

Aaah... I was thinking (reading the changelog) this feature was implemented in the 5.10.20 too... Sorry...

I think the feature IS in 5.10.20, but if I understand it correctly, it means that Boinc CAN wait for up to 24 hours to report results, not that it MUST wait 24 hours. If you need work and your connect setting allows it, Boinc will still ask for work. If you do not need work, it may wait up to 24 hours before it connects just to report completed results.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I think, in the new 5.10.20 version, BOINC wait 24 hours...

BOINC will wait 24 hours before reporting, if there's no other reason to connect earlier, like asking for more work...

Asking for more work will happen just like before, every time amont of cached work drops below cache-setting. The only difference is:

"cache-size" = "connect every N days" + "Maintain enough work for an additional N days".

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

Just posted my opinion of this new 'feature' over on the BOINC CC board.

here

Alinator

blimey, more updates than me having hot lunches, wots with the servers, everytime i seem to log onto this site it always seems to be down?

---

the truth is out there

blimey, more updates than me having hot lunches, wots with the servers, everytime i seem to log onto this site it always seems to be down?

wow a new splash screen for the installation and new system tray icon, is there a screensaver for vista?

---

the truth is out there

blimey, more updates than me having hot lunches

You do know that you don't have to update to every new version (it's good practice in general, but it isn't required), right?

, wots with the servers, everytime i seem to log onto this site it always seems to be down?

SETI@Home is, and always has been a work in progress. Progress is good.

---

blimey, more updates than me having hot lunches

You do know that you don't have to update to every new version (it's good practice in general, but it isn't required), right?

What's with the servers, everytime I seem to log onto this site it always seems to be down?

SETI@Home is, and always has been a work in progress. Progress is good.

Yeah progress. As long as It isn't required to upgrade.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I'm testing the new '24 hours' feature since two days... My cache is decreasing and BOINC don't ask for new work... Only reports every 24 hours after complete next WU before last connect... I have set the preferences 0 days to connect and 10 days of extra work...

I send you more news tomorrow after connecting, but this appears BOINC new version don´t request new work until the cache is empty...

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

I think, in the new 5.10.20 version, BOINC wait 24 hours...

BOINC will wait 24 hours before reporting, if there's no other reason to connect earlier, like asking for more work...

Asking for more work will happen just like before, every time amont of cached work drops below cache-setting. The only difference is:

"cache-size" = "connect every N days" + "Maintain enough work for an additional N days".

In 5.10.20 work will be reported at the first of:

1) More work is needed (a work fetch is generated).
2) 24 hours before deadline.
3) Connect interval (Connect every X) before deadline.
4) 24 hours after completion of a task.
5) A manual connection.

Batching things reduces the load on the database server.

---

BOINC WIKI

I'm testing the new '24 hours' feature since two days... My cache is decreasing and BOINC don't ask for new work... Only reports every 24 hours after complete next WU before last connect... I have set the preferences 0 days to connect and 10 days of extra work...

I send you more news tomorrow after connecting, but this appears BOINC new version don´t request new work until the cache is empty...

Stone the crows!! That's where all the WU's went - 10 day's worth on a C2D.

I'm testing the new '24 hours' feature since two days... My cache is decreasing and BOINC don't ask for new work... Only reports every 24 hours after complete next WU before last connect... I have set the preferences 0 days to connect and 10 days of extra work...

I send you more news tomorrow after connecting, but this appears BOINC new version don´t request new work until the cache is empty...

Stone the crows!! That's where all the WU's went - 10 day's worth on a C2D.

No... I have 10 days set since a month or two and when i have 5.10.13, BOING only request a few WU's every time when it needed to complete the cache...

If the new version runs like apeears... when BOINC decides to request more WU's my cache could be empty and that means a lot of WU's to request...

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)