Can I send a WU back manually?

dkonrade
dkonrade
Joined: 18 Jan 05
Posts: 2
Credit: 29976
RAC: 0
Topic 189209

Can I send a WU back manually I get some that are due one day but computer keeps running the other WU until they are done then sends WU in.

Paul D. Buck
Paul D. Buck
Joined: 17 Jan 05
Posts: 754
Credit: 5385205
RAC: 0

Can I send a WU back manually?

Can I send a WU back manually I get some that are due one day but computer keeps running the other WU until they are done then sends WU in.
Depending on what version you are running, you can suspend projects or work units to force the processing of one or more. I have done this with some LHC@Home work recently as it was "clean-up" and I wanted to get them all done in one day.

So, I suspended the other 4 projects till all of the work was done.

I forget exactly which version added this feature, it was about 4.25 or so. You can access this through the right version of the BOINC Manager, or BOINC Daemon and the third party tool BOINC-View.

Heffed
Heffed
Joined: 18 Jan 05
Posts: 257
Credit: 12368
RAC: 0

Also, if you're feeling up to

Also, if you're feeling up to try the developmental version, (use at own risk) they run a different client side scheduler that helps to ensure that all work gets completed on time. If a WU is dangerously close to it's deadline, the CC goes into 'panic mode' and processes the WU nearing deadline exclusively.

Dandersen/Bsorensen
Dandersen/Bsorensen
Joined: 11 May 05
Posts: 1
Credit: 18672
RAC: 0

I think that what You wants

I think that what You wants is reporting back a "finished" WU.
It seems like it is not reported back, until there is a need for requesting a new work. So half the time every WU are waiting on Your computer. First to wait until processing starts while the proceeding WU are finished. Next the processing are performed and before it is finished a new WU are downloaded to You. The finished workunit are not reported back to central site until a new WU are requested.
You can speed the return of the WU up by choosing the project tab and perform an "update".
By using a low value "0.1" days (2:36 hours) for "communication interval, You can delay the arrival of a new WU until latest moment up till where You are ready to begin processing it.

John McLeod VII
John McLeod VII
Moderator
Joined: 10 Nov 04
Posts: 547
Credit: 632255
RAC: 0

I think that what You wants

Message 11792 in response to message 11791

I think that what You wants is reporting back a "finished" WU.

WUs will report when any of the following occur: The deadline is earlier than 24 hours from now, the daemon requests more work from the project, or there is a manual update.

gravywavy
gravywavy
Joined: 22 Jan 05
Posts: 392
Credit: 68962
RAC: 0

WUs will report when any of

Message 11793 in response to message 11792


WUs will report when any of the following occur: The deadline is earlier than 24 hours from now, the daemon requests more work from the project, or there is a manual update.

providing of course there is a live network connection and that you have not disabled network activity in the BOINC client.

Problems with reporting quite often arise for those without a 24/7 network connection, and those users should do a manual update whenever you have completed wu and the network is up/connected/enabled/etc

If your network is always on it is kinder to the project if you let it do the report at the same time as fetching the next work.

My tip is to adjust the connection interval. When you have an unstarted wu in your machine, how long is it predicted to run for? On my ancient machines this is always around 18hrs, =0.75 days. The truth is they always take longer to run than that, but what is important here is the *predicted* time before the wu has started.

Set the connection interval to just less than that amount. In my case it is set to 0.74 days.

The effect is that when wu 1 finishes, wu 2 starts, and not too long afterwards the client thinks it is running out of work, and asks for wu 3. At the same time it takes advantage of the connection to report wu 1. This means that every wu is reported soon after it finishes, and that most of the time I am holding an unstarted wu on my system instead of usually holding a completed one. The workload for the project is just the same in both cases: it still gets to use one database connection for allocation and report, which is what it wants to do.

~~gravywavy

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.