fix: handle case where memory.limit_in_bytes is nonsensically large (#531)
* fix: handle case where memory.limit_in_bytes is nonsensically large In certain CI environments, this value can be misreported, resulting in an invalid initial `MEMORY_AVAILABLE` value. In these cases, we default the max detected memory to 16GB, or slightly larger than a `performance-l` instance.
Showing
Please register or sign in to comment