Make text about much data ready for review

frankframework · Jul 2, 2024 · 0eda6d6 · 0eda6d6
1 parent 0f56862
commit 0eda6d6
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 15 deletions.
diff --git a/docs/source/advancedDevelopment/advancedDevelopment.rst b/docs/source/advancedDevelopment/advancedDevelopment.rst
@@ -13,5 +13,4 @@ Chapter :ref:`gettingStarted` provides the basics of Frank development. This cha
    dockerDevel/dockerDevel
    narayana/narayana
    deployment/maven
-   streaming/streaming
-
+   muchData/muchData
diff --git a/docs/source/advancedDevelopment/muchData/muchData.rst b/docs/source/advancedDevelopment/muchData/muchData.rst
@@ -0,0 +1,8 @@
+*Work in progress*
+
+About large messages
+====================
+
+The Frank!Framework treats large messages in a special way to save memory. Frank developers sometimes need some knowledge about this to fix issues with their Frank applications. There is a property ``message.max.memory.size`` to configure the threshold: messages larger than this size are treated specially. Large messages are written to a temporary file before they are processed. Under Linux, they are typically stored in the ``/tmp`` folder. If this folder is on a small disk partition, an OutOfMemory Java exception may result. As an exception, messages that are already in a file are not copied to a temp file before they are processed. This exception typically applies to the contents of a file handled by a ``LocalFileSystemPipe``. This exception is more general: the Frank!Framework has intelligence to determine whether a file has been stored already - it is only written to a temp file if it is not available otherwise.
+
+TODO: What is different before 7.9 from the behavior from 7.9 and later?
diff --git a/docs/source/advancedDevelopment/streaming/streaming.rst b/docs/source/advancedDevelopment/streaming/streaming.rst