I've got some going now. I'll let everyone know how they do.
I've got some going now. I'll let everyone know how they do.
6r39 7r199
I have not seen any validation issues yet with the 1.02 app... looks good on my gentoo 64 bit boxes.
Thanks for trying it again. Sorry if I steered anyone into it before it was ready - as Zombie said, the Win64 app was great - the Linux app needed a little (major?) tweak, apparently.
Glad it's working now. Mr. Hankey, your credits could go through the roof, and so could Mumps'! :-)
Bizarre. Here is my i7 windows machine:
http://androinc.net/results.php?host...state=3&appid=
For the 29 credit tasks, it is making over 200 c/h , and for the 115 credit tasks, it is making over 100 c/h.
I wonder if you are being hit by that "pause if CPU usage gets over 25%" setting?
I just did the math on mine. 38+K for the day yesterday, divided by 2 quad core CPUs = ~200 credits/hour per core. I'll let you know if it can sustain that over the next few days...
"My god! Do we really suck, or is this guy really that good?" - Mr Hertz - Shoot 'Em Up
You guys got me thinking, so I did some quick calculations using the validated WU's from Androinc. For yesterday all completed tasks returned 40,022 credits so that would be 1667 per hour. Not too bad I guess if you figure it that way.
Now on a credit per hour per core basis... that's a little different. 40,022/24/23 = 72 credits per core per hour.But that's an average and "average" is for
's.
I expect this to go up a little since I didn't get my new rig online until around 0800 hours.
"My god! Do we really suck, or is this guy really that good?" - Mr Hertz - Shoot 'Em Up