réquiem
-
Sinalizar
como inapropriado
-
Mostrar
Show review history
1. How does a pool know miner's hash rate? I know miner sends easier successful hashes (shares?), but that's not a direct hash rate. 2. What inputs are used for hashing? I've read about Nonce, timestamp, extra Nonce. 3. What is the algorithm for input variations? 4. Is there a random element in how input variations are determined so that two identical miners do not follow the same input sequence? Because if there isn't then they would arrive at exactly the same sequence of hashes, and therefore a miner with better Internet connection (less latency) wins. 5. I am guessing that there is randomness. In this case, is there a chance that the same combination of input parameters may be repeated, thus wasting valuable hash rate? Or is the number of combinations of input variations is so great that there is little chance of that happening? 6. Why hash rate keeps fluctuating? E.g. for my LV07, it averages 1.0TH, but fluctuates between 0.85TH - 1.2TH. Every 3-4 min or so it reaches low point, and in the next 3-4 min it reaches the high point. And on, and on. 7. My LV07 frequency is set to 575 MHz. It generates around 1.0 TH. This means that during every tick the ASIC calculates (1.0 Th / 575 MHz) = 1739 hashes. How is that possible? Each hash is a complex calculation, and doing 1739 of them in a single tick!?! A regular CPU may execute a simple operation in a single tick - like moving data from register to memory, or perform an addition, etc.
1. How does a pool know miner's hash rate? I know miner sends easier successful hashes (shares?), but that's not a direct hash rate. 2. What inputs are used for hashing? I've read about Nonce, timestamp, extra Nonce. 3. What is the algorithm for input variations? 4. Is there a random element in how input variations are determined so that two identical miners do not follow the same input sequence? Because if there isn't then they would arrive at exactly the same sequence of hashes, and therefore a miner with better Internet connection (less latency) wins. 5. I am guessing that there is randomness. In this case, is there a chance that the same combination of input parameters may be repeated, thus wasting valuable hash rate? Or is the number of combinations of input variations is so great that there is little chance of that happening? 6. Why hash rate keeps fluctuating? E.g. for my LV07, it averages 1.0TH, but fluctuates between 0.85TH - 1.2TH. Every 3-4 min or so it reaches low point, and in the next 3-4 min it reaches the high point. And on, and on. 7. My LV07 frequency is set to 575 MHz. It generates around 1.0 TH. This means that during every tick the ASIC calculates (1.0 Th / 575 MHz) = 1739 hashes. How is that possible? Each hash is a complex calculation, and doing 1739 of them in a single tick!?! A regular CPU may execute a simple operation in a single tick - like moving data from register to memory, or perform an addition, etc.
This review was marked as helpful by
0 people
-
Sinalizar
como inapropriado
1. How does a pool know miner's hash rate? I know miner sends easier successful hashes (shares?), but that's not a direct hash rate. 2. What inputs are used for hashing? I've read about Nonce, timestamp, extra Nonce. 3. What is the algorithm for input variations? 4. Is there a random element in how input variations are determined so that two identical miners do not follow the same input sequence? Because if there isn't then they would arrive at exactly the same sequence of hashes, and therefore a miner with better Internet connection (less latency) wins. 5. I am guessing that there is randomness. In this case, is there a chance that the same combination of input parameters may be repeated, thus wasting valuable hash rate? Or is the number of combinations of input variations is so great that there is little chance of that happening? 6. Why hash rate keeps fluctuating? E.g. for my LV07, it averages 1.0TH, but fluctuates between 0.85TH - 1.2TH. Every 3-4 min or so it reaches low point, and in the next 3-4 min it reaches the high point. And on, and on. 7. My LV07 frequency is set to 575 MHz. It generates around 1.0 TH. This means that during every tick the ASIC calculates (1.0 Th / 575 MHz) = 1739 hashes. How is that possible? Each hash is a complex calculation, and doing 1739 of them in a single tick!?! A regular CPU may execute a simple operation in a single tick - like moving data from register to memory, or perform an addition, etc.
This review was marked as helpful by
25 people
Crow
-
Sinalizar
como inapropriado
-
Show history of
1. How does a pool know miner's hash rate? I know miner sends easier successful hashes (shares?), but that's not a direct hash rate. 2. What inputs are used for hashing? I've read about Nonce, timestamp, extra Nonce. 3. What is the algorithm for input variations? 4. Is there a random element in how input variations are determined so that two identical miners do not follow the same input sequence? Because if there isn't then they would arrive at exactly the same sequence of hashes, and therefore a miner with better Internet connection (less latency) wins. 5. I am guessing that there is randomness. In this case, is there a chance that the same combination of input parameters may be repeated, thus wasting valuable hash rate? Or is the number of combinations of input variations is so great that there is little chance of that happening? 6. Why hash rate keeps fluctuating? E.g. for my LV07, it averages 1.0TH, but fluctuates between 0.85TH - 1.2TH. Every 3-4 min or so it reaches low point, and in the next 3-4 min it reaches the high point. And on, and on. 7. My LV07 frequency is set to 575 MHz. It generates around 1.0 TH. This means that during every tick the ASIC calculates (1.0 Th / 575 MHz) = 1739 hashes. How is that possible? Each hash is a complex calculation, and doing 1739 of them in a single tick!?! A regular CPU may execute a simple operation in a single tick - like moving data from register to memory, or perform an addition, etc.
This review was marked as helpful
by 594 people