changeset 5155:20911302c6e7

doc
author Alain Mazy <am@osimis.io>
date Wed, 01 Feb 2023 19:32:14 +0100
parents dce028ec0fe9
children 2020c2e479d3
files OrthancServer/Resources/ImplementationNotes/memory_consumption.txt
diffstat 1 files changed, 16 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/OrthancServer/Resources/ImplementationNotes/memory_consumption.txt	Wed Feb 01 19:24:58 2023 +0100
+++ b/OrthancServer/Resources/ImplementationNotes/memory_consumption.txt	Wed Feb 01 19:32:14 2023 +0100
@@ -37,7 +37,22 @@
 4                  out-of-memory crash                ~  345 MB
 5..20                                                 ~  380 MB (stable)
 
-Note: the use of malloc_trim does not guarantee that Orthanc will never reach a
+3nd test: memory constrained Docker containers
+..............................................
+
+In this last test, we lowered the memory allocation to 300MB and have been able to
+run the first test script for at least 7 minutes (we did not try longer !).  The 
+consumed memory is most of the time around 99% but it seems that the memory constrain
+is handled correctly.  Note that, in this configuration, 128 MB are used by the Dicom
+Cache.
+
+The same test without malloc_trim could never run for more than 35 seconds.
+
+
+Note: 
+----
+
+The use of malloc_trim does not guarantee that Orthanc will never reach a
 out-of-memory error, especially on very constrained systems.  
 Depending on the allocation pattern, the Orthanc memory can get
 very fragmented and increase since malloc_trim only releases memory