I read, that in BOINC >= V6.1.x the function RRI is enabled. [cc_config.xml]

How it work on Multi-Core machines?

On my QX6700 (4 x Core) I have sometimes a bunch of uploads.
[To be on the sure side, the report must be ~ 60 sec. after upload. (delayed RRI)]
So the report will be done really after the last upload, or will be activated after the first upload of the bunch?

So it can happen that a report will be done < 60 seconds after upload?

The RRI-function count really after every upload ~ 60 seconds?


OR, the report is really immediately, maybe 5 seconds after upload?

---

Not entirely correct. RRI is only enabled on Crunch3r's BOINC, which he had labeled v6.1.0. All standard version of BOINC in the official tree (6.2.x, 6.3.x) do not have RRI enabled.

Not entirely correct. RRI is only enabled on Crunch3r's BOINC, which he had labeled v6.1.0. All standard version of BOINC in the official tree (6.2.x, 6.3.x) do not have RRI enabled.

You can enable it through cc_config.xml, Charlie. Since 5.10.45 ...

The report will be done according to the last deferral time that was given since the upload happened. On some projects 7 seconds, on others a minute.

---

Ohh please in easy english words for the not motherlanguage-english-spoken.. ;-D

For example:

[hh:mm:ss]

10:22:10 - 1. upload [counting the time here?]
10:22:20 - 2. upload
10:22:30 - 3. upload
10:22:40 - 4. upload [or counting the time here?]

When the report at SETI@home?

At 10:23:10 ? [30 sec. after last upload]
Or at 10:23:40 ? [60 sec. after last upload]

I see this bunch of uploads often at my Quad-Core-rig..

---

It still depends on the last deferral time that was given to BOINC by the project scheduler (or in case it can't contact the scheduler, the internal incrementing deferral time).

But it's pretty fast on my system. 2 seconds to 5 seconds between uploading and reporting.

---

It still depends on the last deferral time that was given to BOINC by the project scheduler (or in case it can't contact the scheduler, the internal incrementing deferral time).

But it's pretty fast on my system. 2 seconds to 5 seconds between uploading and reporting.

2 to 5 seconds at SETI@home?

Uhh.. that's too early..
If you have the report so immediately at SETI@home.. you will get 'validate errors'..

They didn't know that as they enabled this function?

Maybe it's possible that the programmer could do it like:

10:22:10 - 1. upload
10:22:20 - 2. upload
10:22:30 - 3. upload
10:22:40 - 4. upload [counting the time here]

Report at 10:23:40 . [60 sec. after last upload]

So after every upload the client count the 60 seconds.
If an other upload will come in this 60 seconds, the client will start the '60 sec. countdown' again.

So the SETI@home cruncher are protected for 'validate errors'..

---

If you have the report so immediately at SETI@home.. you will get 'validate errors'..

They didn't know that as they enabled this function?

It isn't re-enabled to please Seti. It's re-enabled to allow you to report quick enough for WCG to be inside their daily backups. If it gives you problems for Seti... don't use it.

then again, no the 2 to 5 seconds was for Primegrid. I just checked my log and see that while I was still crunching for Seti on this computer it took a mere 13 seconds between having uploaded and being reported. Never had a problem.

---