You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often times, running beekeepers build after starting the VM results in out of memory errors. This is observed both on local developer machines and on CI for PR builds. The disparity between webpack's build and dev-server behavior has been talked about elsewhere, e.g. webpack/webpack#6389 and https://blog.box.com/blog/how-we-improved-webpack-build-performance-95.
Figure out what is causing the excessive RAM usage, and address the issue.
Often times, running
beekeepers build
after starting the VM results in out of memory errors. This is observed both on local developer machines and on CI for PR builds. The disparity between webpack'sbuild
anddev-server
behavior has been talked about elsewhere, e.g. webpack/webpack#6389 and https://blog.box.com/blog/how-we-improved-webpack-build-performance-95.Figure out what is causing the excessive RAM usage, and address the issue.
Another fix may be to increase the RAM for the
app
VM.Another fix may be to add a swapfile with https://github.com/azavea/ansible-swapfile.
The text was updated successfully, but these errors were encountered: