Finished 4 WU's and have gotten 38,605 credits so far. Running a single 4870 by itself in a system.
Printable View
Finished 4 WU's and have gotten 38,605 credits so far. Running a single 4870 by itself in a system.
Found the reason why awarded credits started recently changing wildly:
http://moowrap.net/forum_thread.php?id=18
What is this D...A thing? I think I will let ya'll tell me when the water's nice before I jump in this time. I lost at least 8 days on that last AQUA experiment, so I'm a little gun shy now...
DA is some big wig within the BOINC project, aka credit Nazi, Scrooge, etc. etc...
He dictates how much credit projects can dish out to "try" to keep them fairly balanced between users and try to prevent everyone flocking to the ones with the highest credits.
Moo is alpha testing according to the news page on their forum.
Here's my results so far:
http://moowrap.net/results.php?useri...state=3&appid=
and:
http://moowrap.net/top_users.php
Dr. Anderson of Seti fame. He runs such a stellar project ... it was the 1st project and I think they are still running the original code and servers. :)
Hmmm...
Well this project IS definitely BETA. :))
My 4870 (10.10) was cranking right along without error until this afternoon, now all WUs appear to complete normally but end with an error code -161.
Never have gotten my 460 GTX (266.58 Driver) to complete a WU, GPU processing never starts, WU keeps restarting with progress of 0%.
One of my old 9800 GT cards (266.58 Driver) appears to be working but who knows how long that will take to complete a WU and if it validates when completed.
Was hoping to get at least my 100K stone before moving on but as much as this project has been screwed up in the past 24hrs it doesn't look like I'll get there.
David Pope Anderson
He is the creator of the original SETI@home app. He is the guy who owns BOINC development. We U.S. tax payers are paying for him to do it. His belief in cross-project parity is delusional. Impossible. Proven to be so. Yet he keeps spitting in the wind...splattering us all.
Should I run this on my box with one 5870 or run MW in the same box with 2 5870's? It's in the family box so won't run 24/7 but can pick up a few extra stones.
Just from what I have been reading it sounds like people are having problems with dual card setups. I am running a single card in one rig and have not had 1 problem so far.
Yeah, can't figure it out. I have seen a couple 460s on the project working with older drivers but not ver 266.58 which I'm running here. The app apparently never initializes the card as I can't find the "Automatic processor type detection" messge in any of the stderr_out on that machine.
Oh well, my old 9800GTs & 4870 are getting some credit so I'm making some headway.Code:<core_client_version>6.11.6</core_client_version>
<![CDATA[
<message>
aborted by user
</message>
<stderr_txt>
23:31:14 (4704): wrapper: starting
23:31:24 (4704): wrapper: running dnetc518-win32-x86-cuda31.exe (-ini dnetc.ini -runoffline -multiok=1 -e <censored> )
dnetc v2.9109-518-CTR-10092921 for CUDA 3.1 on Win32 (WindowsNT 5.1).
Using email address (distributed.net ID) '<censored> '
[May 05 04:35:20 UTC] nvcuda.dll Version: 6.14.12.6658
23:36:35 (4704): no checkpoint in 301 seconds, restarting
23:36:49 (4704): task process has not exited within 10 seconds, forcing it to die
23:36:55 (4704): wrapper: running dnetc518-win32-x86-cuda31.exe (-ini dnetc.ini -runoffline -multiok=1 -e <censored> )
dnetc v2.9109-518-CTR-10092921 for CUDA 3.1 on Win32 (WindowsNT 5.1).
Using email address (distributed.net ID) '<censored> '
[May 05 04:40:36 UTC] nvcuda.dll Version: 6.14.12.6658
23:42:01 (4704): no checkpoint in 301 seconds, restarting
23:42:11 (4704): task process has not exited within 10 seconds, forcing it to die
23:42:16 (4704): wrapper: running dnetc518-win32-x86-cuda31.exe (-ini dnetc.ini -runoffline -multiok=1 -e <censored> )
23:44:37 (4704): task process has not exited within 10 seconds, forcing it to die...
I don't run the 460GTX 24/7 anyway, just use it once and a while for a little push, it's on my main desktop and I'd like it to last for more than a couple years. I've RMA'd 3 GPUs in the past couple months for dead fans...
IMHO
PNY= Great customer service & fast turn around on RMA.
ASUS= Worst customer service I've experienced in years, almost not worth the hassle of getting a RMA for a card.
Looks like they increased the credit. It started with about 8-9K per WU, dropped to about 3K as DA's credit system kicked in, and now it is up around 9-10K which may make it the best paying ATI GPU app for those who get it to run w/o errors.
I managed to get 30k out of a dozen or so of them before the bug kicked in again and my GPU's went idle. Now I'm waiting for the daily quota to reset because I had so many of them error out. :mad:
This is silliness. I put my two 5870s on this in the AM today. So far I've finished 9 work units for 553K.
Dan
Nope. My dual 5870 still takes 1-2 hours to run a task. Credits are ranging from 400 to 58,000 each. So I think I will continue to let that project under-utalize my GPUs for now. ;)
http://moowrap.net/results.php?hosti...state=3&appid=
All of my tasks are taking around 1 to 1.5 hours. The first nine averaged about ~8 credits per second per GPU. The latest one averaged ~1 credit per second, per GPU, which is half the credits I get off Milkyway. Milkyway gives me ~2 credits per second, per GPU. I'll let it run a little while longer and see what the real credits are, but if it's like the last wu, then it's back to Milkyway.
Dan
Amd 570 slowed down, did one in a little over 97 mins for 18k credits. Oc'd to 880 done in 47 mins for 8500 credits. Maybe just random chance but hard not notice that credits seem to be tied to card per wu rather than wu's done(twice as fast card got half the credits).
Considering a slowed down 570 was drawing 165watts-100w(system usage when idle)=65 watts and an OC'd card 280w-100w=180w give the same credits(albeit at twice the rate)...somethings not right.
I'll run these later tonight and see if this was just a weird coincidence.
Remember, this project uses the new credit method that DA implemented. It is adaptive. So it will be constantly adjusting the credits awarded. Theoretically, the variations will be large at first, smoothing out over time. In the real world? No idea yet, as this is one of the first projects to use it.
Add to that mess, the admin is also tweaking the formula manually.