Devops #4475
Merged
Devops #4475
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Lezek123
approved these changes
Dec 1, 2022
| --out-peers 128 | ||
| --in-peers 64 \ | ||
| --out-peers 64 \ | ||
| --max-runtime-instances 64 |
There was a problem hiding this comment.
Since we have 1 GB heap allocation set for WASM, isn't setting this to such a high value putting the node at risk of memory overflow?
There was a problem hiding this comment.
Yes perhaps this value is a bit large. I suppose it should be manually updated on each rpc node depending on its physical RAM. The default is 8 instances. Maybe 16 or 20 would be better values for a machine with 32GB memory for example?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Final tweaks for network deployment