Does the memory allocation for a lambda have any effect when running locally?

Guess: No. It might affect the lambda up in AWS, but its just a connection back down to your machine, which will do the grunt work.

That was my guess too, just wondered if the local runtime did anything with it to more closely approximate the deployed version

Yeah, we used to set

--max-old-space-size

when spawning a node process locally to match the Lambda function’s memory size.

@Derek Kershner just curious if the thumbs down was that you preferred we didn’t emulate the behavior locally?

That exactly, although most of my reasoning is that the complexity is likely to cause bugs that are hard to reason and take up more of your guy’s time, in the name of something that is likely a poor approximation anyway. (cc: @Jay) It doesn’t actually affect our workflow.

Yeah it won’t be perfect. @Ross Coundon curious why you were looking into this.

It was just curiosity really. I was running into some memory issues and it got me thinking. I think Derek’s probably right, it’s unnecessary complication