How To
Summary
In Docker the GatewayScript Cache is automatically disabled by default. The reason for this is due to the limitation of the docker "aufs" driver which effects the refreshment of the cache.
When the GatewayScript Cache is disabled it causes every transaction that contains/calls upon a GatewayScript to have to recompile that GatewayScript. This naturally impacts transaction time (latency) and will show up as a very large compilation time in some circumstances. For some customers this has even lead to things such as high CPU usage, hang events, and similar behavior.
Currently due to the issue residing in the docker platform itself - this is considered working as designed. We are investigating potential ways in the future of working around Docker's limitations but for now we suggest customers manually enable the GatewayScript Cache to prevent high compilation times and unexpected events.
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
08 June 2021
UID
ibm16091012