Demonstrating Memory Behavior for AWS Lambda Function Freezing

Share onTweet about this on TwitterShare on FacebookShare on RedditEmail this to someone

John Skarbek is’s devops engineer, you can tweet him at @johntskarbek. Originally published on John’s GitHub blog My Brain Dump Site 

AWS indicates that when a function is executed, there are some things that get leftover between runs. The execution environment, which AWS indicates is a container model, contains everything necessary to run the function. After a function is invoked for the first time, it will “freeze” this environment such that it can quickly be called a second time, which will help improve the performance of subsequent runs by avoiding the initialization step of getting your code out into this execution environment. This container reuse, however, can be a benefit or a downside depending on how you write your function. One of these is related to the memory usage of an execution environment.

Say you have the following code:


We initialize 2 empty arrays, arrayA and arrayB, outside of the handler. When the function is run, these two arrays will remain in memory when the function is frozen. Inside of the hander we’ve got 2 more empty arrays, arrayC and arrayD. During the execution of the function we simply push a string item to it and for testing, we clear our arrays arrayA and arrayC. Let’s look at what this does when AWS invokes this function three times:

You’ll notice in the first run, we have pushed one object to all four arrays. In the second run, arrayB has a second object in the array, and in the third run, a third object is added to arrayB. arrayA doesn’t exhibit this behavior because it is reinitialized to an empty array prior to stopping the function. arrayC and arrayD technically get reinitialized at every run.

With this small demo, we can see some value and some potential headache when created incorrectly. This could be a great strategy if we need to do something expensive, such as setup a database connection. Inside of the handler, we can call upon that object to reconnect to the database without needing to go through the heavy lifting every single time.

To avoid leaking memory, we would want to ensure as much data as possible is located within the handler to minimize problems.

Recommended reading: How Does AWS Lambda Run My Code? The Container Model


Share onTweet about this on TwitterShare on FacebookShare on RedditEmail this to someone

Reinventing the way engineering teams track work. Believes developers shouldn't have to do extra work to update others on their status, so does it for them.