Sure. I'll do it.


Regards,
Cheng



 




------------------ Original ------------------
From:                                                                           
                                             "dev"                              
                                                      <[email protected]&gt;;
Date:&nbsp;Thu, Jul 31, 2025 08:08 PM
To:&nbsp;"dev"<[email protected]&gt;;

Subject:&nbsp;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]&gt; wrote:

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

Reply via email to