Hello,

I have always noticed that my (traditional, i.e. genuine) BOINC client is (both on Linux and Windows) very inclined to complete a given task, then wait to submit it. I guess that it waits because of a given timing, or something like this.
The problem is that given credits are often computed on a ``time to compute the task'' basis, aren't they? Thus, I think that I would have (slightly) higher credits if I directly click on ``Update'' than if I wait BOINC client to make the automatic update with the corresponding project.

Am I right? I think that this answer is more important if you compute for lots of projects.

Thanks.

---

See http://www.student.montefiore.ulg.ac.be/~merciadri/ for more pieces of info.

Please read this post.

you should look at the Boinc FAQ about the client... it has a deadline and that deadline depends on the project..... you have a option in the boinc client to connect every so often to report, and such...

Please read this post.

I read it, but it is not my case, as it reports after only a little time.

you should look at the Boinc FAQ about the client... it has a deadline and that deadline depends on the project..... you have a option in the boinc client to connect every so often to report, and such...

Yeah, but my question was about the influence of the time between the task's report and its download.

Please read this post.

I read it, but it is not my case, as it reports after only a little time.

you should look at the Boinc FAQ about the client... it has a deadline and that deadline depends on the project..... you have a option in the boinc client to connect every so often to report, and such...

Yeah, but my question was about the influence of the time between the task's report and its download.

I personally don't know of any projects that gives different credits based on how long it takes to return work, as long as its done before the deadline. If there is such a project then the question is best posted in its forum.
Boinc is design to upload work immediately and try to report multiple WU at the same time to reduce load on the database.
from a JM7 post, reports occur

1) 24 hours before deadline
2) Connect every X before deadline.
3) Immediately on completion of upload if later than 1 or 2.
4) 24 hours after completion.
5) On a work request
6) On an account manager request.
7) On a trickle up request (CPDN only as far as I know).
8) On a trickle down request (none that I know about).
9) After a project specified time with no contact.
10) When the user hits the update button.

EDIT: You could also ask if they have implemented item 9 on the above list to force a report.

GPUGrid is currently offering a 25% 'bonus' for reporting CUDA tasks within two days, instead of the five days allowed by their deadlines.

But they have also implemented regular scheduler (server) connections - item (9) in John's list - so no special action is needed by the user to get the results in quickly.

Please read this post.

I read it, but it is not my case, as it reports after only a little time.

you should look at the Boinc FAQ about the client... it has a deadline and that deadline depends on the project..... you have a option in the boinc client to connect every so often to report, and such...

Yeah, but my question was about the influence of the time between the task's report and its download.

I personally don't know of any projects that gives different credits based on how long it takes to return work, as long as its done before the deadline. If there is such a project then the question is best posted in its forum.
Boinc is design to upload work immediately and try to report multiple WU at the same time to reduce load on the database.
from a JM7 post, reports occur

1) 24 hours before deadline
2) Connect every X before deadline.
3) Immediately on completion of upload if later than 1 or 2.
4) 24 hours after completion.
5) On a work request
6) On an account manager request.
7) On a trickle up request (CPDN only as far as I know).
8) On a trickle down request (none that I know about).
9) After a project specified time with no contact.
10) When the user hits the update button.

EDIT: You could also ask if they have implemented item 9 on the above list to force a report.

Okay. According to this list, my situation is normal. But it has an influence in some given projects, hasn't it? Thanks.

There is a debug command that will cause work to report immediately after completion, but I've never used it and having been up all night, I'm to sleepy to look it up.

Maybe someone else could post the instructions.

There is a debug command that will cause work to report immediately after completion, but I've never used it and having been up all night, I'm to sleepy to look it up.

Maybe someone else could post the instructions.

I know where it is, but I'll only bother posting it if someone can demonstrate a real need: as AB says, it's intended for debug use only, and can cause unwanted extra strain (and even validation errors) on projects where speed is not important.

Altogether, it's best to leave these issues to the projects: like GPUGrid, if they need their own results back quickly, they have the tools available at their end to make it happen - without imposing a global solution on all the other projects attached to your computer.

I do not find it very interesting for the reasons given by Richard Haselgrove (I agree with him). Anyway, I am still aware for other answers.

Thanks.