Quilibrium.one
SocialOfficial
Quilibrium Node Guide
Quilibrium Node Guide
  • 🖖Introduction
  • ✅Safety checks
  • đŸ“ŖAnnouncements
  • 🔗Links & Info
  • đŸ’ģBest server providers
  • đŸ’ģHardware requirements
  • 😎Q1 - Node Manager
  • ⚡Node Auto-installer
  • âŦ†ī¸Updating your node
  • âœ”ī¸Check your node info
  • 🔑Backup your private keys
  • đŸ“ĻBackup your node
  • 🔁Set up the gRPC calls
  • đŸ› ī¸Tools and scripts
  • 🔧Extra tools
  • 🔠Useful commands
  • â‰ī¸Troubleshooting
  • 📌Tutorials
    • Node
      • đŸ”ĸNode step by step installation
      • đŸŗInstalling the node on Docker
      • đŸĒŸInstalling the node and the qclient on Windows WSL
      • â†—ī¸Migrating the node to a new server
      • â„šī¸Running the node via binary file
      • Running a node cluster
      • ✅Reinstalling the node from scratch
      • âš™ī¸Managing your system resources
        • â˜‘ī¸Limiting your vCores usage
        • â˜‘ī¸Limiting your CPU usage
        • â˜‘ī¸Limiting the RAM assigned to each vCore
      • 🔄Switching from tmux to service
      • 💲Log your node balance every 1 hour
      • 🩷Escaping the "Pink Screen of Death"
      • 🔒Set up SSH keys
      • 🔒Creating a root login access
      • 👀Renting Servers Unveiled: Exploring Types and Processor Terminology
    • Qclient
      • Qclient commands
      • How to transfer QUIL
      • How to Bridge QUIL to WQUIL
      • How to retrieve your coin address after a failed bridging operation
  • 📂Archive
    • ⚡OLD - Node Auto-installer
    • đŸ”ĸOLD - Node step by step installation
    • 🔠OLD - Useful server commands
    • â‰ī¸OLD Troubleshooting
    • âŦ†ī¸OLD Updating your node
    • ⚡Importing an existing store folder for fast sync
    • â˜‘ī¸Changing the cpulimit value in release_autorun
  • âš ī¸Work in progress
  • 💜Want to say thank you?
Powered by GitBook
On this page
  1. Archive

Changing the cpulimit value in release_autorun

PreviousImporting an existing store folder for fast syncNextWork in progress

Last updated 1 month ago

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:

find /root/ceremonyclient/node/ -type f -name release_autorun.sh -exec sed -i 's/cpulimit -l [0-9]\+/cpulimit -l 70/g' {} +

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

âš ī¸ Please note that if you run this command...

  • 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.


📂
â˜‘ī¸
Cover

Want to say thank you?

CLICK TO DONATE