Sure. I'll do it.
Regards,
Cheng
------------------ Original ------------------
From:
"dev"
<[email protected]>;
Date: Thu, Jul 31, 2025 08:08 PM
To: "dev"<[email protected]>;
Subject: Re: [DISCUSS] A new repository for fluss-benchmark
Hi Cheng,
Could you start a VOTE for the new repository? I think it requires a
consensus approval like FIP process that needs 3+ committers binding votes
in 72 hours.
Best,
Jark
On Thu, 31 Jul 2025 at 16:37, Wang Cheng <[email protected]> wrote:
> Hi Jark, fluss-benchmark directory has been renamed to fluss-jmh (
> https://github.com/apache/fluss/issues/1428). Could you please create a
> new repository named fluss-benchmarks for us?
>
>
>
> Regards,
> Cheng
>
>
>
> &nbsp;
>
>
>
>
> ------------------&nbsp;Original&nbsp;------------------
> From:
>
"dev"
>
<
> [email protected]&gt;;
> Date:&nbsp;Wed, Jul 30, 2025 07:13 PM
> To:&nbsp;"dev"<[email protected]&gt;;
>
> Subject:&nbsp;Re: [DISCUSS] A new repository for fluss-benchmark
>
>
>
> Thanks, Wang, for initiating this discussion.
>
> I think establishing a dedicated set of benchmarks for Fluss is a great
> idea.
>
> I suggest using the repository name `fluss-benchmarks` ?? the plural form
> makes sense as it will host multiple benchmarking frameworks and workloads.
>
> Additionally, there is already a module named fluss-benchmark in the
> apache/fluss repository. To avoid confusion between the module and the new
> benchmarks repo, I suggest renaming the existing module to fluss-jmh. This
> would better reflect its purpose as a collection of microbenchmarks using
> JMH.
>
> Best,
> Jark
>
>
>
> On Wed, 30 Jul 2025 at 15:23, yuxia <[email protected]&gt;
> wrote:
>
> &gt; Thanks Cheng for driving this work. It's really important for
Fluss.
> For
> &gt; me, the name `fluss-e2e` is not straight forward. Since it's
mainly
> for
> &gt; benchmark,
> &gt; I'd like suggest name it with benchmark related, such as
> &gt; fluss-benchmark(flink name flink-benchmark), or
> fluss-bench(clickhosue name
> &gt; clickbench).
> &gt;
> &gt; Best regards,
> &gt; Yuxia
> &gt;
> &gt; ----- ???????? -----
> &gt; ??????: "Wang Cheng" <[email protected]&gt;
> &gt; ??????: "dev" <[email protected]&gt;
> &gt; ????????: ??????, 2025?? 7 ?? 28?? ???? 5:51:06
> &gt; ????: [DISCUSS] A new repository for fluss-benchmark
> &gt;
> &gt; Hi everyone,
> &gt;
> &gt;
> &gt; I'm writing to propose the creation of a new repository named
> fluss-e2e.
> &gt; This repository will house a comprehensive suite of benchmarking
tools
> &gt; designed to simplify performance evaluation of Fluss clusters
across
> &gt; diverse scenarios.
> &gt;
> &gt;
> &gt; For the primary-key table benchmark, I've developed a
proof-of-concept
> &gt; (PoC) implementation [1], which leverages Alibaba Cloud Hologres'
> &gt; end-to-end performance testing tool [2][3]. For the log table
> benchmark, we
> &gt; can adapt the Open Messaging Benchmark (OMB) framework [4] as a
> &gt; foundational starting point.
> &gt;
> &gt;
> &gt; Importantly, fluss-e2e differs significantly from the existing
> &gt; fluss-benchmark directory [5] in the current Fluss mainline. The
> legacy
> &gt; fluss-benchmark focuses on launching a local pseudo-distributed
Fluss
> &gt; cluster and solely evaluates log tables. In contrast, fluss-e2e
aims
> to
> &gt; provide a robust, multi-scenario performance testing suite that
can
> &gt; validate any Fluss cluster deployment - whether primary-key or log
> tables,
> &gt; local or distributed.
> &gt;
> &gt;
> &gt; Lastly, any ideas for a better name for this repo?
> &gt;
> &gt;
> &gt; Looking forward to your feedback :)
> &gt;
> &gt;
> &gt;
[1]&amp;nbsp;https://github.com/xx789633/fluss-e2e-performance-tool
> &gt <https://github.com/xx789633/fluss-e2e-performance-tool&gt>;
> [2]&amp;nbsp;
> &gt;
>
https://www.alibabacloud.com/help/en/hologres/user-guide/best-practices-for-performance-tests-on-data-writes-data-updates-and-point-queries
> &gt
>
<https://www.alibabacloud.com/help/en/hologres/user-guide/best-practices-for-performance-tests-on-data-writes-data-updates-and-point-queries&gt>;
> [3]&amp;nbsp;
> &gt;
>
https://github.com/aliyun/alibabacloud-hologres-connectors/tree/master/holo-e2e-performance-tool
> &gt
>
<https://github.com/aliyun/alibabacloud-hologres-connectors/tree/master/holo-e2e-performance-tool&gt>;
> [4]&amp;nbsp;https://openmessaging.cloud/docs/benchmarks/
> &gt; [5]&amp;nbsp;
> https://github.com/apache/fluss/tree/main/fluss-benchmark
> &gt
<https://github.com/apache/fluss/tree/main/fluss-benchmark&gt>;
> &gt;
> &gt;
> &gt; Regards,
> &gt; Cheng
> &gt;
> &gt;
> &gt;
> &gt; &amp;nbsp;
> &gt;