Reduce support cases: Memory issues #158
Description
There can be a lot of causes and solutions here. The most common solutions I saw were:
- Switch from a 32 bit app in Azure to 64 bit
- Use the max-old-space-size node process argument
- NOTE on this one: The default heap size in node.js is variable and complicated to determine (some discussion here). It's not always clear if hard-coding this value would help - plus it means we have to restart the node.js process which can lead to slightly worse cold start
- Scale up the app
- Some docs on premium plan here
There were also several that mentioned large file/request sizes that could be helped by our stream support for http or azure resources
Support cases from June 2023 - Sept 2023
Internal-only links:
- https://elixir.microsoft.com/case-review/2307040060001616
- https://elixir.microsoft.com/case-review/2309080040002869
- https://elixir.microsoft.com/case-review/2307240030005058
- https://elixir.microsoft.com/case-review/2308030060000832
- https://elixir.microsoft.com/case-review/2308080040009195
- https://elixir.microsoft.com/case-review/2309060060001518
64 bit:
- https://elixir.microsoft.com/case-review/2309190060002846
- https://elixir.microsoft.com/case-review/2307120060002105
max-old-space-size: