Message boards : Graphics cards (GPUs) : Anomalies in the speed of processing WU
Author | Message |
---|---|
Whether somebody can explain me why this sample was counted by GTX 280 in the time of 25145s but through GTX 260 in 80785s. | |
ID: 10179 | Rating: 0 | rate: / Reply Quote | |
There is a bug I have been chasing and can hit many versions of the BOINC Client but seemed to be especially bad in 6.6.20... this bug causes tasks to run long ... up to 2 to 4 times as long as expected. One participant was running AP tasks on his CPU and was hit ... I get it with GPU Grid tasks ... and that may be what happened here ... | |
ID: 10188 | Rating: 0 | rate: / Reply Quote | |
I don't know what is going on.... | |
ID: 10194 | Rating: 0 | rate: / Reply Quote | |
I don't know what is going on.... Try stopping and restarting BOINC, use advanced menu and stop the connected client, stop the manager and restart and see if the completion speed picks back up. {edit} length and to add: We may be seeing the evidence of my contention that the long running task issue of 6.6.20 may not be fully dead... I have no real hint as to what is happening and forwarded my notes such as they are to BOINC Alpha where I saw this happen to me on 6.6.28 just the other day ... only for me it was a pair of tasks running for 24 hours ... each ... normal time is like yours, about 6 hours and change ... ugh! | |
ID: 10198 | Rating: 0 | rate: / Reply Quote | |
Problem: as far as I know in the case of "the 6.6.20"-bug the runtime and time per step is displayed as normal, which is not the case here. Is this correct that it use Cuda 1.3? It doesn't say so. It says your card has hardware capability level 1.3, which is indeed correct. MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 10206 | Rating: 0 | rate: / Reply Quote | |
Hi, | |
ID: 10208 | Rating: 0 | rate: / Reply Quote | |
Oh, so we do know what the user was doing :) | |
ID: 10211 | Rating: 0 | rate: / Reply Quote | |
After finished last WU i restart project.... | |
ID: 10213 | Rating: 0 | rate: / Reply Quote | |
Gotta remember to check for that lower clock mode the next time I see a slow task ... | |
ID: 10218 | Rating: 0 | rate: / Reply Quote | |
It happend to me too with 6.6.28. | |
ID: 10227 | Rating: 0 | rate: / Reply Quote | |
I don't think Thomasz' problem is hanging WUs, it looks like they're just rather slow. Trying 6.5.0 wouldn't hurt, though.. just to exclude any 6.6.x strangeness. | |
ID: 10234 | Rating: 0 | rate: / Reply Quote | |
WTF... | |
ID: 10247 | Rating: 0 | rate: / Reply Quote | |
Can you test if using boinc 6.5.0 does run more smooth then the one your using now, just to remember you this older version will not show the actual time but only the cpu time. | |
ID: 10250 | Rating: 0 | rate: / Reply Quote | |
WTF... This is one of the problems I am chasing... ETA and I are having a debate (sometimes on the side so you don't see it) about how real this is, how common, and on and on and on ... 6.6.20 was REAL bad with this error (it also affected CPU only tasks with .20 but I was never able to pin down a cause) ... it seems less common with other 6.6.x versions, but it does not appear to be gone... What *I* had suspected it was did not pan out the last time I caught a pair of tasks doing this ... now I need to look at something else the next time I get one ... Question, was this a single GPU system, or did it have multiple GPUs in the box? Two things, next time it happens, see if the GPU has dropped back into a slower clock regime and secondly if it strikes again, usually stopping and restarting BOINC will clear this up... you have to shut down the client, not just close the BOINC Manager ... a reboot will do it too ... As always, if you see one, report as much as you can so we can pin this one down ... | |
ID: 10263 | Rating: 0 | rate: / Reply Quote | |
It's not the WUs. I second trying 6.5.0 and watching the clock speed. Another idea: is someone using the machine? If so it might just be the "run GPU while computer is in use" setting, which is disabled by default in newer BOINC clients. | |
ID: 10273 | Rating: 0 | rate: / Reply Quote | |
hmmm | |
ID: 10284 | Rating: 0 | rate: / Reply Quote | |
When I last updated Boinc (6.6.20 seems to be working fine at the mo and with all the discussion probs best not to update!), it said in the installation wizard that GPU computation wouldn't work if you installed Boinc as a service. | |
ID: 10301 | Rating: 0 | rate: / Reply Quote | |
ExtraTerrestrial Apes | |
ID: 10321 | Rating: 0 | rate: / Reply Quote | |
I also notice, that remote desktop cause error of acemd 6.64.... it crash... That's a known problem, and unfortunately inherent to the way most remote software works (VNC is OK though). Otherwise.. did you fix the 2D clock speed issue? I never had a NV card with power-saving lower 2D clocks, so I can't tell. Try switching the windows power profile? MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 10501 | Rating: 0 | rate: / Reply Quote | |
The easiest way to stop 2D mode is to install ATItool and set the all the clocks at the 3D rate. (Yes ATItool works on nVidia) | |
ID: 10524 | Rating: 0 | rate: / Reply Quote | |
When I last updated Boinc (6.6.20 seems to be working fine at the mo and with all the discussion probs best not to update!), it said in the installation wizard that GPU computation wouldn't work if you installed Boinc as a service. Running as a service (running as a daemon or protected application mode) is a security issue with Vista. As far as I know it works under XP and Linux fine. As for BOINC upgrades there are a few cuda related fixes after 6.6.30 so if you are running windows it might be worthwhile upgrading to 6.6.36. ____________ BOINC blog | |
ID: 10525 | Rating: 0 | rate: / Reply Quote | |
Here is another case, I have 2 gtx295's that usually run a task 10-12 hours. I was supprised to see this yesterday when both had ran for 22 hours and still has 10-20% to go. I'm running 6.6.31 on vista 32bit 4gb ram. | |
ID: 10614 | Rating: 0 | rate: / Reply Quote | |
Here is another case, I have 2 gtx295's that usually run a task 10-12 hours. I was supprised to see this yesterday when both had ran for 22 hours and still has 10-20% to go. I'm running 6.6.31 on vista 32bit 4gb ram. Stop and restart BOINC, make sure the science apps stop too ... simplest way is to reboot... This is the dreaded 6.6.20 issue which though less common on later versions is still there. Worse, a friend actually had it hit him on CPU tasks ... so, it is a core problem that we have no clear idea why it is happening. | |
ID: 10619 | Rating: 0 | rate: / Reply Quote | |
If restarting BOINC doesn't help you could / should check if your GPU dropped to 2D clocks (e.g. with GPU-Z). | |
ID: 10638 | Rating: 0 | rate: / Reply Quote | |
Hi! | |
ID: 10852 | Rating: 0 | rate: / Reply Quote | |
"incorrect function. (0x1) - exit code 1 (0x1)" with the app being terminated at a random code line. It's the most common error and mostly related to GPU-OC or defective hardware, but there can be other reasons as well. | |
ID: 10858 | Rating: 0 | rate: / Reply Quote | |
Message boards : Graphics cards (GPUs) : Anomalies in the speed of processing WU