Suggest better redis configuration for on-premises deployment

[rafaelrenanpacheco]

Hello!

On a fresh Centos7 install, running the on-premises docker-compose shows the following log for the redis container:

oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
Not listening to IPv6: unsupproted
Running mode=standalone, port=6379.
WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
Server initialized
WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Ready to accept connections

The last two warning can be fixed with the following configuration in the SO:

cat <<EOF > /etc/sysctl.d/redis.conf
net.core.somaxconn=511
vm.overcommit_memory=1
EOF

sysctl --system

When running redis after this configuration it shows the following log:

oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
Not listening to IPv6: unsupproted
Running mode=standalone, port=6379.
Server initialized
DB loaded from disk: 0.000 seconds
Ready to accept connections

This way redis starts with the recommended configuration.

[rafaelrenanpacheco]

Sorry, this issue should be created for openvidu.io-docs.

Link: OpenVidu/openvidu.io-docs#28