diff options
| author | reivilibre <reivilibre@users.noreply.github.com> | 2022-04-14 14:25:57 +0000 |
|---|---|---|
| committer | reivilibre <reivilibre@users.noreply.github.com> | 2022-04-14 14:25:57 +0000 |
| commit | 18bef721f612515855b5ebfcbccf3e6c4b09695f (patch) | |
| tree | d1b739a6dd760a9c16db2b832a8219df6e5bcb1f /develop/workers.html | |
| parent | deploy: a743f7d33ebbd383fbe9bf70e024db79525d891c (diff) | |
| download | synapse-18bef721f612515855b5ebfcbccf3e6c4b09695f.tar.xz | |
deploy: 7efddbebefbadce3e5f0938ea123e7e37ad2503c
Diffstat (limited to 'develop/workers.html')
| -rw-r--r-- | develop/workers.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/develop/workers.html b/develop/workers.html index eb90c68507..788fa244d7 100644 --- a/develop/workers.html +++ b/develop/workers.html @@ -428,9 +428,9 @@ the full URI, or even just round robin), the room ID is the path component after of events, then a dedicated set of workers can be provisioned to limit the effects of bursts of events from that bridge on events sent by normal users.</p> <h4 id="stream-writers"><a class="header" href="#stream-writers">Stream writers</a></h4> -<p>Additionally, there is <em>experimental</em> support for moving writing of specific -streams (such as events) off of the main process to a particular worker. (This -is only supported with Redis-based replication.)</p> +<p>Additionally, the writing of specific streams (such as events) can be moved off +of the main process to a particular worker. +(This is only supported with Redis-based replication.)</p> <p>To enable this, the worker must have a HTTP replication listener configured, have a <code>worker_name</code> and be listed in the <code>instance_map</code> config. The same worker can handle multiple streams, but unless otherwise documented, each stream can only @@ -486,7 +486,7 @@ the stream writer for the <code>presence</code> stream:</p> <pre><code>^/_matrix/client/(api/v1|r0|v3|unstable)/presence/ </code></pre> <h4 id="background-tasks"><a class="header" href="#background-tasks">Background tasks</a></h4> -<p>There is also <em>experimental</em> support for moving background tasks to a separate +<p>There is also support for moving background tasks to a separate worker. Background tasks are run periodically or started via replication. Exactly which tasks are configured to run depends on your Synapse configuration (e.g. if stats is enabled).</p> |