APIs for Java Developers

public class DelayGcContext
extends java.lang.Object

This class allows to instruct Javonet that for particular block of code all
garbage collector events should be grouped into batches and executed when batch size
reaches 100 000 objects or waits 30 seconds.

Delay GC context should be used in case when huge load of short living .NET object references (NObjects)
are expected to be created in short time. Batching garbage collector events might highly increase the performance
and lower the amount of transmission between JAVA and .NET process.

Delayed GC context should be considered when part of code generates huge number of calls to .NET that returns
references to other objects and performs further operations on these objects.

Applicable number of calls to be classified as huge start from 500 000 NObject instances per minute. However the
solution could be applied in other cases as well if performance improvement will be detected by experiment.

Important:It should be noticed that using delay GC context might cause increased memory consumption.

Delay GC context groups objects for all threads in which it was initialized in single buffer. When buffer reaches
100 000 objects or times out 30 seconds then Javonet flushes the collect events to .NET process and .NET GC collects
the objects.

Usage sample

Delay GC context should be used by calling Begin() method before the block of code to be wrapped
and End() at the end of the block. Delay GC context affects only objects created in the same thread
in which context was started.

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