How to reduce the number of “lost� WU’s

Ziran
Ziran
Joined: 26 Nov 04
Posts: 194
Credit: 356403
RAC: 1626
Topic 188208

Don’t think i have seen any thing about what the project does to reduce this in the forums, so hear goes.

Then the client requests more work from the server, the server checks if the host is likely to finish the requested work before deadline. As part of this i believe the server asks the client how many Einstein WU’s that is already stored on the computer, so it can calculate if the additional requested work is likely to be done before the deadline.

1. My first suggestion is: then the client requests more work, the server first compare how many Einstein WU’s (including unsent results) that is stored on the computer, with how many the database sees it should be. If these numbers don’t mach, the server should compare what WU’s that actually are on the computer against the database. WU’s not found on the computer would then be marked with an error massage so a replacement WU can be sent out to a new host.

This would reduce the number of “ghost� WU’s and WU’s lost then resetting the project. It would also detect WU’s deleted bye the users of 4.2x clients.

2. Then resetting/detaching from the project, the scheduler should be informed that the client has done this so it can recycle the “lost� WU’s.

3. The first time BOINC is installed on a computer a random computer identification number should be generated. This would help detecting if a computer have trouble attaching to the project and there by creating multiple hosts on his account for the same computer. I think I saw a user who had a computer that immediately detached every time he tried to attach to the project. Every time he tried, a WU was recorded as downloaded by the new host.

Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.

John Greer
John Greer
Joined: 11 Feb 05
Posts: 5
Credit: 69038336
RAC: 3

How to reduce the number of “lost� WU’s

YES

Don't you think it would be a good idea, especially for the very long WUs in CPDN, to have a process that would either:
1) allow the user to re-download the WU
or
2) occasionally re-verify that the user still has the WU and if not, either re-download it or mark it reusable for someone else.

Comment viewing options

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