WARNING: Overclocking a Bitmain L3+ invalidates the 6 month warranty!
Overclocking is pushing your computing components over the designed clock speed to achieve a faster rating. In the case of over clocking a miner you will increase the hashing speed of the L3+ miner from 504MH/s to what ever the overclock ceiling is of the unit. All computer components have a limit and this limit can vary from unit to unit.
Caution: Overclocking processing components increase risk of component failure, increases power usage and in some cases reduce the life of the component.
WARNING: Did I mention that overclocking a Bitmain L3+ invalidates the Bitmain 6 month warranty!
Disclaimer: Overclock at your own risk, I am in no way responsible for any damage you may cause to your miner during overclocking.
Preparing to Overclock the Bitmain L3+
Overclocking the L3+ is very easy but this usually also means its very easy to damage your unit. DO NOT increase the miner frequency speed too much too quickly. Take your time and increase in small increments until you find the optimal setting.
You can find the setting under: Miner Configuration > Advanced Settings
The default frequency is 384 giving your miner a speed of 504 MH/s. It is this setting you need to change to increase your hashing power. As you increase the hashing power the electricity the miner uses will also increase. The idea is to slowly over clock until you find the optimal speed v power usage with the minimal amount of Hardware Errors. This may actually mean reducing the speed a fee frequency settings once you hit that ceiling.
DO NOT jump to a high clock frequency right away, slowly increase and wait for at least 15 minuets for the miner to settle at the new speed. Evaluate the readings and move on if you think its safe.
The table below shows all the variables as I underclocked then overclocked one of my miners.
|Frequency||MH/s Per Board||MH/s Total||Watts||MH/s Per watt||Temp (PCB)||Temp (Chip)||Fan1 (RPM)||Fan2 (RPM)|
I stopped overclocking this miner at a frequency of 469 (613MHz) as I was unhappy with the amount of hardware errors the miner started to produce within the 15min test phase. As you can see here one of the boards started to produce Hardware errors. When the miner produces hardware errors it is not sending completed results correctly to your pool and you can end up with a reduction in hashing power at your pool. You want to avoid this if possible. This is when you see a difference in the local hashing speed and the speed the pool is reporting
You will always get some hardware errors even at stock speeds but I like to aim for as little as possible to give me good results on the pool, ensure the life of the miner and give me a little room with the temperatures in case the ambient room temperature should increase.