-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Out of memory with lots of files (1000+) under AWS Lambda #363
Comments
Hey @kennu this would be a great question for StackOverflow — you want to move the question over there and tag it with |
I take it this is then a configuration issue, not a development issue? |
Yeah. I'd like to keep issues for bugs/new development and start moving
|
Okay thanks. I added a question here: http://stackoverflow.com/questions/38536371/how-to-scale-gatsby-to-1000s-of-static-files-without-running-out-of-memory |
## Breaking Change Use new schema customization approach for Mdx. `Mdx.code.body` is now `Mdx.body`.
I've started to get SIGKILLs when running Gatsby builds under AWS Lambda, after my project went over 1000 .md files. According to the logs all available memory (1536 MB) is being used, so I'm pretty sure this is caused by running out of memory.
Any ideas how to scale Gatsby without requiring more and more memory when the number of static files grows?
The text was updated successfully, but these errors were encountered: