CPU mining uses processor resources for a compatible algorithm. It can affect system responsiveness, temperature, electricity use, and fan noise.
Begin with fewer threads than the maximum and observe responsiveness, temperatures, and accepted work. Leave resources available for Windows.
Practical note: Maximum utilization is not always the most stable or efficient setting.
Track package temperature, clock speed, power, and throttling. Compare results over a meaningful interval rather than a few seconds.
Practical note: Stop if cooling cannot maintain safe conditions specified by the hardware manufacturer.
Look for successful connection, authorization, job receipt, accepted work, rejected work, and reconnect messages.
Practical note: A high displayed rate is not useful if work is repeatedly rejected or the miner disconnects.
Usually, unless thread use is limited. Reserve capacity for normal tasks.
You can test different limits, but full use may reduce responsiveness or efficiency.
Thermal throttling, background tasks, power limits, algorithm behavior, and memory configuration can contribute.