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.

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

Max memory exeded on Heroku web dynos 1X (512 MB) #659

Closed
frjo opened this issue Oct 17, 2018 · 2 comments
Closed

Max memory exeded on Heroku web dynos 1X (512 MB) #659

frjo opened this issue Oct 17, 2018 · 2 comments
Assignees
@frjo
Milestone
2019-Q1

Comments

@frjo
Copy link
Contributor

frjo commented Oct 17, 2018 •
edited
Loading

@danblah I just now upgrades the dynos to 2x so we get 1 GB memory.

We should investigate what eats up the RAM.

It was hovering around 350 MB until yesterday when it hit the roof. I restarted the dynos but is quite quickly climed up to 400+ so then I upgraded. The extra cost is 100 USD per month.

 Oct 16 08:37:11 live-opentech-fund heroku/web.1: Error R14 (Memory quota exceeded)
@frjo frjo added this to the Current release milestone Oct 17, 2018
@todd-dembrey
Copy link
Contributor

Interesting. It seems to be back to normal levels (~350 - which is normal for most wagtail/django apps.) since you added the extra dyno.

For the record the memory went up from 16th Oct 2018 15:10-15:40

@frjo frjo assigned frjo and unassigned todd-dembrey Oct 22, 2018
@frjo
Copy link
Contributor Author

frjo commented Oct 22, 2018

I have now downgraded back to 1x WEB_CONCURRENCY and set WEB_CONCURRENCY down from 3 to 2.

It seems each process takes around 130 MB so currently 260 MB is used.

@frjo frjo closed this as completed Oct 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@frjo frjo

Labels
None yet
Projects
None yet
Milestone
2019-Q1
Development

No branches or pull requests
2 participants
@frjo @todd-dembrey