Load testing reference management

[mahesh-hegde]

We need to load test a few scenarios to get a certainty that resource management is proper.

These tests should be done with generated bindings, and if possible, with the support library.

• Test large number of JNI references without freeing.

  • Keep references in list to prevent NativeFinalizer from kicking off.
  • There's a limit imposed by the JNI itself. However, a normal app should be able to sustain global ref count of low 1000s.

• Test large number of JNI calls with scoped reference management:

  • Possibly in 10K - 100K calls wrapped in arena calls.

• Verify a call returning primitive type does not create any JNI references.

• Verify that class references are being cached.

• Verify native finalizers are being invoked after a forced GC, and that JNI references are actually being freed.

• Verify a reference is not inadvertently deleted with passage of time.

  • Keep a reference for 10 seconds, in the middle force-execute GC, then use it again.