Home
/
Education resources
/
Advanced strategies
/

Maximizing xm rig: configure for full thread utilization

Maximizing XMRig Performance | Users Call for Full Thread Utilization

By

Emily Carter

May 14, 2026, 09:18 AM

Edited By

Anika Kruger

Updated

May 14, 2026, 03:21 PM

2 minutes estimated to read

A digital setup showing XMRig software running efficiently on a server with AMD EPYC processors, utilizing multiple threads for maximum performance.

A growing coalition of users is pushing back against XMRig's thread limitations on dual-socket servers equipped with AMD EPYC processors. While boasting the potential for 768 threads, XMRig is effectively utilizing only 480 threads. Users now call for optimization strategies to harness the software's full capabilities.

The Processor and Cache Conundrum

With dual AMD EPYC 9965 192-Core CPUs theoretically capable of supporting 768 threads, the limitations faced by XMRig are raising eyebrows. A participant noted, "There’s 384MB L3 per CPU; the RandomX scratchpad requires 2MB, so that’s ideally 192 threads per CPU, adding up to 384 threads for two CPUs." This begs the question: Are cache limitations hindering the software's performance?

The existing reports indicate that users require 2MB of L3 cache per thread for efficient mining. Without this, maximization becomes a challenge, leading to innovative configuration discussions.

Thread Configuration and NUMA Nodes: Key Strategies

A prevalent discussion among users revolves around command-line adjustments. One user advised, "Make sure to set NUMA nodes to 2 to utilize both CPUs efficiently." This, combined with proper command configurations, is seen as essential for unlocking maximum potential.

Some insights shared in the community include:

  • Thread Limits: Confirmations suggest that users should aim for a total of 384 threads between the two CPUs.

  • NUMA Configuration: Proper setup of NUMA nodes is crucial for effective thread utilization.

  • Command-line Tweaks: Adjusting command inputs and configurations proves vital to optimizing thread performance.

"Assuming you’re using XMRig via command line, adding --threads=768 can be a game-changer," noted one contributor.

Evolving Practices in Mining Optimization

As miners seek solutions to these limitations, the community remains hopeful for future updates from XMRig aimed at enhancing thread utilization. Experts are predicting a considerable probability that these updates will address the noted cache issues, fostering greater efficiency and boosting productivity.

Community Insights

  • πŸš€ Users agree that optimizing performance involves setting a strategic configuration.

  • πŸ“ˆ Several contributors emphasize the importance of sufficient RAM alongside proper settings.

  • πŸ”§ Command-line configurations and NUMA adjustments appear critical for achieving the desired results.

As the demand for efficiency grows, will XMRig meet the expectations of the mining community? Only time will tell as discussions continue around these essential optimization strategies.