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.

Sign up for GitHub

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

Jump to bottom

Estimator replay IO traces on RocksDB #7058

Open
jakmeier opened this issue Jun 17, 2022 · 0 comments
Open

Estimator replay IO traces on RocksDB #7058

jakmeier opened this issue Jun 17, 2022 · 0 comments
Assignees
@jakmeier
Labels
A-params-estimator Area: runtime params estimator T-contract-runtime Team: issues relevant to the contract runtime team

Comments

@jakmeier
Copy link
Contributor

After implementing #7053, the estimator should be able to take those traces and replay them on RocksDB for an isolated IO cost measurement.
@jakmeier jakmeier added T-contract-runtime Team: issues relevant to the contract runtime team A-params-estimator Area: runtime params estimator labels Jun 17, 2022
@jakmeier jakmeier self-assigned this Jun 17, 2022
This was referenced Jun 17, 2022
Open
Closed
jakmeier added a commit to jakmeier/nearcore that referenced this issue Aug 19, 2022
@jakmeier
feat: Replay IO traces on estimator for statistics
66dce09 
This introduces the ability to replay IO traces on the estimator.
Example usage in `runtime/runtime-params-estimator/README.md`.

While it is not used for estimations, yet, it is already a subcommand of
the estimator. The idea is that for near#7440 a lot of code can be reused.
Further, replaying on the estimator is required for near#7058 and near#7059.
This was referenced Aug 19, 2022
Merged
Open
jakmeier added a commit that referenced this issue Oct 18, 2022
@jakmeier
feat: Replay IO traces on estimator for statistics (#7445)
32be8e3 
This introduces the ability to replay IO traces on the estimator.
Example usage in runtime/runtime-params-estimator/README.md.

While it is not used for estimations, yet, it is already a subcommand of
the estimator. The idea is that for #7440 a lot of code can be reused.
Further, replaying on the estimator is required for #7058 and #7059.
nikurt pushed a commit that referenced this issue Nov 9, 2022
@jakmeier @nikurt
feat: Replay IO traces on estimator for statistics (#7445)
2eb3a51 
This introduces the ability to replay IO traces on the estimator.
Example usage in runtime/runtime-params-estimator/README.md.

While it is not used for estimations, yet, it is already a subcommand of
the estimator. The idea is that for #7440 a lot of code can be reused.
Further, replaying on the estimator is required for #7058 and #7059.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jakmeier jakmeier

Labels
A-params-estimator Area: runtime params estimator T-contract-runtime Team: issues relevant to the contract runtime team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jakmeier and others