HTTP I/O buffer

When HTTP I/O requests exceed the memory limit, caching switches to a temporary file. The following lines from boot.properties display the default values related to buffer size:

# initial size of the in-memory I/O buffer for HTTP requests
#openidm.temporarystorage.initialLength.bytes=8192

# maximum size of the in-memory I/O buffer for HTTP requests
#openidm.temporarystorage.memoryLimit.bytes=65536

# maximum size of the filesystem I/O buffer for HTTP requests, for when memoryLimit is exceeded
#openidm.temporarystorage.fileLimit.bytes=1073741824

# absolute directory path of filesystem I/O buffer for HTTP requests, and uses system property java.io.tmpdir by default
#openidm.temporarystorage.directory=/var/tmp

openidm.temporarystorage.initialLength.bytes: Initial size of the memory buffer in bytes.

Default: 8192 bytes (8 KB). Maximum: The value of openidm.temporarystorage.memoryLimit.bytes.
openidm.temporarystorage.memoryLimit.bytes: Maximum size of the in-memory I/O buffer for HTTP requests. When the memory buffer is full, the content is transferred to a temporary file.

Default: 65536 bytes (64 KB). Maximum: 2147483647 bytes (2 GB).
openidm.temporarystorage.fileLimit.bytes: Maximum size of the temporary storage file. If the downloaded file is larger than this value, IDM throws the exception HTTP 413 Payload Too Large.

Default: 1073741824 bytes (1 GB). Maximum: 2147483647 bytes (2 GB).
openidm.temporarystorage.directory: The absolute directory path of the filesystem I/O buffer for HTTP requests.

Default: The value of the system property java.io.tmpdir.

PingIDM 7.5.0

HTTP I/O buffer