oxidecomputer / oxidecomputer/omicron

Want benchmarking tool for OxQL

Open
#6,127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

clickhouse Metrics oxql
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

It would be very nice to have a tool that lets us benchmark the OxQL implementation. I'd like to track at least the total query duration, and for each ClickHouse SQL query we run: (1) duration, (2) maximum memory consumption, (3) maximum CPU usage.

We already keep track of the IDs of each ClickHouse SQL query in the QueryResults that are returned from the OxQL interface, so I could imagine a tool that:

  • Loads some data of various sizes (number of fields and number of samples)
  • Runs some range of queries
  • Asks ClickHouse via the system.query_log table for the details of all the contained queries
  • Spits it out into a simple format like CSV, so we can print summaries or statistics, make plots, etc.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the OxQL interface and the QueryResults that retain ClickHouse query IDs. Review how the tool could load data of varying sizes, run a range of queries, and use ClickHouse's system.query_log for query details. Done means reporting total query duration plus per-query duration, maximum memory, and maximum CPU in a simple format such as CSV.

Written by the indexing model from the issue text.

Assessment

Tech stack
clickhouse, rust, sql
Domain
databases, performance, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.