c0308307e2
This is an attempt at optimizing service startup. The effect is most pronounced when many services are restarted one by one. The systemd service manager role sometimes does this - for example when `just install-service synapse` runs. In such cases, a 5-second delay for each Synapse worker service (or other bridge/bot service that waits on the homeserver) quickly adds up to a lot. When services are all stopped fully and then started, the effect is not so pronounced, because `matrix-synapse.service` starts first and pulls all worker services (defined as `Wants=` for it). Later on, when the systemd service manager role "starts" these worker services, they're started already. Even if they had a 5-second wait each, it would have happened in parallel. |
||
|---|---|---|
| .. | ||
| bin | ||
| customizations | ||
| ext/s3-storage-provider | ||
| prometheus | ||
| systemd | ||
| homeserver.yaml.j2 | ||
| labels.j2 | ||
| synapse.log.config.j2 | ||
| worker-labels.j2 | ||
| worker.yaml.j2 | ||