âī¸Changing the cpulimit value in release_autorun
Last updated
Last updated
If you run your node using the method outlined in this guide or via the release_autorun.sh file included with the node software, a CPU limit of 50% will be automatically set.
This is done to prevent your node from using 100% of the CPU constantly, which can impact performance negatively, especially when generating proofs.
However, it's important to note that each machine has its own optimal CPU limit for maximum performance. For some, this might be 60%, 70%, or another value.
A quick way to adjust this CPU limit is by using the following command:
Change 70 at the end of the command with whatever value you want to limit your CPU to, then restart your node after the change
Your node will not be able to update by itself anymore (because you have edited a core file). My manual update script however will still work because it contains a specific instruction to overwrite any local edits you made to the file with the source file.
This edit will be overwritten the next time you update via the update script ( Updating your node), you will have to run the command again.
