US 12,217,074 B2
Selective injection of GC safepoints for JNI invocations
Michihiro Horie, Ageo (JP); Kazunori Ogata, Soka (JP); and Hiroshi Horii, Tokyo (JP)
Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION, Armonk, NY (US)
Filed by INTERNATIONAL BUSINESS MACHINES CORPORATION, Armonk, NY (US)
Filed on Oct. 28, 2020, as Appl. No. 17/082,250.
Prior Publication US 2022/0129290 A1, Apr. 28, 2022
Int. Cl. G06F 9/455 (2018.01); G06F 8/41 (2018.01); G06F 9/50 (2006.01); G06F 12/02 (2006.01)
CPC G06F 9/45558 (2013.01) [G06F 8/4434 (2013.01); G06F 9/45504 (2013.01); G06F 9/5077 (2013.01); G06F 12/0253 (2013.01); G06F 12/0269 (2013.01); G06F 2009/45575 (2013.01); G06F 2009/45583 (2013.01); G06F 2009/45591 (2013.01); G06F 2209/5022 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method for managing Garbage Collection (GC) safepoints in a Virtual Machine (VM), comprising:
removing a GC safepoint responsive to any of low GC frequency conditions based on (i) a heap occupancy ratio, determined by calculating a proportion of used memory to total available heap memory, prior to executing a target native method being less than a threshold occupancy amount percentage and (ii) a most recent GC pause time being shorter by a threshold pause time amount percentage than an execution time of the target native method; and
reducing operational interruptions and latency caused by utilizing full memory fences at the GC safepoint by performing garbage collection with the GC safepoint under high GC frequency conditions, as conditions other than low GC frequency conditions, determined to enhance performance of an application, and removing low GC frequency safepoints determined to be unnecessary to avoid utilization of the full memory fences that degrade performance of the application, the removing low GC frequency safepoints being executed by the VM automatically based on the heap occupancy ratio and the most recent GC pause time.