DanielLeens commented on issue #12063: URL: https://github.com/apache/seatunnel/issues/12063#issuecomment-5541694634
Thanks @Rangsh. I checked current dev and the open PR set: the IMap job-storage benchmark foundation is present, and no open PR currently targets runningJobGrowth or completedJobHistoryGrowth. The repository rejected the assignee update for this account, so no GitHub assignment metadata was changed; this thread records the accepted claim for coordination. Please begin with reproducible evidence rather than a speculative production change: run the named methods with the same runner class, JDK, arguments, and storage configuration; attach the JMH JSON plus CPU, wall, lock, GC, or JFR evidence; and identify whether the variance is in the fixture, Hazelcast/MapStore path, serialization/allocation, or the execution environment. If the evidence identifies a production bottleneck, keep the change limited to that path, preserve running and completed job-state durability, add targeted behavior coverage, and include comparable before/after results. Please link the focused PR here. -- 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]
