pitrou commented on code in PR #41036: URL: https://github.com/apache/arrow/pull/41036#discussion_r1561323596
########## cpp/src/arrow/compute/row/grouper_benchmark.cc: ########## @@ -0,0 +1,127 @@ +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. + +#include "arrow/util/key_value_metadata.h" +#include "arrow/util/string.h" +#include "benchmark/benchmark.h" + +#include "arrow/compute/row/grouper.h" +#include "arrow/testing/gtest_util.h" +#include "arrow/testing/random.h" +#include "arrow/util/benchmark_util.h" + +namespace arrow { +namespace compute { + +constexpr auto kSeed = 0x0ff1ce; +constexpr int64_t kRound = 256; + +static ExecBatch MakeRandomExecBatch(const DataTypeVector& types, int64_t num_rows, + double null_probability, + int64_t alignment = kDefaultBufferAlignment, + MemoryPool* memory_pool = nullptr) { + random::RandomArrayGenerator rng(kSeed); + auto num_types = static_cast<int>(types.size()); + + // clang-format off + auto metadata = key_value_metadata( + { + "null_probability", + "true_probability", + "unique" + }, + { + internal::ToChars(null_probability), + internal::ToChars(null_probability), // for boolean type + internal::ToChars(static_cast<int32_t>(num_rows * 0.5)) // for string type Review Comment: > Both scenarios have use cases. GroupBy/HashJoin are sometimes used for deduplication and in that use case the key is mostly unique (in fact, we hit bugs in our hash-join impl when users tried this case). I see, thanks. Can we clearly mark both kinds of scenarios in the benchmarks? (either as comments in the source code or by using different names for the benchmarks) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
