Image missing.
Eliminating JavaScript cold starts on AWS Lambda

created: Aug. 16, 2025, 11:44 a.m. | updated: Aug. 17, 2025, 11:04 p.m.

) ─────┴────────────────────────────────────── ~$ porf native hi.js hi [ 271ms ] compiled hi.js -> hi ( 12.9KB ) ~$ du -h hi 16K hi ~$ ./hi hello blog! LambdaA few days ago I got Porffor running on Lambda, not simulated locally but really on AWS! I wrote a cold start benchmark for Node, LLRT (Amazon’s own experimental JS runtime optimizing cold starts) and Porffor running identical code:export const handler = async () => { return { statusCode : 200 , headers : { "Content-Type" : "text/plain" }, body : "Hello from " + navigator . PorfforPorffor is ~12x faster than Node and almost 4x faster than LLRT in this case. ConclusionYou might be expecting me to start shilling for you to plug Porffor into your Lambda instantly… but unfortunately not.

1 day, 11 hours ago: Hacker News