Message boards : Questions and problems : Settings to not report tasks
Message board moderation
Author | Message |
---|---|
Send message Joined: 12 Mar 15 Posts: 6 ![]() |
I'm trying to do a bit of a research on the projects and I would like to know if there is any way for the client to not report tasks. I thought about disabling network communications, but seeing as I want it to download more WUs if the queue empties, as well as managing the client remotely, that isn't an option. Any ideas? |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
Suspending network activity doesn't block remote management - it only stops internet activity such as uploads, downloads and contacting project servers. Perhaps the wording is misleading. There's no way to request new work from the project you're researching without reporting completed (i.e. uploaded) work - 'request' and 'report' are combined into a single scheduler interaction. The only way I know of is to suspend network activity - having first downloaded as much work as the project allows. You could possibly do something sneaky with the host network settings (re-direct the upload url to a non-existent IP address, perhaps), which would allow work requests to continue for a while - but even then, BOINC would notice that the uploads weren't getting through, and stop requesting new work after a while (a high ncpus, and a low max_concurrent, might put off that day as long as possible). |
![]() ![]() Send message Joined: 23 Feb 08 Posts: 2524 ![]() |
Not sure what you want to research. If you aren't interested in ever reporting the tasks, or if you want to pick when to report them. If you never want to report them, you can always delete the files from your hard drive. If the project has resend lost tasks on, however, they will keep coming back. Eventually BOINC will notice that you aren't getting credit for the work and will stop sending any. There are time of day restrictions in the preferences and also upload data speed throttles. Depending on the project's finished file size, you may be able to set the throttle so slow and the available time so narrow that only a single task can report before the window closes. As you can leave download speed wide open, you should still get work units. But again eventually BOINC will notice you aren't getting credit and stop sending work. If you need some other method, then you may need to download the client source code and modify to fit your requirement. ![]() |
Send message Joined: 12 Mar 15 Posts: 6 ![]() |
Not sure what you want to research. If you aren't interested in ever reporting the tasks, or if you want to pick when to report them. I do intend to report tasks before deadlines; however, I want to be able to control when to do it. The throttle method seems good on paper, but by limiting network usage, I wouldn't be able to download new WUs, should the buffer end during a time where communications aren't allowed. The obvious solution would be to use a large buffer size and call it a day. But: 1- If the WUs take longer than expected, deadlines may fail; 2- if the WUs run faster than expected, there won't be enough of them. |
Send message Joined: 6 Jul 10 Posts: 585 ![]() |
The design of BOINC is to buffer as much as till the next allowed connection. If completed work is not allowed/cannot upload, the client stops fetching work if there are more than 2 results per core in the transfer tab. E.g if you have 9 complted jobs queud on a quad for one project, its considered pointless to get more work for that project until the upload issue is resolved. Coelum Non Animum Mutant, Qui Trans Mare Currunt |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.