Forum > GPU crunching
x38g reports
Jason G:
--- Quote from: perryjay on 16 Jul 2011, 02:34:40 pm ---Here's an oldie but a goody http://setiathome.berkeley.edu/workunit.php?wuid=730523283 I know the first one was showing a couple of no heartbeats but it looks like it finished and had the same count as everybody else. Wonder why he didn't get any credit?
--- End quote ---
The count itself has value mostly for approximation & guessing somethings are about right, & other aesthetic qualities. Even the later 295's that processed successfully & became canonical with x38g look to be running on the edge. It has error results eerily matching the 560ti's with insufficient core voltage &/or cooling ( Yes, at this stage it appears the 560ti issues have been isolated as mostly attributable to those two primary factors).
The likelihood the original 6.03 result is broken is very high, given that a flaky looking 295 weakly matched your result... the final 6.03 that resolves the quorum sits 'the other side' of the 295 result from you. That x38g & x38e didn't perfectly match one another in this case is at first surprising until you include the multiple stability influencing factors that could be at play ... Just keep your own temps down & ensure sufficient core voltage etc, so you aren't 'the bad guy' :)
[Edit:] I've just had a brainwave that it may be helpful to add some indication of the number of reportable signals close to threshold, as we did with some astropulse bench testing a while back. I'll give it some thought.
perryjay:
I'm glad you got a handle on the 560Ti problem. Is there something you can do from this end or can you get the word out on how to fix it on the users end? I know I see a lot of my inconclusives coming from 560Tis so it sure would be nice for everybody concerned.
Jason G:
--- Quote from: perryjay on 16 Jul 2011, 04:22:55 pm ---I'm glad you got a handle on the 560Ti problem. Is there something you can do from this end or can you get the word out on how to fix it on the users end? I know I see a lot of my inconclusives coming from 560Tis so it sure would be nice for everybody concerned.
--- End quote ---
I'm currently giving it some deep thought. There are special nVidia developer tools available that I may be able to get temperatures & possibly voltages & clock rates. I could in future print lots of explanation to stderr & go into a temprary exit, or at least a failsafe mode of some sort when things look really obviously bad. I think after a long period of careful design, under certain more obvious circumstances it should be possible to choose either a hard error out to induce reissue & avoid contaminating the science database, or under some other known conditions do a temporary exit for some short time period & try again in some predetermined time interval. We'll see, the 560ti situation certainly raises these questions, and is no doubt a result of stock units being pushed far beyond reference nVidia specs.
Jason
perryjay:
Got an invalid. I found 8 pulses the other two guys didn't. http://setiathome.berkeley.edu/workunit.php?wuid=781226722
Jason G:
--- Quote from: perryjay on 18 Jul 2011, 12:51:27 pm ---Got an invalid. I found 8 pulses the other two guys didn't. http://setiathome.berkeley.edu/workunit.php?wuid=781226722
--- End quote ---
I have no immediate explanation for that one. Got a copy of the task by chance ?
[Edit:] I'll try get my updated offline bench suite updated & into public downloads at some point. Still wrestling with the fallout from juggling the new PSU etc, but should be under control soon.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version