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

Migrate off of New Relic and Memcachier #330

Open
panchr opened this issue Nov 27, 2017 · 1 comment
Open

Migrate off of New Relic and Memcachier #330

panchr opened this issue Nov 27, 2017 · 1 comment
Assignees
Milestone

Comments

@panchr
Copy link
Collaborator

panchr commented Nov 27, 2017

For New Relic, we want to find a way to store/index all logs onto something on AWS. For Memcachier, we should find a suitable caching replacement on AWS.

@panchr panchr added this to the v3 milestone Nov 27, 2017
@panchr panchr self-assigned this Nov 27, 2017
@maximz
Copy link
Member

maximz commented Nov 27, 2017

Thanks for digging into this, Rushy.

For what it's worth, I don't think we're actually using Memcache. Take a look at https://github.com/recalapp/recal/blob/master/settings/prod.py#L40 : this defines four separate caches. I did a brief search through the code and couldn't find any places where the memcache cache is used. The other caches are used quite a bit, and they are all backed by django.core.cache.backends.db.DatabaseCache

Memcache may eventually be useful, but I'm not sure we're at the point where django.core.cache.backends.db.DatabaseCache can't handle our use case.

I also think we stopped using New Relic a while back -- @dxue2012 would know better!

panchr added a commit that referenced this issue Nov 28, 2017
Neither of these were being used. Closes #330.
panchr added a commit that referenced this issue Nov 30, 2017
Neither of these were being used. Closes #330.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants