All About BTC, LTC, ETH mining spil well spil other alternative crypto currencies
It seems that many users are having trouble understanding what is the actual hashrate they get from their 5-chip Gridseed ASIC miners, the reason for that is partly related to how the Gridseeds are treats te different miner software and the difference ter what is being reported. Wij are kicking off with the bfgminer Three.Ten.0 with Gridseed support running a single unit – see the screenshot above spil the example that wij are going to talk about. Note that the bfgminer has just bot began and there are 11 accepted shares, Two rejected and 0 hardware errors. The very first number demonstrating 361.Two KHS is the local hashrate of the miner (running at 850 MHz), this is calculated based on the frequency the miner is running at and is the hashrate that you should be getting te ideal conditions, however normally the conditions differ. The actual hashrate you are getting is the third number, the one wij have marked te crimson, so that you can clearly see what wij are talking about. That third number shows the actual hashrate based on the number of accepted shares and their difficulty, it takes into account the rejected shares and the hardware errors you get. The number is calculated spil an average since you have commenced the miner software. The question that you are most likely going to ask is why if ter ideal conditions wij should be getting 361.Two KHS here wij have 426.7 KHS spil actual hashrate. The reason for that lies te the fact that wij just had 11 shares accepted and wij had luck so that their difficulty wasgoed below the average, so the reported hashrate is averaged overheen a very brief period of time and is not what wij should be getting te the long run. You need to leave the miner run for a longer time ter order to have a better representation of the actual hashrate you will be getting, but te the long run you are most likely going to get a result that is a bit lower than the optimal value of 361.Two KHS.
Ter the 2nd example wij are going to be looking at cgminer Trio.7.Two modified to support Gridseed. Te the example above wij have a single miner overclocked to run at 950 MHz and the software miner has bot running for a few hours already. Again the very first number that shows 404.Three KHS is the theoretical hashrate te ideal conditions that is based on the operating frequency of the miner. The 2nd number that wij have marked with crimson is the actual hashrate that wij are getting with this ASIC device running cgminer. The 2nd number takes into account the time the miner is running, the number of accepted shares and their difficulty, the number of rejected shares and the hardware errors the device is getting. So instead of 404.Three KHS the actual hashrate wij are getting is 401.Five KHS te this case and this is the result wij are getting with the cgminer running for Four hours.
If wij take a look at the hashrate reported by the pool for the Gridseed ASIC miner using the cgminer example above wij can see that the pool reports 398.46 KHS and not 401.Five KHS. The number of submitted shares and rejected ones reported by the pool is also different. The reason for that is that the pool statistics has bot reset about 8 hours before beginning the miner and the statistics ter cgminer is for about Four hours only. The reported actual hashrate of cgminer is based on Four hours of running, however the reported hashrate by the pool is based only on the shares submitted te the past 1 hour. Different mining pools base their average hashrate on the number of shares submitted te the last X minutes and that period can vary inbetween 1 minute to 1 hour or even more. And spil with the software miners not being able to report very adequate hashrate ter just a minute or two, if the pool reports hashrate based on the shares submitted overheen a brief period of time it might be reporting lower or higher values that are not close to the real one. Looking at the right number ter bfgminer or cgminer should give you a pretty good idea on the actual hashrate you are getting, also pools that average hashrate overheen a longer period of time such spil at least Five or Ten minutes can be used to give you a good idea.
The very first miner available with support for the Gridseed ASIC devices wasgoed a modified version of cpuminer that however does not report local or actual hashrate spil that software miner does not keep statistics for the number of accepted and rejected shares, neither does take into account the hardware errors produced by the device. So it reports a hashrate of 0 all of the time, even tho’ it is actually working, the only way to find what is the actual hashrate if using cpuminer is to look at the hashrate reported by the pool.