SEZ9 commented on issue #12063: URL: https://github.com/apache/seatunnel/issues/12063#issuecomment-5707358319
@Rangsh thanks — confirming both items. **1. Superseded note — done.** The one-line note plus the Superseded callout in the PR description under Evidence cover what was asked. Fork runs [`34354309911`](https://github.com/Rangsh/seatunnel/actions/runs/34354309911) / [`34354315647`](https://github.com/Rangsh/seatunnel/actions/runs/34354315647) are now clearly marked as baseline-only on `dev` @ `75fd4ed`, not a PR before/after. Nothing further needed there. **2. Same-worker Benchmarks dispatch — still open.** Your dispatch request (inputs as listed in your table, expected order baseline → PR → PR → baseline at head `7948e2640`) is complete as written; it just needs a committer with workflow dispatch permission to action it. I have nothing to add to the inputs. **3. After the run** — agreed on your plan: post the Score / Error / CV table for both methods at `initialStoredJobCount=0` and `1000` from that single host, with the explicit CV reading for `runningJobGrowth` @ `1000` and whether a higher-sampling follow-up is warranted, per the two-step plan. Please keep the measurement head at `7948e2640` (spotless-only on top of `c553a8c04`) until that run is captured so the table and the head stay aligned. Remaining asks: - Whoever dispatches the Benchmarks run: please drop the run link in this thread when it starts. - @Rangsh: once it finishes, post the same-worker table here as described. No other action needed from you right now. <!-- streview-comment:1100 --> -- 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]
