ImageGear handles all of the memory mapped file operations internally, except for a specific case discussed in the next section. The application only needs to set a few parameters to enable the usage of memory mapped files and adjust it to its needs.

The usage of memory mapped files is controlled by three global control parameters:

• "DIB.FILE_MAPPING.THRESHOLD". Specifies minimum DIB size, in megabytes, for which the memory mapped file shall be used. DIBs that are smaller than this threshold are allocated in physical memory. By default, this parameter is set to 0, which means that the use of memory mapped files is disabled. 1-bit images are always allocated in the physical memory and are not affected by this parameter.
• "DIB.FILE_MAPPING.PATH". Specifies the path to a folder where memory mapped files will be stored. Memory mapped files are temporary files that are created upon DIB creation and deleted upon its deletion. By default, this parameter is set to an empty string, which means that ImageGear will use the system temporary folder for memory mapped files. This parameter is only used when the "DIB.FILE_MAPPING.THRESHOLD" parameter value is greater than zero. This parameter does not affect 1-bit images.

  For best performance, use a separate SSD drive or hard drive for storing memory mapped files, and make sure that the operating system and other applications do not use this drive.

• "DIB.FILE_MAPPING.FLUSH_SIZE". Specifies the maximum size of a memory block in a DIB that can be processed without flushing the memory mapped file. The default value is 200 Mb, which shall be efficient on typical systems that have 4 Gb of RAM. Greater values may improve performance on systems that have a larger amount of RAM. However, making this value too large (comparable to RAM size) will impact the system responsiveness and may lead to allocation failure for large DIBs. This parameter is only used when the "DIB.FILE_MAPPING.THRESHOLD" parameter is greater than zero. This parameter does not affect 1-bit images.

All three parameters DIB.FILE_MAPPING.THRESHOLD, DIB.FILE_MAPPING.PATH, and DIB.FILE_MAPPING.FLUSH_SIZE are taken into account at the time of the DIB creation. After the DIB has been created, changing these parameters will not have an effect on the storage of this DIB, or flush frequency during its processing. However, if some operation replaces the DIB in an IGPage Object (e.g., Resize, Rotate), a new DIB will be created according to the current DIB.FILE_MAPPING.THRESHOLD and DIB.FILE_MAPPING.PATH values, and will then be processed according to the DIB.FILE_MAPPING.FLUSH_SIZE value at the time of the DIB replacement.

The following example tells ImageGear to use memory mapped files for images whose pixel data size is equal to or greater than 500 MB:

Set currentParameter =
IGCoreCtl1.CreateObject(IG_OBJ_GLOBAL_PARAM)
currentParameter.Value.ChangeType IG_DATA_LONG
currentParameter.info = ""
currentParameter.name = "DIB.FILE_MAPPING.THRESHOLD"
currentParameter.Value.Long = 500
IGCoreCtl1.Settings.UpdateParamFrom currentParameter

The following example tells ImageGear to create temporary memory-mapped files in the current directory:

' Keep memory mapping files in the current directory
Set currentParameter =
IGCoreCtl1.CreateObject(IG_OBJ_GLOBAL_PARAM)
currentParameter.Value.ChangeType IG_DATA_STRING
currentParameter.info = ""
currentParameter.name = "DIB.FILE_MAPPING.PATH"
currentParameter.Value.String = "."
IGCoreCtl1.Settings.UpdateParamFrom currentParameter

The following example tells ImageGear to set the flush size to 100 Mb:

' Set the memory mapping flush size to 100 Mb
Set currentParameter =
IGCoreCtl1.CreateObject(IG_OBJ_GLOBAL_PARAM)
currentParameter.Value.ChangeType IG_DATA_LONG
currentParameter.info = ""
currentParameter.name = "DIB.FILE_MAPPING.FLUSH_SIZE"
currentParameter.Value.Long = 100
IGCoreCtl1.Settings.UpdateParamFrom currentParameter

©2016. Accusoft Corporation. All Rights Reserved.