Forum > GPU crunching
GTX 460 superclocked
TouchuvGrey:
--- Quote from: Josef W. Segur on 24 Aug 2010, 06:06:41 pm ---
--- Quote from: TouchuvGrey on 24 Aug 2010, 04:04:47 pm ---Downloaded and installed Lunatics_Win64v0.37_(SSE3+)_AP505r409_AKv8bx64_Cudax32f.exe
( Beta ) hoping this will help. i've watched my host average drop from 13,500 per day to
8700 per day since installing the GTX460. Suspecting i screwed something up along the way.
i have a Black Belt in that sort of thing. <sigh>
--- End quote ---
Actually, we screwed up. We failed to make it clear that all S@H CUDA applications built before the Fermi cards were released have problems on those cards, so you were running the v12 application and turning in a lot of tasks with a false result_overflow. Many of those ended up being judged invalid so got no credits. Some also happened to be paired with another host also running old CUDA code on Fermi, those unfortunately get validated and assimilated into the database. However, they overflow so quickly that there are few credits granted even for those.
There may be a lingering problem because the DCF has adapted to doing a lot of the work in extremely short time. That could lead to BOINC killing some tasks for "exceeded elapsed time limit", the infamous -177 error. The new rescheduler Fred M made has an expert feature to prevent any possibility of that, and IIRC there's a way to use that feature without actually rescheduling tasks. I hope someone who has actually used that will post a quick clear procedure. I don't have any GPU capable of crunching, so am only going on what I've read elsewhere.
You might also want to reduce your cache settings before asking for work during the uptime beginning Friday, the system thinking your GTX460 is much faster than it really is could lead to getting more work than you really want. After the host has 50 or so validated tasks done with x32f the server average should be close enough to not worry about that much, so the cache can be made as large as you need before the next outage.
Joe
--- End quote ---
Thank you Joe:
That explains quite a bit i was puzzled by. i'm very looking forward to
using an app that can take full advantage of the Fermi series. When they become
available i just may have to get a 2nd 460 for Aiden ( my main rig, named for my
newest grandson ).
i need clear and simple procedures for modifying config files and applications.
If there is any ambiguity at all in the instructions i will choose the wrong way of
doing something far more often than random chance would seem to allow.
TouchuvGrey:
--- Quote from: SciManStev on 24 Aug 2010, 06:47:39 pm ---On the expert tab, there is a check box that says Limit rsc_fpops_bound to avoid -177 errors. Check that off, and go to the first tab and push run. It takes a few seconds, but it works perfectly. I stopped a bunch of -177 errors cold by running that. Make sure you are not in simulation mode, which is also on the expert tab.
Steve
--- End quote ---
i just looked and failed to find the expert tab which tells me i'm looking in the wrong
place or i don't have one. Where do i look or how do i get one ?
To Richard who said "Anybody who installed any v12 or other non-Fermi app after then, with all the warnings here and on the main project, just wasn't reading...."
i plead guilty as charged, i have a long history of not reading the instructions.
perryjay:
You are using Fred's (Efmer) 2.0 rescheduler aren't you? If you are, just look along the top, the expert tab is the last one on the right.
--- Quote --- i plead guilty as charged, i have a long history of not reading the instructions.
--- End quote ---
I read them it's just that they might as well be in Greek most of the time. I need a lot of hand holding on these things. ;D
TouchuvGrey:
--- Quote from: perryjay on 24 Aug 2010, 07:28:21 pm ---You are using Fred's (Efmer) 2.0 rescheduler aren't you? If you are, just look along the top, the expert tab is the last one on the right.
--- Quote --- i plead guilty as charged, i have a long history of not reading the instructions.
--- End quote ---
I read them it's just that they might as well be in Greek most of the time. I need a lot of hand holding on these things. ;D
--- End quote ---
It sounds like i need to be using that rescheduler, where do i get it and how and where do i install it ?
A lot of this is Greek to me too, but what little i can get from it is a liitle that i did not know before.
Josef W. Segur:
--- Quote from: Josef W. Segur on 24 Aug 2010, 06:06:41 pm ---
Actually, we screwed up. We failed to make it clear that all S@H CUDA applications built before the Fermi cards were released have problems on those cards
...
Joe
--- End quote ---
--- Quote from: Richard Haselgrove on 24 Aug 2010, 07:00:49 pm ---Well, we were slow to pick up, but we were there by early June: I thnink all the warnings were in place by
http://lunatics.kwsn.net/1-discussion-forum/when-corrupted-results-get-validated.msg27734.html#msg27734
http://lunatics.kwsn.net/gpu-crunching/unified-installer-with-fermi-support.msg27926.html#msg27926
Anybody who installed any v12 or other non-Fermi app after then, with all the warnings here and on the main project, just wasn't reading. And of course, from that point onwards, just allowing stock download would have worked.
--- End quote ---
Agreed, anyone who read and remembered the 19th reply in the first thread you mentioned should not have gotten into difficulties. The second thread is in the section of this site closed to all except developers and alpha testers, so TouchuvGrey will not have seen that. In retrospect, your proactive approach suggested there was a very good idea and I hereby declare you not a part of the "we" who screwed up. And of course your warnings on the main project, etc. were very helpful. So much so that I for one didn't realize until quite recently that the smoldering embers were threatening to turn into a full blown fire.
Basically, the difficulty is we developers and many others here have a very technical orientation. What is obvious to us is not necessarily so for our users, and we failed to communicate effectively across that gap. Even a clear statement on the front page and in the description of the 0.36 downloads that V12 isn't Fermi compatible would not have completely prevented the developing problem, many are buying Fermi cards as an upgrade and no reinstall seems necessary in such cases. I'd be more comfortable if we had at least tried that kind of warning, though.
Joe
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version