trux plus s5
15 Jun 2006 23:03:07 UTC
Topic 191387
(moderation:
question, im useing trux with calibration on for e@h opti app from akos(did i spell that right? sorry if i didnt) and im wondering, it just downloaded an s5 unit and app,, should i turn off calibration? or, if i read right the credits for s5 is determind by the server and thus calibration shouldnt matter,,, right? or am i wrong?
sorry if im rambling, im posting this at the same time im trying to trouble shoot a "jerky pc" issue that sprung up from a stupid "idea" the other day involveing port 19 and a dumb idea to point a browser to it... ooops!
btw, i do NOT suggest ANYONE try that, seriously, youd basicly be dos'ing your own pc, it aint fun! took me a half hour to kill i.e. to halt the overload, thus i think its related to this new issue,,, im rambleing agian. sorry! hey, did i just hijack my own thread? lol
seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.
trux plus s5
)
S5 credit calculation is entirely server based.
RE: S5 credit calculation
)
Hi,
seems as if the credit calculation is fixed on server side. something like S@H flop couting, but on server side not client side.
Don't get me wrong now !
Is there any project that will not go that way ?
Leaving "the leveling of playgound" to the "recycle bin" where it belongs ?
Hi! Crunch3r Whats
)
Hi! Crunch3r
Whats happened with this url ?
http://calbe.dw70.de/
It keeps redirecting me to here -:(
I even restarted my DNS & NSCD servers, to no avail.
btw:
I use boincstudio, to crunch Einstein,
and yours, to crunch rosetta & hashclash
I run both on same pc. I use http://www.vmware.com
Thanks
Click signature for global team stats
RE: Is there any project
)
Well, CPDN has always decided credit server-side, the same has Folding@Home but granted their BOINC-application is stuck in beta, and now Einstein@home also decides credit server-side.
As you know, SETI@home uses fpops_cumulative, while some rumours has it Rosetta@home will start to use fpops_per_cpu_sec when CASP7 has finished...
This leaves many smaller projects that still atleast for the time being seems to continue to rely on benchmark * cpu-time to decide credit-claims...
Meaning, there should still be ample opportunity to continue running projects that even on the same computer can give 2x variation in claimed credit/hour in the same project due to BOINC-benchmark being all over the place on multi-cpu, and variation of claims will be even higher across computers.
"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."