There is a similar post which asks the question about scaling up hash rates with computational power here. My question is similar, however with the added question about a potential bottleneck.

I am running a self-contained node on an AMD EPYC 7402 on a Gigabyte MZ72-HBO motherboard (single CPU slot atm), with 2933MHz ECC RAM and blockchain located on an LVM-raid (mirror i.e. raid1 config) Samsung 870 QVO SATA SSD. If I mine with 24 threads, I get a hash rate of ~10,000H/s. If I double that thread count, then I only see an increase of ~1.5K-2KH/s. I see a limit to that increase at 36 threads. This increase is not substantial enough to warrant the extra power, it appears there is a sweet spot after which I see drastically diminishing returns.

Also, it appears that the Ryzen 9 5950X is hashing at almost twice this rate, but that doesn't make much sense. Even though the boost is an extra GHz, that is just boost. My cores are running at the max rate of 3.4 GHz consistently.

Is this a result of my total contribution to the global mining pool and inherent "limit" of what one person can contribute based on what is available? OR could this be the result of an unforeseen bottleneck somewhere in my system?

Would I benefit from placing the blockchain on an NVME SSD for example? Could the software raid be affecting read/write performance?

I'm not asking for specific hardware/config support, more curious if there are known limits other people have faced and things that have worked or not worked for their rigs.

1 Answer 1


I suggest carefully reading: https://github.com/tevador/RandomX#which-cpu-is-best-for-mining-randomx

... More specifically, efficient mining requires:

  • 64-bit architecture
  • IEEE 754 compliant floating point unit
  • Hardware AES support (AES-NI extension for x86, Cryptography extensions for ARMv8)
  • 16 KiB of L1 cache, 256 KiB of L2 cache and 2 MiB of L3 cache per mining thread
  • Support for large memory pages
  • At least 2.5 GiB of free RAM per NUMA node
  • Multiple memory channels may be required:
    • DDR3 memory is limited to about 1500-2000 H/s per channel (depending on frequency and timings)
    • DDR4 memory is limited to about 4000-6000 H/s per channel (depending on frequency and timings)

Where the blockchain resides is largely irrelevant as mining doesn't require disk IO. Speed (and amount) of RAM and cache availability are far more important.

  • 1
    AH!!! Ok cool, so I'm pretty sure the RAM channels are my bottleneck right now as I've only got two slots (channels) filled. Makes sense as I can see the hash rate trying to push past 11000 but just not quite getting there... I missed that the first time around reading these specs! Thanks :)
    – BitShift
    Commented Jan 26, 2022 at 9:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.