Rerun the benchmark?

Is it possible to rerun the benchmark with the latest release? Since January 2024, the llrt binaries have grown 2+ MB. I've been doing some coldstart benchmarking to compare LLRT standard sdk with Node 22. My test using arm in us-east-2 instantiates a STS client and invokes get-caller-identity. It isn't quite the same as a ddb put, but it's similar enough that I'd expect the http and λ times to be close to yours on coldstarts. In the table below http means time recorded from the client and λ is time from the invocation logs like yours. Overhead means http - λ. I'm noticing that the overhead in the cold start is higher for LLRT than when using the Node 22 runtime by about 50 ms. I also notice that my p50 for http is ~40 ms higher than your benchmark, but λ is ~17 ms higher. I suspect the increase in binary size is the main contributor, but if you can rerun the benchmarks that will help narrow down what is causing the deltas.

Start with example/functions/src/v3-lib.mjs and the benchmark setup described in the issue. Rerun the LLRT and Node 22 cold-start comparison using the stated ARM, us-east-2, STS get-caller-identity scenario, then compare the HTTP, invocation, and overhead measurements with the reported table. Done means updated results that help assess whether binary growth explains the deltas.