Rangsh commented on issue #12063:
URL: https://github.com/apache/seatunnel/issues/12063#issuecomment-5692681864

   @SEZ9 thanks — completing the asks that are on our side.
   
   ### 1. Superseded note on #12173 — confirmed
   The one-line superseded note was already on 
[#12173](https://github.com/apache/seatunnel/pull/12173) (PR comment from 
2026-09-14). I have also added the same **Superseded** callout to the PR 
description under Evidence, covering fork runs 
[`34354309911`](https://github.com/Rangsh/seatunnel/actions/runs/34354309911) / 
[`34354315647`](https://github.com/Rangsh/seatunnel/actions/runs/34354315647) 
as baseline-only on `dev` @ `75fd4ed` (not a PR before/after).
   
   ### 2. Same-worker Benchmarks — still needs a committer
   I still cannot dispatch on `apache/seatunnel` (403), and @SEZ9 noted the 
same. Measurement head remains **`7948e2640`**.
   
   @nzw921rx (or another committer with workflow dispatch permission) — could 
you please trigger **Benchmarks** on `apache/seatunnel` with:
   
   | Input | Value |
   | --- | --- |
   | `seatunnel_ref` | `dev` |
   | `benchmarks` | `IMapJobStorageBenchmark` |
   | `custom_benchmarks` | 
`IMapJobStorageBenchmark.(runningJobGrowth\|completedJobHistoryGrowth)$` |
   | `pr_number` | `12173` |
   
   Expected same-worker order: **baseline → PR → PR → baseline**. Please drop 
the run link in this thread when it starts.
   
   ### 3. After that run finishes
   I will post the Score / Error / CV table for both methods at 
`initialStoredJobCount=0` and `1000` from that single host (replacing the 
superseded fork table), with an explicit CV reading for `runningJobGrowth` @ 
`1000` and whether a higher-sampling follow-up is needed — per the two-step 
plan already aligned with @SEZ9.


-- 
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]

Reply via email to