Tweet
Fix for never-credited wu in the works. New Seti-clients soon.
From Berkeley Technical News:
<blockquote><i>September 12, 2001
We have recently diagnosed a long-standing problem: certain work units never get results returned. There are at least two cases: 1) if a work unit produces a result file larger than 60 KB, the client silently discards the result file and fetches a new work unit; 2) if a work unit has corrupt data, the client immediately discards it. In both cases the user doesn't receive credit for processing the work unit.
Because our server never gets results for these work units, they remain on disk indefinitely, and are sent over and over again to clients. Users aren't getting credit for an increasing fraction of the work units they complete.
As a short-term solution, we are purging old work units from our server. This will hopefully reduce the fraction of "uncredited" work units close to zero. Longer-term, we will fix the client so that it handles large result files correctly. We hope to have this fix in the Unix and command-line versions soon, and in the Windows and Mac versions after that. </i></blockquote>
<blockquote><i>September 12, 2001
We have recently diagnosed a long-standing problem: certain work units never get results returned. There are at least two cases: 1) if a work unit produces a result file larger than 60 KB, the client silently discards the result file and fetches a new work unit; 2) if a work unit has corrupt data, the client immediately discards it. In both cases the user doesn't receive credit for processing the work unit.
Because our server never gets results for these work units, they remain on disk indefinitely, and are sent over and over again to clients. Users aren't getting credit for an increasing fraction of the work units they complete.
As a short-term solution, we are purging old work units from our server. This will hopefully reduce the fraction of "uncredited" work units close to zero. Longer-term, we will fix the client so that it handles large result files correctly. We hope to have this fix in the Unix and command-line versions soon, and in the Windows and Mac versions after that. </i></blockquote>
.
Comment