Memcached container customization
Local installations of Flow Production Tracking are no longer offered. This documentation is intended only for those with existing instances of Shotgun Enterprise Docker. Click here for a list of our current offerings.
Purpose
This article is intended for Flow Production Tracking System Administrators. It gives information about additional parameters that can be configured in for the memcached container.
Overview
Memcached is, according to https://memcached.org , “an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.”
Memcached is one of the important components of Flow Production Tracking stack, and can cause Flow Production Tracking performance issues if configured incorrectly.
We ship default Memcached configuration with Flow Production Tracking Enterprise Docker, which suits most of our clients.
However, in some cases default Memcached parameters are not enough and need to be adjusted based on needs.
Memcached mainly relies on RAM and uses the default value of 64MB. This value can be easily re-configured by modifying the docker-compose.yml file.
Memcached container configuration
Here is an example of your Memcached service in your Compose file:
memcached:
image: memcached:1.4
command: ["-m", "4096"]
ports:
- "11211:11211"
restart: always The amount of memory allocated to Memcached for object storage is `4096` (4GB).
The more RAM you allocate, the more data you can store, and therefore the more effective your cache is.
Do not specify a memory allocation larger than your available RAM. If you specify too large a value, then some RAM allocated for Memcached uses swap space, and not physical RAM. This may lead to delays when storing and retrieving values, because data is swapped to disk, instead of storing the data directly in RAM.