Not sure what your question is. A hash is a hash is a hash. For pools? There is no advantage to having the same card generate multiple work threads, except that some people suggest that you might squeeze a couple extra Hashes out of the parallelized GPGPU structure. I don't really see it myself. Yes, this was essentially what I was wondering. Over the long haul it wouldn't really matter I supposed, but on the 0-minute "lucky" block solves where a multi-GH/s worker might only contribute a dozen or so shares before the block is solved, it could make a significant difference if indeed splitting the hashing power up into 2 or more workers makes a diff. lol? That's like saying "should I roll 4 dice all at once, or 2 dice over here and 2 dice over there?"
It's all random luck, so your results should be the same.
|
|
|
some brands may perform better than others.
|
|
|
fails: asus 5850 -> x16 5850 xtreme -> x1
works: 5850 xtreme -> x16 asus 5850 -> x1
|
|
|
Fixed pay per Share: A fixed price paid for every share (proof of work) received. Will be made available if there is demand for it. * grue DEMANDS
|
|
|
if your card can overvolt, you can get at least 400 MH/s (assuming cooling is adequate). dont mind the rejects, they were caused by internet failure.
|
|
|
Go read what a pyramid scheme is, this pool is a version of one.
troll? or did you not read any of the replies?
|
|
|
What's the benefit to you? Are you able to buy amazon giftcards at lower than face value?
because he bought some cards during the $20 for $10 promotion?
|
|
|
And I will, but you do realize that a person (me) with virtually no programming experience (except for coding an RPG in Qbasic when I was 12) will have a very hard time understanding that WIKI stuff which makes reference to things I've never heard of? I'm not sure why you can't figure out a way to tell your computer to get around the problem. Like, if you know what a given output needs to be, why cant you figure out what the input needs to be? It is based on an algorithm after all. Your computer isn't just guessing values 'randomly,' since randomness is another word for causation (caused by randomness). Why can't you use the algorithm to determine what the relationship is between inputs and outputs such that you can determine why a certain input gives the output that it does? My guess is that when TiagoTiago says "you can't know what effect a change in the input will have in the output," he really means "it's INFEASIBLE to try to know what effect a change in the input will have in the output." It's gotta be possible.
*sigh* http://en.wikipedia.org/wiki/Avalanche_effector do you want me to explain the entire sha-1 process?
|
|
|
i think running 2 instances of a miner increases stales dramatically. you really dont need to do it, just have a pool monitoring script
|
|
|
well, the asus card has better cooling, so it's better to place it in the x16 slot than the x1 slot
|
|
|
What's the relationship between the input and the output? Isn't there some kind of determination of a certain output given by a certain input? Will a given input always produce the same output? My apologies, I don't quite get it.
this isn't elementary algebra
|
|
|
In another thread that I read, I envisioned it as a 'guess-the-number' game. So, it'd be like if I told you to "guess a number between 1 and a million" where the only acceptable values are 0, 1, 2, and 3, and then after a difficulty increase, the only acceptable numbers are 0, 1, and 2, and so on. There's no way to tell your computer to hash out all 0's for example?
no, thats not how hashing works. go to the wiki
|
|
|
16CoEKvvcbAVSduEDpF5n43R5cJToBoPZc
|
|
|
lol, mojang is going to sue you for using their graphics
|
|
|
|