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

Investigate memory usage during build #404

Open
davewasmer opened this issue Oct 12, 2017 · 1 comment
Open

Investigate memory usage during build #404

davewasmer opened this issue Oct 12, 2017 · 1 comment
Labels
Milestone

Comments

@davewasmer
Copy link
Collaborator

There are reports (from @seawatts) that Denali apps with multiple on-the-fly compiling addons (not sure if that's relevant) end up using more than Heroku's 700mb memory limit, resulting in the dyno getting killed before launching.

We figure out why the heck Denali is using > 700mb of memory to build.

@seawatts
Copy link
Contributor

This might not be an actual issue. But I haven't confirmed. I believe that it might have been a coincidence that Heroku was spinning up the instance at the same time it was trying to build.

@davewasmer davewasmer added the bug label Oct 13, 2017
@davewasmer davewasmer added this to the v0.1.0-beta.1 milestone Oct 24, 2017
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

2 participants