New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using an external cache server #2123

Open

matrixbot opened this issue Dec 16, 2023 · 0 comments

Labels

T-Task

Collaborator

matrixbot commented Dec 16, 2023 •

edited

Loading

This issue has been migrated from #2123.

I found that synapse uses a cache, implemented its own means (synapse/util/caches).
This creates some difficulties:

with scaling (workers must communicate with master process in order to have the same data in the cache and with the database)
with clustering for high availability (I've read @ara4n in #matrix:matrix.org that the synapse does not provide the clustering capability).

I believe that using an external cache server like memcached or reddis could solve these problems.

The advantages of an external cache:

it can be accessed by all the processes of application, possibly running on several nodes.
memory storage is quite efficient, and done in a separate process.
it becomes possible to configure workers to use same cache and same database as synapse.
it becomes possible to configure two synapse servers are behind the balancer and work with one cache and a shared database.

matrixbot closed this as completed

matrixbot changed the title ~~Dummy issue~~ Using an external cache server

matrixbot added the T-Task label

matrixbot reopened this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment