aldettinger commented on issue #5743:
URL: https://github.com/apache/camel-quarkus/issues/5743#issuecomment-1943792111
Hi @brianmolinaspring,
Many thanks for contributing to Camel Quarkus :+1:
Trying to summarize there is a microservice implemented with camel-quarkus
3.7.1 that is consuming/releasing memory. The microservice is assumed to be
inactive / doing nothing.
A peak of 250 MiB of memory is reached every 40 minutes when the garbage
collector probably reclaims the memory.
So far, this behavior is reproduced:
+ in native mode with a microservice deployed on kubernetes
+ in dev mode with the rest-json camel-quarkus example
Please amend if above summary is not correct.
The main hytothesis would be that there is actually a bit of activity
occurring under the hood.
A way to validate this hypothesis would be to collect some information
before the memory is reclaimed.
Especially collecting a dump of the java class histogram showing the most
used classes would be helpful.
Note that investigating in dev mode could be misleading and is not
recommended. Investigating in jvm or native mode should help. And most of the
time investigating in jvm mode is sufficient to understand what's happening.
--
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
