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
  • Locate Your Configuration File
  • Navigate to the Engine Settings
  • Set the dataWorkerMemoryLimit
  • Calculate the Memory Limit
  • Apply the Configuration
  • Restart your service
  • Check your server performance:
  1. Tutorials
  2. Node
  3. Managing your system resources

Limiting the RAM assigned to each vCore

If you're encountering Out of Memory (OOM) errors in your system, and you haven't followed the recommended 1:2 ratio between CPU cores and RAM, there's a solution available within the configuration settings of your system.

This tutorial will guide you through the process of using the dataWorkerMemoryLimit setting in your ceremonyclient/node/.config/config.yml file to mitigate OOM errors.

Locate Your Configuration File

Find and open your ceremonyclient/node/.config/config.yml file. This file typically contains various configuration settings for your system.

Navigate to the Engine Settings

Within the config.yml file, locate the section related to the engine settings. This is where you'll make the necessary adjustments.

Set the dataWorkerMemoryLimit

Under the engine heading, add or modify the dataWorkerMemoryLimit parameter. This parameter allows you to specify the memory limit for each worker (core/thread) in bytes.

engine:
  dataWorkerMemoryLimit: [memory_limit_in_bytes]

Calculate the Memory Limit

Keep in mind that while adjusting the memory limit can help alleviate OOM errors, it's still recommended to have at least 2GB of physical memory per worker for optimal performance.

Determine the appropriate memory limit based on your system's specifications. The default allocation is 1.75GB per worker. If your system has less memory available, adjust the limit accordingly.

For example, to allocate 500MB per worker: 500 * 1024 * 1024 = 524288000

engine:
  dataWorkerMemoryLimit: 524288000

Similarly, for 875MB per worker: 875 * 1024 * 1024 = 917504000

engine:
  dataWorkerMemoryLimit: 917504000

Apply the Configuration

Save the changes to your config.yml file.

Restart your service

service ceremonyclient restart

Check your server performance:

Monitor the node log to ensure everything is functioning correctly:

sudo journalctl -u ceremonyclient.service -f --no-hostname -o cat


PreviousLimiting your CPU usageNextSwitching from tmux to service

Last updated 1 month ago

I also like to use to monitor system resources more closely (free to use on up to 15 servers)

📌
âš™ī¸
â˜‘ī¸
Hetrixtools
Cover

Want to say thank you?

CLICK TO DONATE