Hash speed drain

  • Resolved metaborg

    (@metaborg)


    7 years ago

    Sorry for making such a long post but…

    Im using an intel I7 when i use the miner of coin hive i have 70 hashes/s, using the plugin i get 35 h/s, 17.5% for the author seems right, but i get a 50% less hashing rate which does not seem as what the plugin should charge (developer + my 3% should give a total of 20.5 % cost for implementation of the plugin, (miners in my site are only getting 50% of mined hashes) its at a 30% hash loss and when i do the math i dont understand where is the difference going.

    When i make mining with the wp plugin the coin hive dashboard tells me my mining is 35 h/s, but using the coinhive miner i get 70 hashes/s (info of the coinhive dashboard)

    intel i7

    100% = 70 hashe/s
    50% = 35 hashes/s
    developer: 17.5% of 70 hashes/s is around 12.25 h/s

    so 12.25 h/s + 35 h/s is 47 h/s

    47 shashes – 70 hashes is 23 hashes which are somehow in the limbo.

    Where are the missing 20+ hashes/s?

    Thanks in advance for your effor to resolve this issue, it will improve the service of the 20+ users i have in my site.

    • This topic was modified 7 years ago by metaborg.
    • This topic was modified 7 years ago by metaborg.
    • This topic was modified 7 years ago by metaborg.
    • This topic was modified 7 years ago by metaborg.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author denniske1001

    (@denniske1001)

    If you are using the pro version the miner will run 5 minutes for your site key and then one minute for the developer site key.

    Just let it run for 30min and you will see the pattern in the logs:
    04-11-2017 23:42:06 Miner refreshed with site= …
    04-11-2017 23:47:06 Miner refreshed with site= dev
    04-11-2017 23:48:06 Miner refreshed with site= …
    etc.

    So this will result in running the miner every 6th minute for the dev. For example the following minutes the miner will run for dev:
    6, 12, 18, 24, 30, 36, 42, 48, 54, 60

    These are 10 minutes out of 60 minutes per hour. So 1/6 = 16.666 % the miner runs for dev.

    The only thing that may cause a bit less performance compared to running the coinhive miner is the switching of the site key (in the log “Miner refreshed with site…”).
    You can then see the hashrate shortly drop and rise again in the miner control widget.

    I will do a benchmark in the next days where I check the hashrates.

    Plugin Author denniske1001

    (@denniske1001)

    I let the miner run for about 4 hours. These are the results:

    Miner Stats

    So I have written down the hashes before starting the miner and afterwards and calculated the hashrate. The site/dev ratio was 85%/15% which is okay. Also the calculated hashrate was only slightly lower than the hashrate reported in the logs.

    Maybe the coinhive dashboard hashrate display is confused because of the changing of the site key.

    Can you let the miner run for a longer time period and calculate the hashrate using before and after total hashes values?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Hash speed drain’ is closed to new replies.