Skip to content

The uncompressed size of the node 22 layer v42 is much larger than v39 #404

@Phydaux

Description

@Phydaux

Description

We noticed deploy errors on our lambdas yesterday because we had gone over the AWS lambda size limit. However we hadn't increased the size of our deployed code. The only lambda layer we use is NewRelic.

I pulled the newrelic lambda layer zip files for v39 (our last successful deploy) and v42.

On my machine the uncompressed sizes were:

  • for arn:aws:lambda:eu-west-1:451483290750:layer:NewRelicNodeJS22X:39, 111MB
  • for arn:aws:lambda:eu-west-1:451483290750:layer:NewRelicNodeJS22X:42, 174MB

Steps to Reproduce

I pulled a copy of both newrelic-nodejs22x-v39.zip and newrelic-nodejs22x-v42.zip from AWS.

Unzip:
$ unzip newrelic-nodejs22x-v39 -d /tmp/v39
$ unzip newrelic-nodejs22x-v42 -d /tmp/v42

Check size:

$ du -sh /tmp/v39/ 
111M	/tmp/v39/
$ du -sh /tmp/v42/ 
174M	/tmp/v42/

Expected Behaviour

This is a much larger jump in size than I would expect from what is, I believe, only a minor package update.

Your Environment

Deploying Node v22 AWS lambdas

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions