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

Benchmark SS #17322

Closed
Tracked by #17041
alexanderbez opened this issue Aug 8, 2023 · 1 comment
Closed
Tracked by #17041

Benchmark SS #17322

alexanderbez opened this issue Aug 8, 2023 · 1 comment
Assignees
Labels

Comments

@alexanderbez
Copy link
Contributor

alexanderbez commented Aug 8, 2023

Each SS backend engine should be benchmarked using a large enough and consistent data set, preferably one we use for SC as well.

In addition, for each backend engine (RocksDB, PebbleDB, BTree/SQLite), ensure the default configurations are evaluated correctly.

@github-actions github-actions bot added the needs-triage Issue that needs to be triaged label Aug 8, 2023
@alexanderbez alexanderbez added C:Store WG: Storage and removed needs-triage Issue that needs to be triaged labels Aug 8, 2023
@alexanderbez
Copy link
Contributor Author

I'm going to mark #17280 as closing this. We have baseline benchmarks and we can use them to add further benchmarks (just by updating the engines map) to further benchmarks the existing engines with different tuning options.

@alexanderbez alexanderbez self-assigned this Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant