-
Notifications
You must be signed in to change notification settings - Fork 73
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
Collect EOS-VM-OC memory usage from the mainnet #1159
Labels
Comments
Will also collect EVM contract memory usage. |
The steps for this are
|
Below are result from April 12 mainnet snapshot and syncing to May 23. For EVM contracts, 1 MB (16 pages), covers 88% of actions. 2 MB will cover 95% actions. EVM Contracts
Native contracts
|
Information has been collected. Close this issue. Will collect new on on a future date if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is one of work items identified in eosnetworkfoundation/product#149 for eosnetworkfoundation/product#161.
To configure a reasonable memory slice count for EOC-VM-OC, we need to understand typical memory usages.
This work will use a January 2022 snapshot from the mainnet, instrument EOS-VM-OC code to keep track and report
the largest number of linear memory the current code uses, start nodeos from the snapshot and sync with a mainnet peer node,
collect memory usage, and find max and 95 percentile of number of linear memory pages used by all contract codes.
The text was updated successfully, but these errors were encountered: