Announce matrix-synapse-auto-compressor
This commit is contained in:
parent
bb89d7b3fb
commit
d3a0ef22b6
16
CHANGELOG.md
16
CHANGELOG.md
|
@ -1,3 +1,19 @@
|
||||||
|
# 2023-03-12
|
||||||
|
|
||||||
|
## synapse-auto-compressor support
|
||||||
|
|
||||||
|
Thanks to [Aine](https://gitlab.com/etke.cc) of [etke.cc](https://etke.cc/), the playbook can now set up [rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state)'s `synapse_auto_compressor` tool to run periodically.
|
||||||
|
|
||||||
|
If enabled, `synapse_auto_compressor` runs on a schedule and compresses your Synapse database's `state_groups` table. It was possible to run `rust-synapse-compress-state` manually via the playbook even before - see [Compressing state with rust-synapse-compress-state](docs/maintenance-synapse.md#compressing-state-with-rust-synapse-compress-state). However, using `synapse_auto_compressor` is better, because:
|
||||||
|
|
||||||
|
- it runs on a more up-to-date version of `rust-synapse-compress-state`
|
||||||
|
- it's a set-it-and-forget-it tool that you can enable and never have to deal with manual compression anymore
|
||||||
|
|
||||||
|
This tool needs to be enabled manually, for now. In the future, we're considering enabling it by default for all Synapse installations.
|
||||||
|
|
||||||
|
See our [Setting up synapse-auto-compressor](docs/configuring-playbook-synapse-auto-compressor.md) documentation to get started.
|
||||||
|
|
||||||
|
|
||||||
# 2023-03-07
|
# 2023-03-07
|
||||||
|
|
||||||
## Sliding Sync Proxy (Element X) support
|
## Sliding Sync Proxy (Element X) support
|
||||||
|
|
|
@ -195,6 +195,8 @@ When you're done with all the configuration you'd like to do, continue with [Ins
|
||||||
|
|
||||||
### Other specialized services
|
### Other specialized services
|
||||||
|
|
||||||
|
- [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers (optional)
|
||||||
|
|
||||||
- [Setting up the Sliding Sync Proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like Element X) (optional)
|
- [Setting up the Sliding Sync Proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like Element X) (optional)
|
||||||
|
|
||||||
- [Setting up the Sygnal push gateway](configuring-playbook-sygnal.md) (optional)
|
- [Setting up the Sygnal push gateway](configuring-playbook-sygnal.md) (optional)
|
||||||
|
|
|
@ -29,7 +29,9 @@ After deleting data, you may wish to run a [`FULL` Postgres `VACUUM`](./maintena
|
||||||
|
|
||||||
[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database.
|
[rust-synapse-compress-state](https://github.com/matrix-org/rust-synapse-compress-state) can be used to optimize some `_state` tables used by Synapse. If your server participates in large rooms this is the most effective way to reduce the size of your database.
|
||||||
|
|
||||||
This tool should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first.
|
**Note**: besides running the `rust-synapse-compress-state` tool manually, you can also enable its `synapse-auto-compressor` tool by [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md). The automatic tool will run on a schedule every day and you won't have to compress state manually ever again.
|
||||||
|
|
||||||
|
`rust-synapse-compress-state` should be safe to use (even when Synapse is running), but it's always a good idea to [make Postgres backups](./maintenance-postgres.md#backing-up-postgresql) first.
|
||||||
|
|
||||||
To ask the playbook to run rust-synapse-compress-state, execute:
|
To ask the playbook to run rust-synapse-compress-state, execute:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue