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

Increase database server instance sizes #308

Closed
GUI opened this issue Jan 8, 2016 · 1 comment
Closed

Increase database server instance sizes #308

GUI opened this issue Jan 8, 2016 · 1 comment
Assignees
Labels

Comments

@GUI
Copy link
Member

GUI commented Jan 8, 2016

As we discussed today, we'll be increasing the database instance sizes as a temporary measure to help with analytics performance while we work on a better long-term solution (#235).

Currently we're on m4.xlarges, so moving to m4.2xlarges should give us a pretty good boost. We'll also need to adjust the ElasticSearch config to allocate more memory towards it.

This swap shouldn't result in any downtime for API traffic, but it will result in a couple of brief outages of the analytics queries in the admin interface. I'll plan to do this upgrade later this evening or over the weekend to minimize impact for any admin users.

@GUI GUI added the server label Jan 8, 2016
@GUI GUI self-assigned this Jan 8, 2016
@GUI
Copy link
Member Author

GUI commented Jan 9, 2016

The servers have been upgraded.

I'm running some optimize commands on some of the static data from last year, so that's chugging along in the background. The optimizations seem to be taking longer than I expected, so those might still be running for a couple days. But even with those running in the background, the performance of the analytics in the admin is better, so I think we should be good for a while.

@GUI GUI closed this as completed Jan 9, 2016
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