Skip to content
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

automated measurement of contract CPU/computron/memory usage #5295

Open
warner opened this issue May 5, 2022 · 1 comment
Open

automated measurement of contract CPU/computron/memory usage #5295

warner opened this issue May 5, 2022 · 1 comment
Labels
enhancement New feature or request SwingSet package: SwingSet

Comments

@warner
Copy link
Member

warner commented May 5, 2022

What is the Problem Being Solved?

As discussed in #4219 (comment) , before we can confidently enable per-delivery computron limits, we need to know that none of our contracts are at risk of exceeding them.

That means some sort of automated test which pays close attention to the metering results of startVat/buildRootObject (contract startup), plus a few typical deliveries. It should also track how large the contract bundles are (in bytes), to compare against transaction size limits.

Description of the Design

I'm guessing this would fit into @mhofman 's loadgen framework, or the automation that @arirubinstein has built.

@warner
Copy link
Member Author

warner commented May 5, 2022

The reporting on this should give us an alert if the usage comes within 50% of whatever limits we impose on vats in the chain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request SwingSet package: SwingSet
Projects
None yet
Development

No branches or pull requests

2 participants