orpiske commented on issue #5452: URL: https://github.com/apache/camel-quarkus/issues/5452#issuecomment-1779799762
@aldettinger Yes, something like that would help. I'd recommend something like this (that's what I use for Camel Core): ``` -agentpath:/path/to/libasyncProfiler.so=start,ann,threads,event=cpu,file=report.html ``` You probably don't need to adjust the interval - I believe the default of 10ms used by the profiler is enough, but we can adjust if we don't collect enough detail. Also, if I understand it correctly, your tests run for a very long time ... We don't need that much and, probably, around 5-10 minutes should give enough information. > Looking at the git logs, there are quite some commits with impact on core. So, maybe we'll need a kind of Camel only reproducer at some points to help ensure the regression is fixed ? Yes. The core of Camel Core has been very much active recently 😁 I have a load generator for core but it's mostly for local components (ie.: `seda`, `disruptor`, `direct`, etc). It could be modified, but I don't have the tooling to generate external load (besides Kafka). -- 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
