Is web3.eth.hashrate broken or my CPU is ?

PleuPleu Posts: 3Member
edited February 2016 in Mining
Hello all,

I was playing with eth when I found out that when typing > web3.eth.hashrate returns only ~240 000 when mining with my CPU with 4 threads (can't test on GPU), whereas on geth, > eth.hashrate returns ~1 400 000. Since, to my knowledge, eth is supposed to be slightly faster than geth, it kind of suprises me.

We can multiply the result of web3.eth.hashrate by the number of threads to get closer to geth's hashrate in the case that eth returns only one thread's hashrate, but we are still way off.
Why such a gap ?

Thanks :).

Answers

  • happytreefriendshappytreefriends Posts: 533Member ✭✭
  • PleuPleu Posts: 3Member
    $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily $ uname -a Linux linux 4.2.0-30-generic #35-Ubuntu SMP Fri Feb 19 13:52:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/cpuinfo | grep "model name" model name : Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz model name : Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz model name : Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz model name : Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz

    Command used to start eth:
    $ eth -C -t 4 -m on console
    And geth:
    $ geth --mine console

    I think you should test your hashrate with both clients on a private network to see if you get the result as I have.
Sign In or Register to comment.