Plan to do major dis-assemble my families computers next week, install new parts, swap components around and install new OS on one of them. So I have set to NNT,
Ver 7.0.25(x64) on 64 bit win7.

The question is why does it now immediately report after each task is completed?

its a feature... dont like it either, imho since 6.12.3x (something around)

---

- Performance is not a simple linear function of the number of CPUs you throw at the problem. -

I think this may be due to the numerous and constant threads started on "when will my wotk be sent back" Now we know. Immediately and if it doesn't there might be a problem somewhere

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

It was added from 6.12.34 as a means of making sure people getting ready to shut down systems could get their work reported ASAP. A lot of people set no new tasks before they head off on a holiday and so you'd have all that work getting timed out.

---

BOINC blog

There is a CC_config.xml option <report_results_immediately>. While previous versions the default would be 0 and 1 would be used to enabled it. Perhaps it can still be used in order to disable the immediate sending of results for you.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Changeset [trac]changeset:23571[/trac] added just that feature. I don't know why, but there was a change earlier in the month which allowed projects to have each task reported immediately, so I guess Dr. Anderson was in a mood to have clients contact projects very often.

                                                                   Joe

If report immediately is not set to 1, what determines when they are reported?

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

If report immediately is not set to 1, what determines when they are reported?

The default settings coded into the application. Just like all of the other variables when they are not entered into the cc_config.xml, or when the file is not present.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

copied from Ageless:
Reporting, if:

1) 24 hours before deadline.
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message.
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.
11) Report immediately every task, if "No new Task" is set.
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)

and the "report_immediately" setting in the cc_config have no influence on NNT reporting. Already tested :-)

---

- Performance is not a simple linear function of the number of CPUs you throw at the problem. -