-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat: Add support for --mem-pool-type and --memory-limit options to multiple benchmarks #14642
feat: Add support for --mem-pool-type and --memory-limit options to multiple benchmarks #14642
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense to me -- thank you @Kontinuation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested some queries and it's working well, thank you!
Thanks again @Kontinuation and @2010YOUY01 |
This PR is merged but for some reason the github ui is not showing it: |
…ultiple benchmarks (apache#14642) * Add support --mem-pool-type and --memory-limit options for all benchmarks * Add --sort-spill-reservation-bytes option
Which issue does this PR close?
--memory-limit
for all benchmarking tools #14641.Rationale for this change
I had to run sort-tpch queries with memory limit when testing fixes for memory related issues, so I decide to add
--memory-limit
option for most of the benchmarking cli tools. I wish other developers could find it handy.What changes are included in this PR?
This PR adds 2 cli options
--memory-limit
,--mem-pool-type
and--sort-spill-reservation-bytes
to the following benchmarking tools:dfbench
subcommands:sort
,sort-tpch
,clickbench
,h2o
,imdb
,parquet-filter
tpch
imdb
external_aggr
already supports--memory-limit
, it now accepts--mem-pool-type
. The default value of--mem-pool-type
isfair
so the behavior remains unchanged.Are these changes tested?
The changes were tested manually.
Are there any user-facing changes?
No. The benchmarking guide has not covered every option so hopefully the developers could find these options themselves using
--help
.