SEZ9 commented on issue #12063: URL: https://github.com/apache/seatunnel/issues/12063#issuecomment-5690946919
@Rangsh thanks for the status update. **Superseded fork table** - Agreed that `34354309911` / `34354315647` were baseline-only on `dev` @ `75fd4ed` and are not a PR before/after. Please confirm once the one-line "superseded" note is on #12173. **Same-worker Benchmarks dispatch** - I do not have dispatch permission on `apache/seatunnel` either, so I cannot trigger the run or validate the input names myself; this remains gated on a committer with workflow dispatch permission. Whoever triggers it, please drop the run link in this thread. - Agreed on holding `7948e2640` as the measurement head for #12173 in the meantime. **Plan for `runningJobGrowth` @ `initialStoredJobCount=1000`** - Your two-step approach sounds reasonable: one follow-up same-worker dispatch with more JMH sampling on the same selector at `7948e2640`, and if CV still sits in the ~15%+ band, label that cell as inherently noisier and lean on the fixture causal evidence plus the other three cells. Please state that reading explicitly next to the table when you post it. **Remaining asks** 1. Confirm the "superseded" note is on #12173. 2. Once the same-worker run finishes, publish the Score / Error / CV table for both methods at `initialStoredJobCount=0` and `1000` from that single host, replacing the fork table. 3. Include the explicit CV reading and whether the follow-up higher-sampling dispatch is needed alongside the table. <!-- streview-comment:1073 --> -- 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]
