Optimise your installation
These settings improve the reliability and performance of a running Zendrite installation.
PostgreSQL connection limit
Section titled “PostgreSQL connection limit”PostgreSQL accepts only a limited number of connections.
The max_connections and superuser_reserved_connections settings in postgresql.conf usually set this limit.
Once the limit is reached, PostgreSQL immediately stops accepting new connections until existing ones close.
This is a common misconfiguration.
For example, with max_connections set to 100 and superuser_reserved_connections set to 3, the effective limit is 97 connections.
Keep Zendrite below that limit.
Otherwise database queries fail unexpectedly, which causes problems both in Zendrite and for users.
If other software uses the same PostgreSQL server, its connections reduce the number left for Zendrite. Check the connection limits that other software configures and subtract them.
Set how many connections Zendrite opens with max_open_conns in each database block.
If you use the global database pool, set max_open_conns once in the global section.
If you raise max_connections on your PostgreSQL server, raise max_open_conns in your Zendrite configuration to match.
Do this only on servers with enough capacity to run the extra queries at the same time.
PostgreSQL optimisation
Section titled “PostgreSQL optimisation”PostgreSQL uses few system resources by default and performs better when it may use more. The PGTune tool generates example configurations. Before you change settings, consider your setup, such as other software on the same machine or PostgreSQL server.
File descriptor limit
Section titled “File descriptor limit”Most platforms limit how many file descriptors one process can open. Every connection Zendrite makes uses a file descriptor, including database connections and requests to remote homeservers. In large federated rooms, Zendrite talks to many remote servers and can exhaust the low default limits.
Set the file descriptor limit to 65535. Zendrite logs a warning at startup if the limit is too low:
UNIX systems have a hard limit and a soft limit.
Show the soft limit with ulimit -Sn and the hard limit with ulimit -Hn:
Raise the soft limit before you start Zendrite:
Once the limit is high enough, the startup warning no longer appears.
Under a systemd service, add LimitNOFILE=65535 to the [Service] section of the unit file instead.
DNS caching
Section titled “DNS caching”Zendrite has a built-in DNS cache that reduces the load on your DNS resolver. It may also speed up outbound federation.
Enable it in the global section of your configuration file:
Time synchronisation
Section titled “Time synchronisation”Matrix relies on TLS, which needs a correct system clock. If the clock drifts, federation may fail partly or completely, and clients may fail to connect to your Zendrite server.
Enable NTP sync to keep the system time correct.