aldettinger commented on issue #8027: URL: https://github.com/apache/camel-quarkus/issues/8027#issuecomment-3612218371
> [@aldettinger](https://github.com/aldettinger) just for my knowledge, can you give me more context about this detection of performance regression ? What exactly is the scope checked ? The crux of it is to run the same sample application compiled against different versions of camel-quarkus and measure the mean throughput. The point is more to check than camel-quarkus versions behave the same than determine any kind of capacity. JDK regressions are not in scope. So far we have never found any camel-quarkus regressions but spotted a couple of camel and quarkus ones. What else to say, it's upstream, it's not meant to be a full blown performance harness, it tries to shift left a basic performance review so that we could react as soon as the staging release phase. As such, the design is minimal, support running on community member machines, with a nominal duration reduced to the strict minimum. The original intent is to automate as much as possible and reduce the maintenance burden. Hope this helps, feel welcome if any more clarifications are needed. -- 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]
