Changes for page Volume Mapping (On-premise)
Last modified by Erik Bakker on 2024/08/26 12:37
From version 47.1
edited by Erik Bakker
on 2022/10/31 15:15
on 2022/10/31 15:15
Change comment:
There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2022/10/31 11:27
on 2022/10/31 11:27
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -76,16 +76,6 @@ 76 76 77 77 === 3.3 Temporary file system === 78 78 79 -If you do not want to work with **persistent** data but have a need for **non-persistent** data the temporary file system option is for you. This way you can increase the container’s performance by avoiding writing into the container’s writable layer. 80 - 81 -[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]] 82 - 83 -To configure this option you need a target location. On top of that you can define the maximum size of the temporary file system. 84 - 85 -[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage-filled-in.png]] 86 - 87 -{{warning}}We strongly advice to define this number as that way you can limit the potential impact this solution can have on the stability of your machine.{{/warning}} 88 - 89 89 === 3.4 Named pipe === 90 90 91 91 The named pipe option can be selected but we yet have to see a valid use case within the context of eMagiz for using this option. Therefore we won't discuss this option further in this microlearning.