Open LesnyRumcajs opened 1 month ago
The config.toml
[client]
#Controls whether the keystore is encrypted
encrypt_keystore = false
data_dir = "/home/forest/forest_data"
enable_rpc = true
enable_metrics_endpoint = true
metrics_address = "127.0.0.1:6116"
rpc_address = "0.0.0.0:2345"
[network]
listening_multiaddrs = ["/ip4/0.0.0.0/tcp/34000"]
#Kademlia option enforce p2p connections.
kademlia = true
#Amount of peers the node should maintain a connection with
#Helps in syncing ( moderate value to not be exceeded)
target_peer_count = 5000
Also the node is started with the following flags
--chain mainnet --config config.toml --stateless
Host node performance.
Hi all, is there a timeline for the new fixes?? We plan to run a forest bootstrap node, so we can have an idea of timeline when to expect. Thanks.
Reducing the memory footprint of bootstrap nodes is a low-priority issue, and it will not be done soon.
Issue summary
We've been running a stateless node over the weekend (May 18th - May 20th). The results are not satisfactory, given the overall connectivity and resource usage.
/dns4/bootstrap-mainnet-0.chainsafe-fil.io/tcp/34000/p2p/12D3KooWKKkCZbcigsWTEu1cgNetNbZJqeNtysRtFpq7DTqw3eqH
We expected the resource usage for a stateless node to be around ~500 MiB at most, but it's higher. Looking at the trend, there may be a memory leak somewhere. The CPU usage is also high - higher than in full-node Lotus.
The Forest used is
v0.17.2
. @samuelarogbonlo could you please add more details on the deployment, i.e., flags and configuration used? Thanks.Other information and links