GT610 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED error on GPU work

Message boards : Number crunching : GT610 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED error on GPU work
Message board moderation

To post messages, you must log in.

AuthorMessage
Alez
Volunteer tester

Send message
Joined: 18 Jul 99
Posts: 8
Credit: 5,455,148
RAC: 0
Anguilla
Message 1381833 - Posted: 16 Jun 2013, 14:51:26 UTC

Since the project has gone over to ver 7 this is just about all I've had on my GT610 gpu. Have been forced to abort all work and set no more work. Have reset the project to no avail and have deleted everything from the project directory so it has a fresh start. Each time I download work they are set as having a run time of @ 9 mins which is never going to happen on this card but it never increases the run time.
It's this computer http://setiathome.berkeley.edu/show_host_detail.php?hostid=6827670

Any ideas what to do ?
ID: 1381833 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1381843 - Posted: 16 Jun 2013, 15:37:33 UTC - in response to Message 1381833.  
Last modified: 16 Jun 2013, 15:38:21 UTC

That machine doesn't just have a GT 610 GPU: it has a GTX 660 Ti as well.

  Device 1: GeForce GTX 660 Ti, 2047 MiB, regsPerBlock 65536
     computeCap 3.0, multiProcs 7 
     pciBusID = 2, pciSlotID = 0
  Device 2: GeForce GT 610, 511 MiB, regsPerBlock 32768
     computeCap 2.1, multiProcs 1 
     pciBusID = 6, pciSlotID = 0

I'm afraid BOINC will be basing those 9 minute (estimated) run times on the predicted speed of the GTX 660 Ti. The difference in the speeds of the two cards (at least x7, from the number of multiProcs, and probably more) is just too wide for BOINC to cope with. Your very fast i7-3770K CPU will also be used, in the early stages at least, to predict the run time for GPU tasks, and again the system is too far out of balance for BOINC to make sense of it.

I assume you're running a different project's tasks on the GTX 660 Ti, and maybe another project again on the AMD Radeon HD 7870/7950/7970 in the same system. If so, you're obviously experienced in fine-tuning BOINC and using its configuration options. If you really want to use the GT 610 to crunch SETI, and to use it in that computer, I suggest you install the new version of the optimised applications you've used in the past, and add a <flops> entry tuned to the speed of the GT 610. Even that might not be enough to fully balance the system.
ID: 1381843 · Report as offensive
Alez
Volunteer tester

Send message
Joined: 18 Jul 99
Posts: 8
Credit: 5,455,148
RAC: 0
Anguilla
Message 1381856 - Posted: 16 Jun 2013, 16:45:22 UTC
Last modified: 16 Jun 2013, 16:53:51 UTC

That's what I thought, will give the lunatics app a pop. Didn't have this problem with ver 6 and as you can see Seti knows it's running the app on the 610. I figured that it would start with a wildly optimistic time but as Seti is only run on the 610 and not on either of the fast cards I would have expected that the run times would have increased to realistic values.
I also run milkyway this way with the 610 taking @34 mins per unit and the ATI 7970 taking 35 secs and the schedular copes with this. Don't know why the run times have never changed on Seti from 9 mins for ver 7 yet I was able to successfully complete astropulse units on this card which take longer to run.
As I never managed to complete a ver 7 unit on the card any idea roughly how long it would take so I can work out the flops rather than trying trial and error. Guess I could start at @ 10 x slower than the 660 ti's.
ID: 1381856 · Report as offensive
Alez
Volunteer tester

Send message
Joined: 18 Jul 99
Posts: 8
Credit: 5,455,148
RAC: 0
Anguilla
Message 1382580 - Posted: 18 Jun 2013, 23:15:09 UTC

upgraded and now I have finally completed a ver 7 unit :) Didn't have to set a flops count either after I worked it out then remembered that it's displayed in the log info when boinc first queries the cards....doh !!
ID: 1382580 · Report as offensive

Message boards : Number crunching : GT610 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED error on GPU work


 
©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.