Opened 15 years ago
Last modified 14 years ago
#896 closed Defect
Client issues 'empty' RPC requesting zero work — at Initial Version
| Reported by: | Richard Haselgrove | Owned by: | davea |
|---|---|---|---|
| Priority: | Minor | Milestone: | 6.12 |
| Component: | Client - Work Fetch Policy | Version: | 6.6.28 |
| Keywords: | Cc: |
Description
Description If a client has a CUDA work shortfall, but no CUDA project is fetchable, it may issue a CPU work fetch instead. If there is no CPU shortfall, the work fetch is issued for 0.00 seconds.
For example:
17/04/2009 11:21:51 [wfd] CPU: shortfall 0.00 nidle 0.00 est. delay 0.00
17/04/2009 11:21:51 [wfd] CUDA: shortfall 21420.16 nidle 0.00 est. delay 0.00
17/04/2009 11:21:51 Einstein@Home chosen: CPU minor shortfall
17/04/2009 11:21:51 Einstein@Home [wfd] request: CPU (0.00 sec, 0) CUDA (0.00 sec, 0)
Reproducibility Difficult. Only observed during SETI server crashes, but observed twice during different outages - once with client v6.6.23, and several times with client v6.6.68
Suspect code area Function WORK_FETCH::choose_project() in work_fetch.cpp
There is no "none of the above" escape path to cancel the work fetch if no project with the desired resource is fetchable.
Reporting history On boinc_alpha:
17 Apr 2009, "Work fetch bug in v6.6.23" (with log)
23 Apr 2009, "Fw: Work fetch bug in v6.6.23" (analysis with JM7)
10 May 2009, "Work fetch bug continues in v6.6.28" (7 instances logged)
