From ca207636192efa0b1b9c6e1ebf754183a9d52783 Mon Sep 17 00:00:00 2001 From: Maxime Michel Date: Thu, 5 Dec 2019 04:47:53 +0100 Subject: [PATCH] Mention the new % unit for maxBytes and maxPhysicalBytes in Memory management documentation (#8435) (#8461) Signed-off-by: Maxime Michel --- docs/deeplearning4j/templates/config-memory.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/deeplearning4j/templates/config-memory.md b/docs/deeplearning4j/templates/config-memory.md index 0e1169e52..4660baaf8 100644 --- a/docs/deeplearning4j/templates/config-memory.md +++ b/docs/deeplearning4j/templates/config-memory.md @@ -30,9 +30,9 @@ With DL4J/ND4J, there are two types of memory limits to be aware of and configur * `-Xmx` - this allows you to specify JVM heap memory limit (maximum, at any point). Only allocated up to this amount (at the discretion of the JVM) if required. -* `-Dorg.bytedeco.javacpp.maxbytes` - this allows you to specify the off-heap memory limit. +* `-Dorg.bytedeco.javacpp.maxbytes` - this allows you to specify the off-heap memory limit. This can also be a percentage, in which case it would apply to maxMemory. -* `-Dorg.bytedeco.javacpp.maxphysicalbytes` - this specifies the maximum bytes for the entire process - usually set to `maxbytes` plus Xmx plus a bit extra, in case other libraries require some off-heap memory also. Unlike setting `maxbytes` setting `maxphysicalbytes` is optional +* `-Dorg.bytedeco.javacpp.maxphysicalbytes` - this specifies the maximum bytes for the entire process - usually set to `maxbytes` plus Xmx plus a bit extra, in case other libraries require some off-heap memory also. This can also be a percentage (>100%), in which case it would apply to maxMemory. Unlike setting `maxbytes` setting `maxphysicalbytes` is optional Example: Configuring 1GB initial on-heap, 2GB max on-heap, 8GB off-heap, 10GB maximum for process: