gcscreenshot1.pnggcscreenshot2.png
When running a Java based RFA provider, the RFA API internally allocates objects in order to handle incoming RWF messages (Screenshot 1). These objects are correctly collected during GC cycle (Screenshot 2), but ideally, I would like to avoid object creation all together.
Is there any way to make the RFA API to pool these objects rather than create and throw away?
Hello @Anton.Crona
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query? If yes, please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
AHS
Hello @Anton.Crona
The RFA Java API lets the application use the OMMPool object factory. The OMMPool is a factory for creating OMM objects and provides an efficient means for releasing and reusing OMM objects created frequently.
However, the OMMPool does not support that specific memory/GC behavior that your have mention.
