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

scale to RAM #315

Closed
maxheld83 opened this issue Sep 27, 2021 · 2 comments
Closed

scale to RAM #315

maxheld83 opened this issue Sep 27, 2021 · 2 comments
Assignees
Milestone

Comments

@maxheld83
Copy link
Contributor

No description provided.

@maxheld83
Copy link
Contributor Author

to avoid this again in the future, we must load test the live app

@maxheld83 maxheld83 moved this to Blocked in max's scrum(ish) Nov 3, 2021
@maxheld83 maxheld83 moved this from Blocked to Todo in max's scrum(ish) Nov 3, 2021
@maxheld83 maxheld83 self-assigned this Nov 4, 2021
@maxheld83 maxheld83 moved this from Todo to In Progress in max's scrum(ish) Nov 11, 2021
@maxheld83
Copy link
Contributor Author

there's not much to do here.

We ran out of RAM not b/c there any one slot took too much RAM or too many visitors did (that just triggered it, b/c we were so damn close), but because there were too many slots live at once (for testing).

As a result, we can't meaningfully "scale to RAM", b/c:

  1. that may start too many instances, and not for the reason we want to
  2. we'd need to make sure that the slots are sparsely distributed, otherwise we'll never have enough RAM.

The long-term solution for this lives in:

In the meantime, I've reduced RAM again to 3.5gigs and will keep an eye on slots (i.e. delete them when no longer used), that should do the trick.

Repository owner moved this from In Progress to Done in max's scrum(ish) Nov 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant