Why is my XMRig hashrate so low?

Your XMRig hashrate is usually low because your CPU is running too many mining threads, memory settings are holding it back, or heat and power limits are slowing it down. Start with XMRig’s startup messages and local speed readings: they help you separate a setup problem from your computer’s normal limits.

Check which speed looks low

Hashrate is the number of mining calculations your computer completes each second, shown as H/s. XMRig shows your local speed, while your mining pool—a service that combines miners’ work—estimates speed from the work you submit.

Those numbers will not always match:

• Let XMRig finish initializing and run for several minutes before judging its speed.
• Compare longer averages, not just a brief peak.
• Give your pool more time. Its estimate can jump around when you submit work infrequently.

If local speed looks normal but the pool estimate stays low, check for rejected shares. A share is a submitted piece of work that proves you are mining. Connection trouble, an incorrect pool configuration, or unstable hardware settings can cause rejections.

Check your CPU, threads, and memory

Monero uses RandomX, its mining algorithm—the rules that define the calculations miners perform. RandomX favors CPUs, your computer’s general-purpose processors. A powerful graphics card does not guarantee strong Monero performance.

More mining threads are not always better. A thread is one stream of work running on your CPU. RandomX generally needs about 2 MB of L3 cache per mining thread. L3 cache is a small, fast memory area inside your CPU.

If your CPU has 16 MB of usable L3 cache, eight threads can be a sensible starting point, even if it supports more. The best setting still depends on your processor.

Try these checks:

• Start with XMRig’s automatic thread selection.
• Test fewer threads and compare stable averages.
• Close games, browser-heavy workloads, and other demanding apps.
• Check that your RAM uses the intended memory channels and supported speed.

RandomX’s fast mode needs a roughly 2,080 MB dataset, plus cache and other memory. Its light mode uses a 256 MB cache but is much slower. Insufficient available RAM or disk-backed memory use can badly hurt performance.

Read XMRig’s startup warnings

Look for messages about huge pages. These are larger memory blocks that reduce memory-management overhead. If XMRig reports that huge pages are unavailable or only partly allocated, you may be losing significant speed.

Also check its MSR status. MSRs are processor control registers; XMRig can adjust certain supported settings to help RandomX run faster. A failed adjustment can reduce performance, depending on your CPU.

Use official XMRig instructions for your operating system. Some changes require administrator access or a restart. Do not disable security protections blindly or run an unknown “optimized” miner with elevated permissions.

Look for heat and power limits

If speed starts high and then drops, check CPU temperature and clock speed. Thermal throttling means your processor slows itself down to prevent overheating.

Clean blocked vents, keep airflow clear, and check your power-saving settings. Laptops often cannot sustain their initial speed. Compare results with the same CPU model, not just a similar product name.

The bottom line

Check local averages first, then thread count, huge pages, available memory, and temperatures. Change one setting at a time. Aim for steady speed and reasonable power use—not a brief record that overheats your computer.