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. Tutorials
  2. Node

Managing your system resources

Quilibrium will use 90-100% of your CPU power all the time. Take precautions to avoid being banned by your provider.

PreviousReinstalling the node from scratchNextLimiting your vCores usage

Last updated 1 month ago

A good starting point to limit your CPU usage is 70%

My CPU is frying!

Limit your overall CPU usage: Limiting your CPU usage (recommended)

Diminish the number of vCores used by your node: Limiting your vCores usage


In this case, there is a theory that limiting CPU usage is better than reducing the number of active cores. The former approach allows all vCores to operate at a reduced capacity, enabling them to 'breathe,' while the latter essentially deactivates some cores while maintaining full power usage for the remaining ones.

My RAM is burning hot!

Diminish the number of vCores used by your node (easier): Limiting your vCores usage

Diminish the RAM assigned to each vCore (more complex): Limiting the RAM assigned to each vCore

If I limit my CPU usage, do I still need to limit my vCores?

That depends. Each vCore is assigned 2 GB of RAM. So the ratio between your vCores and your total RAM needs to be least 1/2. Even if you limit your overall CPU usage, this ratio needs to stay the same, or you will go OOM (Out of Memory).

The only case in which you may not need to limit your vCores number, is if you assign less RAM to each vCore by Limiting the RAM assigned to each vCore (This, though, it's not the best for your node performance).


📌
âš™ī¸
Cover

Want to say thank you?

CLICK TO DONATE