<p>Yes Erik, the mining feature is still built-in and you can check how many hashes your CPU can perform. <strong>Although it's pointless and you cannot earn anything, it is still a fun experiment that people like to try.</strong> If you have a bitcoin core installed and synced with the network, you can just simply open the <code>command console</code> and type in and enter:</p>

<p><code>setgenerate true</code></p>

<p>This will initiate your CPU and will start mining. 
You can then get your hashrate by typing in </p>

<p><code>getmininginfo</code></p>

<p>Your hashrate will be shown in integer format and you should see a number like 1-3 million hashes per second.
To turn off the mining, because you will just be wasting energy type in</p>

<p><code>setgenerate false</code></p>

CC BY-SA 3.0
2015-10-02T20:28:23.953Z
so I'm using osx and those commands are not available by default.
erikvold
CC BY-SA 4.0
2020-12-11T05:03:57.757Z
I guess this should be the accepted answer then!
Bitcoingraffiti
CC BY-SA 4.0
2020-12-11T06:16:29.403Z
This answer is really old and outdated. `setgenerate` was removed in version 0.13 because mining with bitcoin core on mainnet is useless and has been for a number of years. https://bitcoin.stackexchange.com/a/70696/26873
m1xolyd1an
CC BY-SA 3.0
2015-08-12T23:05:38.043Z
2015-08-12T23:05:38.043Z
m1xolyd1an
<p>Most CPUs will do a few megahash per second, which is completely worthless for anything other than testing and has been for several years now. It may be possible to improve performance in the future as Skylake Intel x86 processors include specific instructions for SHA256, but only by a few percent. Even with improvements it is a waste of time and power attempting to use anything but the most efficient dedicated hardware. A large portion of ASIC miners are effectively obsolete due to their power requirements outstripping their output, and they are orders of magnitude more efficient than mining on a CPU. </p>

CC BY-SA 3.0
2015-08-12T08:40:26.650Z
This is not technically true. You can still enable the internal miners using the `-gen` option, and using the `setgenerate` RPC. It is non-optimized and slow though, even for a CPU miner.
Pieter Wuille
CC BY-SA 3.0
2015-08-12T14:07:19.670Z
@PieterWuille My mistake, I conflated the removal of `getWork` with removal of the miner entirely. Running `bitcoin-cli setgenerate true` does seem crash `bitcoind` though, wish I hadn't learned that in production.
Claris
CC BY-SA 3.0
2015-08-12T14:09:49.303Z
Please report that as a bug. As long as the feature exists, it should work.
Pieter Wuille
CC BY-SA 3.0
2015-08-12T02:24:40.817Z
2015-08-12T14:15:57.357Z
2015-08-12T14:15:57.357Z
Claris
<p>I'm curious how many hashes per sec my cpu is able to perform, is there some way to check this?</p>

<p><a href="https://bitcoin.stackexchange.com/questions/38863/about-traditional-bitcoin-mining">This is a follow-up to this question</a>.</p>

<bitcoin-core><hashpower><solo-mining><cpu-mining>
How to tell how many hashes/sec the bitcoin core app on osx is running?
erikvold
# How to tell how many hashes/sec the bitcoin core app on osx is running?

(Asked by: username_0 on 2015-08-12)

I'm curious how many hashes per sec my cpu is able to perform, is there some way to check this?

[This is a follow-up to this question](https://bitcoin.stackexchange.com/questions/38863/about-traditional-bitcoin-mining).

**Tags:** bitcoin-core, hashpower, solo-mining, cpu-mining


---

## 2 answers

### Answer by username_3 on 2015-08-12. Score: 3 | Accepted answer

Most CPUs will do a few megahash per second, which is completely worthless for anything other than testing and has been for several years now. It may be possible to improve performance in the future as Skylake Intel x86 processors include specific instructions for SHA256, but only by a few percent. Even with improvements it is a waste of time and power attempting to use anything but the most efficient dedicated hardware. A large portion of ASIC miners are effectively obsolete due to their power requirements outstripping their output, and they are orders of magnitude more efficient than mining on a CPU.

> **Comments:**
> **username_4**: This is not technically true. You can still enable the internal miners using the `-gen` option, and using the `setgenerate` RPC. It is non-optimized and slow though, even for a CPU miner.  
> **username_3**: @username_4 My mistake, I conflated the removal of `getWork` with removal of the miner entirely. Running `bitcoin-cli setgenerate true` does seem crash `bitcoind` though, wish I hadn't learned that in production.  
> **username_4**: Please report that as a bug. As long as the feature exists, it should work.  

---

### Answer by username_1 on 2015-08-12. Score: 6

Yes Erik, the mining feature is still built-in and you can check how many hashes your CPU can perform. **Although it's pointless and you cannot earn anything, it is still a fun experiment that people like to try.** If you have a bitcoin core installed and synced with the network, you can just simply open the `command console` and type in and enter:

`setgenerate true`

This will initiate your CPU and will start mining.
You can then get your hashrate by typing in

`getmininginfo`

Your hashrate will be shown in integer format and you should see a number like 1-3 million hashes per second.
To turn off the mining, because you will just be wasting energy type in

`setgenerate false`

> **Comments:**
> **username_0**: so I'm using osx and those commands are not available by default.  
> **username_2**: I guess this should be the accepted answer then!  
> **username_1**: This answer is really old and outdated. `setgenerate` was removed in version 0.13 because mining with bitcoin core on mainnet is useless and has been for a number of years. https://bitcoin.stackexchange.com/a/70696/26873  

---

