Forum > GPU crunching

Boinc 6.6.36 configuration

<< < (2/2)

Richard Haselgrove:
The <plan_class> is vital - that's what makes it a CUDA app.

The jury is still out on <api_version> - I haven't seen any comments about it, and in particular I haven't seen any persuasive reasons for including it. My guess is that there are lots of crunchers out there who "can't be bothered" to fine tune their app_infos with flops and things, and perforce put up with the weird EDF effects that result. They probably don't have <api_version> either - if it works for them, it should work for you too.

Geek@Play:
Thanks Richard

In case anyone cares.  I have not yet been isssued a 505 AP work unit.  By the time I was able to access Berkeley during the recovery, all the new 505 were gone.

Zeus Fab3r:

--- Quote from: Geek@Play on 28 Jun 2009, 05:30:33 pm ---Thanks Richard

In case anyone cares.  I have not yet been isssued a 505 AP work unit.  By the time I was able to access Berkeley during the recovery, all the new 505 were gone.

--- End quote ---

I have one 5.05 result to report using stock app.
It took nearly a day on Q6600@3Ghz claiming 1014 credits.
That's why I'm really eager to try one with an opt. beta version.
Sadly, due to my status here, I'm unable to grab one  :(
and I'd like to know what it takes to become a tester arround here?

Cheers, ZF

Edit: Just found out  ;D. My fifth post did the trick and now I'm a squire !

ndblaikie:
I am making my first post in these forums  :)

I have downloaded about 4 505's using the stock app on a C2D 2.13gHz takes about 90-100 hours, so am eager to be able to see how it runs on an optimized app. Strange thing is though since updating BOINC to 6.6.36 have mainly got CUDA work and not much CPU, could have something to do with the long crunch time of the 2 505's I have left will wait and see.

Navigation

[0] Message Index

[*] Previous page