DanielLeens commented on issue #11580: URL: https://github.com/apache/seatunnel/issues/11580#issuecomment-5124712471
Thanks for the thoughtful follow-up. I agree that this direction makes sense, and I also agree that it should not stay only as a small standalone feature issue if the target is a long-lived performance regression gate. My suggestion is: 1. keep this issue as the first-stage task for a runnable baseline harness; 2. open a separate umbrella/STIP discussion for the long-term benchmark framework; 3. make the first phase intentionally small: one Zeta baseline workload, reproducible environment assumptions, machine-readable output, and clear metric definitions; 4. defer PR-gating policy until we have enough repeatable data to understand variance, required resources, and false-positive risk. For the umbrella/STIP, the most useful content would be the phased roadmap, supported workload matrix, metrics to collect, environment isolation rules, comparison format, and explicit non-goals for the first implementation. After that is written down, this issue can link to it as the first concrete implementation slice. -- 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]
