aldettinger commented on issue #5452:
URL: https://github.com/apache/camel-quarkus/issues/5452#issuecomment-1783188794
@orpiske Once variability is erased, the 4.0.1 performance drop might not be
such a big issue.
Furthermore, if we look at it from LTS to LTS, we end up with just a small
penalty:
```
Camel Quarkus Throughput Performance Increase Compared to Previous Version
Camel Quarkus version | Duration | JVM req/s [%increase] | Status |
-----------------------------------------------------------------------------
2.16.0 | 45m | 38276.70 req/s [+0.00%] | OK |
3.2.1 | 45m | 37042.86 req/s [-3.22%] | OK |
```
Hope this could help to balance effort/reward that could be expected in this
area.
At the end of the day, the issues are surfaced that way in Camel Quarkus:
+ Camel Quarkus 3.2.1 LTS -> `-3%` small regression, that's not blocking
+ Camel Quarkus 3.5.0 non LTS -> `-30%`, we would recommend users to stay
on 3.4.x
+ Camel Quarkus 3.6.x next release -> we'll check it's on par with 2.16.x
when we adopt Camel 4.2
--
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: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
