|
From: | A.R. Burgers |
Subject: | [Octave-bug-tracker] [bug #53943] memory usage explodes on a javaMethod call |
Date: | Mon, 21 May 2018 15:18:07 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299 |
Follow-up Comment #2, bug #53943 (project octave): Here is I think a relevant discussion of this topic: https://stackoverflow.com/questions/4667483/how-is-the-default-java-heap-size-determined The 35Gb is 1/4 of the physical memory of 145Gb, which is the default MaxHeapSize java -XX:+PrintFlagsFinal -version | grep HeapSize uintx ErgoHeapSizeLimit = 0 {product} uintx HeapSizePerGCThread = 87241520 {product} uintx InitialHeapSize := 2147483648 {product} uintx LargePageHeapSizeThreshold = 134217728 {product} uintx MaxHeapSize := 32126271488 {product} java version "1.7.0_161" Java(TM) SE Runtime Environment (build 1.7.0_161-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.161-b13, mixed mode) _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53943> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |