-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stateless node bad performance #4346
Labels
Comments
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 |
4 tasks
This was referenced May 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: