Questions and Answers :
GPU applications :
Cuda Units working on High priority
Message board moderation
Author | Message |
---|---|
Dorsilfin Send message Joined: 28 Jul 08 Posts: 69 Credit: 4,484,890 RAC: 0 |
Since I started running the new Boinc version last night. All the WU's are running in High priority and are only downloading 20 at a time. It isnt allowing me to que up more work then that, and I go through the stack of 20 very quickly. Any suggestions? |
Nighthawk[TECH] Send message Joined: 7 May 01 Posts: 5 Credit: 2,078,360 RAC: 0 |
I believe the issue lies in a poor estimation of how long each WU will take. Using the "show overall view" portion of BOINClogX shows completion estimates that range from 250hrs to 850hrs for regular MB workunits. Even though the estimate in BOINC manager says 0:00:00, I think the backend is using the estimates displayed by BOINClogX. The client then thinks that the WU are high priority because they will not be completed before the deadline, and promotes them, plus it refuses to get more work because it thinks it has plenty. I don't have a solution, just an explanation, but I hope one is found soon, as S@H has taken over BOINC with these high-priority WU's and I am racking up huge LTD in my other projects. |
Geek@Play Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 |
I have been using Boinc 6.4.5 to crunch down my cache in anticipation of installing a cuda enabled GPU. Boinc has been crunching in EDF mode for 48 hours now and this is without an NVIDIA GPU installed. Something strange about this version of Boinc! The bad thing is that all the AP work is not being done because they are not due for 30 days or so. Boinc....Boinc....Boinc....Boinc.... |
Euan Holton Send message Joined: 4 Sep 99 Posts: 65 Credit: 17,441,343 RAC: 0 |
Go to the list of your computers in your account, and check out the CUDA host's Task Duration Correction Factor. When I started processing CUDA units, mine got set to a very high level (100 I think, my main box running 'normal' optimised apps has a value of 0.14). That's the source of the problem, I think, as I believe that value is used as part of the calculations on how long it'll take to process each work unit. |
Sergej O. S. Send message Joined: 29 Oct 08 Posts: 123 Credit: 44,886 RAC: 0 |
Thanks. So, I totally exit BOINC and changed <duration_correction_factor>81.168666 in my client_state.xml file to 0.3 (guessed time for unptimized applications on my Q6600) and now BOINC work in usual priority and even got new yummu tasks. |
Byron S Goodgame Send message Joined: 16 Jan 06 Posts: 1145 Credit: 3,936,993 RAC: 0 |
|
©2025 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.