Add Deno

[tmokmss]

It appears Deno can sometimes be faster than Node.js or Bun. https://deno.com/blog/aws-lambda-coldstart-benchmarks

It'd be great if this benchmark add Deno runtime.

[gitblit]

I agree. I came here looking to see if there was an open request to confirm the claim. Would be great to see this datapoint amongst the other JS runtimes and at varying lambda size - which is something not considered by blog post.

[soundstep]

Having a go at it https://github.com/maxday/lambda-perf/pull/1467

[soundstep]

Hi @maxday (sorry to ping directly), any chance someone can have a look at that one? https://github.com/maxday/lambda-perf/pull/1467 Cheers.

[markhaslam]

If helpful for implementing this I just noticed that Deno archived the deno-lambda repo (https://github.com/denoland/deno-lambda) just today, and then point to their official documentation on how to deploy Deno to AWS Lambda here: https://docs.deno.com/runtime/tutorials/aws_lambda/

[soundstep]

Cheers, I closed that PR and I'll check what that all means.

[vicary]

@soundstep Out of curiosity I tried to build a lambda myself following the official docs and was greeted with the error The image manifest or layer media type for the source image... on all combinations of build arch and runtime arch, would love to see how you do it!

EDIT: It's OT, edited in place to reduce noise.

I am using docker BuildKit (formerly buildx) so I have to include --provenance=false to prevent said error during Lambda deployement.

[soundstep]

Without context, I'm not sure, I don't think I've seen that error; I only built a docker image locally on a MacBook Pro M1, and chose the corresponding arm arch, which worked. I still have an issue that needs sorting but that should be fine.

The easiest is probably to build your image on a github action runner and push it from there?

[soundstep]

FYI, new PR: https://github.com/maxday/lambda-perf/pull/1492

[maxday]

Thanks a lot! Will take a look at it now