I am mining on a single Antminer S9 with Slush Pool.

There is a setting called “ondergrens difficulty”:

When I read their manual, voorwerp #8 states

The pool automatically assigns difficulty that corresponds to the hash rate of your miner.

My scoring hash rate and hash rate are consistent with what the manufacturer of my mine advertises: 13.Five TH/s

and my default difficult is set too be 128.

However when I proceed reading their manual further I find that ondergrens difficulty should be set at 1024 for 1TH/s and then increases linearly with the hashrate.

According too the table my difficulty should be 13 times 1024 which is 13312. This is way higher than the pool determined 128.

What should I set the ondergrens difficulty be?

I attempted to understand what ondergrens difficulty is but I wasgoed incapable too find a clear and plain explanation what this number represents.

Two Answers

That’s just the ondergrens that the pool will assign that worker, not the difficulty that it’s actually working on. You can find that te your miner status pagina, under “DiffA#” which shows the difficulty of the last accepted share.

Generally you should not need to switch the ondergrens. It’s there te case the pool is having trouble determining what difficulty to use.

From the research I have done to understand the ondergrens difficulty it boils down to a balance inbetween server/client bandwidth limitations and time to waterput at risk.

The pool which you connect to distributes work for miners to solve. The more difficult each “package” of work sent to you, the longer you will take to find a solution and reply back to the pool with this solution, named share.

Spil explained ter this Postbode you will on average be rewarded the same solving problems of 10k difficulty at Ten seconds vanaf share, spil solving problems of 1k difficulty at 1 2nd vanaf share.

On the Antminer s9 Miner Status Tabulator the stats I believe, it may not be juist, I have deciphered are the following:

  • Summary:
  • Elapsed – Time passed since online
  • Utility – Number of Accepted shares vanaf minute
  • WU (Worker Utility) – Total Difficulty Submitted (Accepted + Rejected) vanaf minute
  • Pools:
    • Accepted – Number of Shares Accepted by the pool
    • DiffA# – Total difficulty of accepted shares
    • DiffR# – Total difficulty of rejected shares
    • Rejected – Number of submited Shares rejected by pool
      • either good hashes of bad work or bad hashes of good work
      • Discarded – Discarded Work that has not bot worked on. According to a developer of cgminer, meaningless.
      • Stale – Number Shares that were sent after a block wasgoed already solved.
      • LSDiff – Last Accepted Share Difficulty
      • LSTime – Time since Last Accepted Share
      • You can now check to see which difficulty the pool has automatically assigned to you te the Miner Status Pagina.

        So back to the initial question / response of the “optimum” difficulty is a balance of how many packages back and forward the network connection inbetween the server and client is comfy with treating and time to waterput at risk.

        • If the difficulty is very low, the network and server will be flooded with shares of solutions you have found and may reject some spil it can not treat so many packets vanaf 2nd.
        • So some work you have done te solving problems has gone to waste spil thesis solutions have bot rejected.
        • you are spending some time waiting for recieving fresh work from the server and also spending time sending the solutions to the server that could have bot used for finding solutions.
      • If the difficulty is very high, you may be working on solving a problem which no longer needs solving and so you will get no credit for the work. Spil far spil I understand, thesis submited shares would be marked spil Stale or Perhaps Rejected.
      • Presently a fresh bitcoin block is found every Ten minutes or so, sometimes under a minute sometimes more than 15 minutes. So, if you set the difficulty to a value which permits you to generate 1 share vanaf minute –> Utility = 1.0 then when blocks get found under 1 minute, you have lost that minute because the pool will generate fresh work with the latest fresh block to mine and the work you were working on that you couldn’t accomplish ter time would be futile. But if the next block were found ter 1 minute and Two seconds, you would have only lost Two seconds theoretically cause you would have very likely managed to submit a share.

        So, ultimately you don’t want to overcharge the pool but you want to make sure that you risk spil few shares spil possible.

        Your Risk would be approximately =1 / ( Average Accepted Shares vanaf minute * Average Minutes vanaf Block )

        From my practice hashing at 13.Five TH/s at a difficulty of 13.3K will produce approximately 1 share every Four.Five seconds or so –> Utility = 13.Five –> “WU = 13.Five*13312 = 179712” , Risk of approx 0.74%

        To optimize your difficulty you should look to maximize the WU : Worker Utility Value. Theoretical Max WU you can achieve is approximately 1 vanaf 71.6 MH/s, so a 13.Five TH/s machine can not achieve a better than a WU of 197706.

        I presently have a system configured at 10k Difficulty with a Utility of Eighteen.0 obtaining a Worker Utility of 190k, mining at KanoPool. I have aimed for Eighteen shares vanaf minute spil that is what is recommended by the pool.

        Just tho’ I may contribute my research on the subject incase it helps 🙂

        Disclaimer: This response are just compiled kattig from forum replies, github code and other onvriendelijk here and there I have found and my own understanding of how it evidently works. This is not necessarily 100% juist information.

        Related movie: Boost Ethereum Mining Speed on Nvidia GPU’s


        No comments

        Leave a Reply

        Your email address will not be published. Required fields are marked *

        You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>