Modified SETI MB CUDA + opt AP package for full GPU utilization

[Devaster]

bench attached

[attachment deleted by admin]

[Raistmer]

Seem that this app´s running

Tested with two PC´s. Vista 64 bit. Nvidia 9800 GT and 9800GTX+
Boinc 6.5 and Nvidia Driver 181

But one Question i have. I wont let run both apps. I mean GPU and CPU Seti Apps. At the moment i let run Seti GPU and WCG.
What must i do in the settings?

You can run only SETI MB and SETI AP on CPU+GPU simultaneously now. There is no known option to run only SETI MB on both CPU and GPU w/o too much hand work (you need to change task headers starting/stopping apps and so on).

[Slawek]

Hello all


What news ? New cuda APP ? ( where? ;P )

now im only computing AP ... not CUDA no new work for my CUDA engine

 

[Raistmer]

Hello all


What news ? New cuda APP ? ( where? ;P )

now im only computing AP ... not CUDA no new work for my CUDA engine

 

Dont'know why you use only AP. There is SETI MB CUDA version available. This thread just about modification of that version.

[Raistmer]

Ok, new bug fxes available - so new modded app available too
VLAR bug still with us although most advanced GPUs (fastest ones) could be free from it already - worth to test. Midrange like my own 9600GSO still suffer from it, especially under Vista.
Again, it's worth to try under XP - there are chances it will work under XP better.

Current bug fixes fight mostly with different overflows. Actually, they should eliminate overflows at all. So, please, report any overflow you will get if it not from VLAR and not from task was ran after driver crash w/o OS reboot.



[attachment deleted by admin]

[Richard Haselgrove]

I've seen one overflow with CUDA stock v6.07: http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=1693470

That had 30 spikes at AR=0.378607 - but the CPU v6.03 validator found exactly the same thing, so I'm assuming it's genuine.

Edit - likewise http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=1693468

[Raistmer]

Sure, nobody cancel "valid" overflows existence. Only "invalid" ones important o CUDA MB.

[Raistmer]

This build devoted to  all who still experiences videodriver crash on VLAR tasks. It should abort its own execution if VLAR with AR <0.14 is detected (temporary measure, of course).
All thanks go to Crunch3r & Maik  for this mod.


[attachment deleted by admin]

[Jason G]

Let me know how it goes and I'll crank it up again if it now stops crashing drivers and doesn't require manual babysitting.  Once the heat here goes down anyway, I don't really fancy pumping more Watts into the room right at the moment

[Raistmer]

Let me know how it goes and I'll crank it up again if it now stops crashing drivers and doesn't require manual babysitting.  Once the heat here goes down anyway, I don't really fancy pumping more Watts into the room right at the moment

Hehe, yes, heating more needed here than at your place now
It should go OK now, but will see (as usual)

ADDON: oops, I just going to post on main forums about update but project is closed for maintenance now... Time to start moan it seems

ADDON2 - unfortunately I already deleted all VLARs from current cache load + it seems beta feeds only midrange AR tasks now (see Richard's posts). So online mod validation will take some more time.

[Crunch3r]

... Time to start moan it seems

Moan ? I can do that a lot ! 
Let me see, where should I start??

First cross-project parity and credit correction... is that what you had in mind ?

[Raistmer]

First cross-project parity and credit correction... is that what you had in mind ?

No, I just joked about usual SETI forums moanings about any server outages even if they scheduled ones.
As I said in another thread all cobblestone value changes is really bad thing in my point of view too. Idea of interproject comparison is not so bad, but it should not be determining one IMHO...

ADDON: If cobblestone credits and RAC are overtopped to inter-project comparison idea they lost many advntages and become just measures of some artifical "absolute rating" between participants. I'm not sure that correct "absolute rating" between very different projects is possible at all.

[Archangel999]

use mb_r396 mode with my windows xp x64 and all is ok no more crash and errors

[Raistmer]

use mb_r396 mode with my windows xp x64 and all is ok no more crash and errors

396 is outdated now. Use 400 instead.

[Raistmer]

About Vista's driver restart:

The default timeout period in Windows Vista is 2 seconds.

http://www.microsoft.com:80/whdc/device/display/wddm_timeout.mspx