Some, but not all scripts report "load time" for stateless engines (time to download parquet and sync)

Open
#944 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
shell

Research direction

Start with the linked datafusion-partitioned/results/20260511/c6a.4xlarge.json file and review the load_time addition from commit 6d5ee0a and pull request #860. Compare how the stateless-engine scripts report load time, clarify whether raw Parquet download and fsync belong in the measure, and consider the work complete when reporting is consistent across those engines.

Written by the indexing model from the issue text.

Description

While reviewing recent DataFusion results, I found there is now a "load time" reported for DataFusion

For example, this link

Image

Here is the source file that has 17:
https://github.com/ClickHouse/ClickBench/blob/a377499b950b17b2d96b79625375d57b18a36634/datafusion-partitioned/results/20260511/c6a.4xlarge.json#L10

It was added in https://github.com/ClickHouse/ClickBench/commit/6d5ee0a68573bbb481fdb8f799cc3348a9bb0634 which was part of a large refactoring in https://github.com/ClickHouse/ClickBench/pull/860

Image

I am not sure if you intended the load_time to include the download / fsync time for the raw parquet dataset, but if you did I would request that we measure it consistently across stateless engines

Dominant language
Shell
Stars
1.1k
Forks
328
Avg merge
4h 12m
Merged PRs (30d)
605

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from ClickHouse/ClickBench

All issues in ClickHouse/ClickBench

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.