Batching GC with DelayGcContext

Batching GC with DelayGcContext

There could be a scenario where huge amount of short living instances of .NET objects are being created on Java side. Huge amount is estimated above 500 000 objects per minute. It could be when .NET side triggers event subscribed on Java side with many reference-type arguments (NObjects) or when multiple objects are being created for executing business logic calculation in big loops. In each of these cases when memory utilization is increased Java garbage collector will quickly start collecting NObject instances. Javonet forwards such calls to .NET side. When there are more then 500,000 collections per minute the overall application performance might be affect by additional GC call for each of the NObject instances.

In such cases the new DelayGcContext class (introduce in Javonet 1.4) could be applied. The best way to determine if DelayGcContext is required is by performing performance tests with suspicious piece of code. DelayGcContext class allows to indicate the beginning and the end of the code for which the garbage collection calls should be batched. The GC buffer for these objects will be flushed to .NET side every time the buffer size exceeds 100 000 objects pending in the queue or when 30 seconds pass.

The beginning of delayed garbage collection section should be indicated by calling static “Begin” method on DelayGcContext class and terminated by calling “End” method as presented on the snippet below:

 for (int i=0; i<5000000;i++) {
 	NObject objA = Javonet.New("SampleType",i);
 	NObject objB = objA.get("B");
 	(... some other operations ...)
 	NObject objC = objB.getRef("subProp").getRef("subProp").invoke("GetC");

        //in this block objA, objB, and objC instance if not referenced in other parts of code
        //will be subjected for garbage collection after each iteration of the loop

More about DelayGcContext you can read in our docs section for DelayGcContext class.