Page History

...

The Runtime maintains a pool of connections to Redis. Response times decrease when requests have to wait for connections in the pool to become available.

...

The connection pool size should be increased depending on the expected load per Runtime instance. 

From our observations, the connection pool does not handle sudden increases in load very well. Therefore, we recommend to use a constant pool size by setting the max-active, max-idle and min-idle properties to the same value.

Disable TCP Keepalive in Redis

In order to prevent Redis from closing connections during periods of inactivity, set the tcp-keepalive property to zero in the Redis configuration file.

Consider disabling saving Redis data to disk

By default, Redis saves its data to disk after a certain amount of time and a certain amount of writes have occurred. Under high load (and lots of sessions stored) this may have a negative impact on performance. Consider the risk of losing session data if using a single Redis instance versus the performance impact. If the decision is to keep saving data to disk enabled, then consider disabling the stop-writes-on-bgsave-error setting. Leaving this setting enabled may cause Redis to refuse all writes if saving data to disk fails. This may leave the entire Runtime cluster unuseable until Redis recovers. For more details, consult Redis Persistence .