Why does XMRig show "miner speed n/a" for the first few seconds?

XMRig shows “miner speed n/a” for the first few seconds because it does not yet have a usable speed measurement to display. This is usually normal: the miner needs to finish starting up, begin working, and collect enough timing data before it can show a rate.

What “n/a” means here

Your mining speed is called your hashrate. It measures how many mining calculations your computer performs each second, usually shown as H/s, or hashes per second.

At startup, “n/a” means “not available,” not necessarily zero. XMRig, or the dashboard showing its results, may not have a valid measurement yet.

Speed is measured over time rather than at a single instant. XMRig commonly reports averages over 10 seconds, 60 seconds, and 15 minutes. Those readings do not all become useful immediately. You may see a short-term speed appear while longer-term fields still show no value.

If you are viewing XMRig through a separate dashboard, its update schedule can add another small delay.

What happens before speed appears

Before XMRig can measure useful work, it has several startup tasks to complete. When mining Monero, these can include:

• Connecting to your mining pool, a service that combines miners’ work and shares rewards.
• Receiving a mining job, which tells your computer what work to do.
• Preparing RandomX, Monero’s mining algorithm—the rules your computer follows to perform mining calculations.
• Starting the processor workers that carry out those calculations.

RandomX setup is especially relevant. Its fast mode prepares a dataset of about 2,080 MB in memory. Building that dataset takes time, and the delay varies with your processor, memory, and other programs running on your computer.

During preparation, you might see processor activity before you see a mining speed. That activity can be setup work rather than the repeated mining calculations counted in the displayed rate.

Why you do not need to wait for an accepted share

A common misunderstanding is that speed appears only after your pool accepts your first share. A share is a piece of mining work you submit to show the pool that your computer is contributing.

XMRig measures its local speed from the calculations it performs. It does not need an accepted share to calculate that speed.

This distinction matters because your first accepted share may take longer to arrive, especially on a slower processor. Your local speed can already be visible and valid during that wait.

A pool’s website is different: it often estimates your speed from submitted shares, so its reading can take longer to appear or settle.

When the delay deserves a closer look

If speed appears shortly after startup and then updates normally, you usually do not need to change anything.

If it stays unavailable well after startup should have finished, read XMRig’s messages. Check whether:

• RandomX preparation has completed.
• Processor workers have started.
• A pool connection and mining job are present.
• Mining is paused or errors are being reported.

A missing huge-pages optimization can reduce performance, but it does not by itself mean speed must remain unavailable. Avoid changing settings simply to remove a brief startup message.

The bottom line

For the first few seconds, “miner speed n/a” usually means “still getting ready or measuring.” Wait for startup to finish and a short measurement window to pass. Investigate only if the reading stays unavailable or the startup messages show a problem.