Forum > GPU crunching
Win7-64 machine + 8800GTX + vanilla BOINC 6.10.18.: What now?
PatrickV2:
--- Quote from: Raistmer on 27 Nov 2009, 05:12:51 pm ---Look at result page on website.
--- End quote ---
Aha, all 4 we-re VLAR-kills:
<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.010757 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
What would the 'regular' cuda app have done with these? Started the calculation and barfed out in-flight?
Regards,
Patrick.
Claggy:
--- Quote from: PatrickV2 on 28 Nov 2009, 10:48:23 am ---
--- Quote from: Raistmer on 27 Nov 2009, 05:12:51 pm ---Look at result page on website.
--- End quote ---
Aha, all 4 we-re VLAR-kills:
<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.010757 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
What would the 'regular' cuda app have done with these? Started the calculation and barfed out in-flight?
Regards,
Patrick.
--- End quote ---
The stock Cuda app would have done the work, but would have done it at close to CPU speed,
on my 9800GTX+ they take over an hour to do, against 15 to 20 mins on mid range AR's.
Claggy
PatrickV2:
--- Quote from: Claggy on 28 Nov 2009, 01:52:05 pm ---
--- Quote from: PatrickV2 on 28 Nov 2009, 10:48:23 am ---
--- Quote from: Raistmer on 27 Nov 2009, 05:12:51 pm ---Look at result page on website.
--- End quote ---
Aha, all 4 we-re VLAR-kills:
<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
- exit code -6 (0xfffffffa)
</message>
<stderr_txt>
VLAR WU (AR: 0.010757 )detected... autokill initialised
SETI@home error -6 Bad workunit header
File: ..\worker.cpp
Line: 144
</stderr_txt>
]]>
What would the 'regular' cuda app have done with these? Started the calculation and barfed out in-flight?
Regards,
Patrick.
--- End quote ---
The stock Cuda app would have done the work, but would have done it at close to CPU speed,
on my 9800GTX+ they take over an hour to do, against 15 to 20 mins on mid range AR's.
Claggy
--- End quote ---
I would not really mind having such units take the same time as on the CPU really; abandoning/'killing' them seems also rather harsh? Or does that have little impact on Seti@Home? Will my machine not be 'marked' as being unreliable in the seti database when it kills off units on a regular basis?
Also, I finally got some work for my machine, but the 8800GTX is taking about 5 to 7 minutes per cuda unit. That is as to be expected?
EDIT: Oh wait, that's not the 'real' time, as I just watched the counter going up. I suppose I could get the real time from the errlog from the seti website?
Same question for the CPU units: ~2 hours / unit on a non-overclocked Q6600?
Regards, Patrick.
Claggy:
Use the rebranding program to move the VLAR Wu's to the CPU.
Claggy
PatrickV2:
--- Quote from: Claggy on 29 Nov 2009, 12:07:57 pm ---Use the rebranding program to move the VLAR Wu's to the CPU.
Claggy
--- End quote ---
OK, thread has 18 pages, and I see a V2 and V3 being posted on the first page. Checked the last 2 pages, no updates. Public beta and GPU areas do not contain it.
What's the most up-to-date rebranding tool, and how should this be run? Daily? Hourly?
Regards,
Patrick.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version