Skip to content
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.

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

Performance Optimizations #43

Open
coopermaruyama opened this issue Aug 4, 2017 · 0 comments
Open

Performance Optimizations #43

coopermaruyama opened this issue Aug 4, 2017 · 0 comments
Assignees
Labels

Comments

@coopermaruyama
Copy link
Member

coopermaruyama commented Aug 4, 2017

When the cache TTL expires, the cache will not be refreshed until the next user visits the site, because refreshing the cache is triggered by a request. This means that this user will have a very slow initial loading time.

The architecture needs to be updated such that:

  1. A worker is responsible for updating the cache
  2. Rather than using a memory cache, we setup an external redis server for caching. This has the added benefit that rather than each node in the cluster keeping its own cache, all nodes share one cache (the redis cache).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant