Upgraded to 6.4.5 but not seeing any improvement

Message boards : Number crunching : Upgraded to 6.4.5 but not seeing any improvement
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 846161 - Posted: 28 Dec 2008, 22:23:31 UTC - in response to Message 846154.  

OK, that has solved why you are not getting new workunits.

Luke.
Yes, but not how to get some new WUs downloaded. Currently there are 50 WUs in the queue and this host completes them at the rate of at least 32 per day. This means that in about a day and a half the queue will be empty. So, can I repair the Duration Correction Factor by editing some file, or should I reinstall version 6.2.19?

Yes, you can shut down BOINC, edit the <duration_correction_factor> in the client_state.xml file, and restart BOINC. The default value is 1, which should allow you to get more work.

Meanwhile, all the S@H work you have was downloaded before you made the conversion, so BOINC will keep 6.03 and use it to process all those. The first new download should be accompanied by 6.05 and its associated files. Thus, there will still be a delay before you'll see CUDA action, and probably another disturbance in DCF.
                                                           Joe
ID: 846161 · Report as offensive
Profile Steven Meyer
Avatar

Send message
Joined: 24 Mar 08
Posts: 2333
Credit: 3,428,296
RAC: 0
United States
Message 846195 - Posted: 28 Dec 2008, 23:59:05 UTC - in response to Message 846161.  

Yes, you can shut down BOINC, edit the <duration_correction_factor> in the client_state.xml file, and restart BOINC. The default value is 1, which should allow you to get more work.

Meanwhile, all the S@H work you have was downloaded before you made the conversion, so BOINC will keep 6.03 and use it to process all those. The first new download should be accompanied by 6.05 and its associated files. Thus, there will still be a delay before you'll see CUDA action, and probably another disturbance in DCF.
                                                           Joe

OK, I

  • shut down BOINC,
  • edited the client_state.xml file setting <duration_correction_factor> to 1.000000
  • restarted BOINC
  • set SETI@Home to "No new tasks"
  • aborted all the tasks in the queue without any work done so far
  • reset SETI@Home to allow new tasks
  • updated the SETI@Home project

This caused BOINC to request new work and it got 20 new tasks, along with the 6.05 application.

12/28/2008 3:50:10 PM|SETI@home|Sending scheduler request: To fetch work.  Requesting 2359973 seconds of work, reporting 0 completed tasks
12/28/2008 3:50:15 PM|SETI@home|Scheduler request completed: got 20 new tasks
12/28/2008 3:50:17 PM|SETI@home|Started download of setiathome_6.05_windows_intelx86__cuda.exe
...

ID: 846195 · Report as offensive
Previous · 1 · 2

Message boards : Number crunching : Upgraded to 6.4.5 but not seeing any improvement


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.