Ethernity Docs
  • Welcome to Ethernity CLOUD
  • Getting Started
  • Ethernity Node Quick Start
    • Hardware Requirements
    • BIOS Settings
    • Supported Platforms
    • Blockchain Settings
    • Security Considerations
    • Installation
  • Ethernity Client Quick Start
    • Platforms and dependencies
    • Blockchain Settings
    • Security Considerations
    • Installation
  • ethernity node
    • Prerequisites
      • Hardware with SGX Support
      • Check SGX Support
      • Installing Linux
        • Download
        • USB Installation Media
        • Ubuntu 18.04 LTS
        • Ubuntu 20.04 LTS (Recommended)
        • Ubuntu 22.04 LTS (Experimental)
        • SSH Connection
      • Blockchain Wallets
    • Download
    • Installing the Node
    • Update the node
    • Configuring the Node
      • Select the network
        • Mainnet on Bloxberg
          • ETNY on Bloxberg
        • Testnet on Bloxberg
          • Data Processors
          • Bloxberg (BERGS)
          • tETNY on Bloxberg
          • tETNY Faucet
        • Mainnet on Polygon
          • ECLD on Polygon
        • Testnet on Polygon (MUMBAI)
      • Task execution price
      • Resources configuration
    • Monitoring the Node
    • Troubleshooting issues
    • Firewall Rules
    • Proof of eXecution
      • Blockchain Metadata
      • IPFS
    • Node Reset
      • Node Connect
        • DHCP
        • Static IP
        • Console
      • Change Password
      • Node wallets
  • Mainnet
    • Mainnet on Bloxberg
    • ETNY on Bloxberg
    • Mainnet on Polygon
    • ECLD on Polygon
  • TESTNET
    • Data Processors
    • Bloxberg (BERGS)
    • tETNY on Bloxberg
    • tETNY Faucet
    • Polygon (MUMBAI)
  • Developer Guide
    • Introduction
    • The EC Protocol
      • Data flow inside EC
    • The GUIDE
      • Environment Prerequisites
      • Step-by-Step dApp
  • ENS Domain Registration
    • Introduction
    • ENS Smart Contract Details
      • Polygon Mainnet
      • Bloxberg Mainnet
    • Registration Steps (ENSRegistrarController)
  • Ethernity Client
    • Prerequisites
      • Python 3.6+
      • git
      • Blockchain Wallet
    • Download
    • Running the Client
    • Configuring the Client
    • Proof of eXecution
      • Blockchain metadata
      • IPFS
  • Ethernity Smart Contract
    • Data Owner API
    • Data Processor API
  • Wallet
    • MetaMask
    • Installation
    • New Wallet
    • Restore Wallet
    • Wallet Validation
    • Contract Upgrade
    • Receive ETNY - Optional step
    • Send ETNY - Optional step
    • Change RPC URL
  • Public Sale Buying Journey
    • Round 1
      • Interest Registration
      • Public sale start
      • Queue placement
      • Crypto (USDT) payment
      • Bloxberg receiving address
      • Troubleshooting
    • Round 2
      • ❗VERY IMPORTANT
      • Interest Registration
      • Login
      • KYC - R2
      • Queue placement
      • Payment Options
        • USDT
        • Coin Payments - Crypto
        • Coin Payments - Paypal
    • Round 3
      • ❗VERY IMPORTANT
      • Interest Registration
      • Login
      • KYC
      • Package Selection
      • Payment Methods
        • DIRECT
          • USDT - ERC-20
          • USDT - TRC-20
          • USD - Polygon
          • BUSD - BSC
        • COINPAYMENTS
        • PAYPAL
        • CEXs and Hot Wallets Withdraw
          • Binance
          • Coinbase
          • Kraken
          • MetaMask
          • Trust Wallet
        • Receive ETNY
  • Staking dApp
    • Intro
    • Node address and private key
    • Import private key
    • Connect wallet to dApp
    • Change connected wallet
      • Disconnect wallet address
    • Staking dApp homepage
      • Account
      • Pending
      • Approved
      • Terminated
      • Marketplace
    • Base stake
      • Create base stake
      • Approve base stake
    • Extended stake
      • Create extended stake
      • Apply for an extended stake
      • Approve extended stake
    • Open Beta Staking dApp
  • SWAP dAPP
    • Intro
    • Create Account
    • Login
    • KYC
    • Setting up the profile
    • Dashboard
    • Confirmation
    • Sign transactions
  • LIQUIDITY PROGRAM
    • Liquidity Supply Guide
    • Connect wallet
    • Select range
    • Choose contribution
    • Viewing pools
    • Remove liquidity
  • Hardware Affiliate Program
    • Intro
    • Hardware Affiliate
      • Create Account
      • Login
      • Dashboard
      • Generate codes
      • Upload Codes
      • Profile information
    • Node operator
      • Register
      • Login
      • KYC
      • Activate Device
  • Contact
    • Social Media
Powered by GitBook
On this page

Was this helpful?

  1. ethernity node
  2. Configuring the Node

Resources configuration

PreviousTask execution priceNextMonitoring the Node

Last updated 1 year ago

Was this helpful?

To modify the memory (RAM), CPU, and HDD/SSD space for your node in the Vagrantfile, you can follow these steps:

1. Open the terminal on your system or connect via SSH

  1. Navigate to the directory where the Vagrantfile is located. In this case, it's ~/mvp-pox-node/. You can use the cd command to change directories. For example:

cd ~/mvp-pox-node/
  1. Open the Vagrantfile using your favorite text editor, such as "vi" or "nano". For example, to open it with nano:

nano Vagrantfile
  1. Locate the lines in the Vagrantfile that define the memory, CPU, and HDD/SSD space:

  • The domain.memory line sets the amount of memory (RAM) in megabytes (MB). In this example, it's set to 4096 MB (4 GB).

  • The domain.cpus line sets the number of CPUs. In this example, it's set to 2.

  • The domain.machine_virtual_size line sets the HDD/SSD space in gigabytes (GB). In this example, it's set to 128 GB.

5. Modify the values according to your requirements. For example, if you want to increase the memory to 8192 MB (8 GB), change the line to:

6. Save the changes and exit the text editor. In nano, you can press Ctrl+X, followed by Y and Enter to save the changes.

After updating the configuration settings, the node has to be redeployed by running the following

$ sudo vagrant reload

Running this command will reload the VM, applying any changes made to the Vagrantfile without destroying the VM's current state. It will provision any necessary changes and update the VM accordingly.

Make sure you are in the same directory as the Vagrantfile when running the command from above.