hiero-ledger / hiero-ledger/hiero-consensus-node

Reduced memory footprint when running in cluster with Solo

Open
#20,058 0 comments 0 reactions 1 assignee Claimed by @tinker-michaelj View on GitHub
Needs Triage
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

Solo has the following high level requirement:

- Title: Reduced Minimum System Requirements (Enterprise Laptop)
- Description: Network simulation (current target 3 nodes, 1 mirror node, jsonrpc relay, explorer) operating on a 16gb(12gb VM space) 4 core laptop.

Currently in a single node network running the Mirror Node Monitor Pinger 25 TPS, a single Consensus Node will exceed 7 GB for memory. Due to Solo Q4 requirements we need this brought down significantly to achieve our goal of running a full 3 consensus node network all on a 16 GB / 4 Core laptop with 12 GB dedicated to VM space.

Please assist the Solo team in either configuring Consensus Node to have a reduced footprint or making changes to ensure Consensus Node will not inhibit Solo team from achieving their Q4 target.

![Image](https://github.com/user-attachments/assets/a637f0c1-baf4-4ebf-a63d-5c635c8338e3)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.