Another setting instead of Additional work buffer |
![]() |
| log in |
Questions and Answers : Wish list : Another setting instead of Additional work buffer
| Author | Message |
|---|---|
|
What I do when the CUDA completion time is way out is to change the <flops></flops> number in the app_info.xml file. When I started my flops was 3.000.000.000, but since BOINC keeps recalculate the completion time I now have it set to 10.000.000.000 flops after I have changed it several times. The finishing time isn't that important I think, problem is that the additional work buffer setting gets affected. | |
| ID: 893122 · | |
What I do when the CUDA completion time is way out is to change the <flops></flops> number in the app_info.xml file. When I started my flops was 3.000.000.000, but since BOINC keeps recalculate the completion time I now have it set to 10.000.000.000 flops after I have changed it several times. The finishing time isn't that important I think, problem is that the additional work buffer setting gets affected. Because there is only one duration_correction_factor per project. The plan is to (eventually) make it one DCF per application. ____________ BOINC WIKI | |
| ID: 893125 · | |
Questions and Answers : Wish list : Another setting instead of Additional work buffer
| Copyright © 2013 University of California |