search

heroku / roadmap

This is the public roadmap for Salesforce Heroku services.
195 stars 11 forks source link

Expanded Memory when building on heroku-24 stack #307

Closed refi93 closed 1 month ago

refi93 commented 4 months ago

Required Terms

What service(s) is this request for?

Heroku dynos

Tell us about what you're trying to solve. What challenges are you facing?

When we tried to upgrade from heroku-22 to heroku-24 stack we ran into "Out of memory" errors when building our app with webpack (TypeScript project) which is apparently caused by swap space no longer being available on heroku-24 stack, as mentioned here.

Looks like only 2.5GB memory is available during build time (Performance-M dyno used for build, regardless of plan) which IMHO seems like too little for many, if not most modern web apps.

Overall, this seems like a blocker for us for upgrading to heroku-24 stack as it seems quite tricky to keep our app build within such narrow memory limit.

We considered building our app on some self-hosted server and uploading the built artifact to heroku, but it would be tricky to manage the env vars which webpack currently takes from env and "bakes" into the build, so we would probably need to redesign our build process, which is surely doable but the effort we'd spend on that seems pretty high, to the point that it may be less effort to just switch over to another serverless platform, or even self-hosted solution.

Could you consider increasing the available RAM during app build, at least for paid plans? Could perhaps re-enabling swap space with some extra flag be an option?

seems like we are not the only one facing this issue: https://github.com/heroku/roadmap/issues/255#issuecomment-2234483779

ASayre commented 3 months ago

Hi @refi93! Thank you for sharing your feedback here. We're currently doing some internal testing to increase this on the heroku-24 stack, and we'll be sharing more very soon after we've completed our validations.

jeffbax commented 1 month ago

Hi @refi93! Thank you for sharing your feedback here. We're currently doing some internal testing to increase this on the heroku-24 stack, and we'll be sharing more very soon after we've completed our validations.

Just wondering if there's been any progress on this, I haven't been able to find anything in the changelog indicating there would now be swap or notably more memory to support large node builds.

ASayre commented 1 month ago

@jeffbax , @refi93 : Alongside the recent change to set Heroku-24 as the default stack, we've also recently addressed the memory available to each of our builds. You can find more information here.

Enjoy!

jeffbax commented 1 month ago

@jeffbax , @refi93 : Alongside the recent change to set Heroku-24 as the default stack, we've also recently addressed the memory available to each of our builds. You can find more information here.

Enjoy!

alrighty, sounds like still no swap just a ton more ram? I will give things another go and see where things land

thanks!

jeffbax commented 1 month ago

@ASayre so far things are looking better, even with NODE_OPTIONS=--max_old_space_size=2560 unset in the environment (which we had needed in the past) so hoping this clears things up for us! 🚀

edmorley commented 2 weeks ago

We've also now documented the available RAM for builds on the main Heroku Dev Center Limits page: https://devcenter.heroku.com/articles/limits#build-resources