It appears I was using `@initDuration+@billedDuration` and not `@initDuration + @duration` artificially inflating the baseline to 144ms from ~78ms. The delta between making a service call to STS from init vs. the handler is close to nothing when using llrt.

@jason.energy was a multimodal mc at #cascadiajs He ranged from concert in the park pose to Carole Baskin leopard print. Good times!

The next version of LLRT supports calling AWS services in init so you can utilize the extra CPU power. In testing, the initDuration+duration went from p50 of 144 ms to 76 ms! However, the E2E duration (from the client) stayed the same p50 of 268 ms vs p50 of 266 ms. This makes no sense to me.

My garbage disposal kept failing due to low voltage at the switch (36 volts instead of 120). Today after it failed for the third time and my normal voodoo didn't work, I bought a new switch. The culprit was smoked sugar ants in the contact.

Got my api running on llrt! They patched the iam client issue. Init Duration vs Node 22 went from 375 ms to 114 ms (3.3x improvement) and normal invokes went from 181 ms to 81 ms (2.2x improvement). All with much less memory; in Node I allocated 832 MB vs 256 MB for llrt.

PSA, the npm packages `debug` and `chalk` got compromised. www.aikido.dev/blog/npm-deb... This hacker news comment has a ripgrep command to make sure you don't have it: news.ycombinator.com/item?id=4517...

Added a new CloudWatch Insights query to get coldstart time by lambda runtime and memory to this gist: gist.github.com/perpil/abfba...

Stymied again. I got pieces working, but client-iam doesn't work with llrt. I tried swapping the iam client with aws-lite, but llrt doesn't support its dependency on node:querystring.

It's happening! I think I've figured out how to fully get my API working on github.com/awslabs/llrt by migrating to hono. POC seems to work.

This speaker headshot from GitHub Universe is built different.

This limbo attempt of mine circa 2021 has it all. I think the man bun threw off my center of balance.

Caught up with @alexdebrie.bsky.social who is out here for the AWS heroes summit and hand delivered a crab sando.

Scored 5lb 8oz of stalkeyed sidewalkers yesterday with Captain @pete-naylor.bsky.social

Still not getting billed for my init duration, I thought it was supposed to start on August 1st?

All smiles in the intense Seattle sun with Allen @readysetcloud.io and Jeevan @antstack.com at #buffconf

The LED drivers keep crapping the bed in my lights. I just buy a donor and Frankenstein the new driver into my existing light.

My son said "Hey Google" instead of "Hey Dad" to me today. Awkward 😳.

Back by popular demand, Seattle is offering free blackberries to everyone all August long.

While coldstarts are still free, I reran my benchmarks with aws-lite.org It's 15% faster than all my optimizations so I updated my recent article to include it: speedrun.nobackspacecrew.com/blog/2025/07... h/t @brianleroux.bsky.social

My Lambda coldstarts are faster than yours. A new article detailing all the tricks I use to save about 100ms when using Node 22. Just in time for AWS billing for Init Duration starting August 1. speedrun.nobackspacecrew.com/blog/2025/07...

Just upgraded my cloudfront fronted website and api to support QUIC in 1 request following these instructions. aws.amazon.com/blogs/networ...

The problem with letting nerds redefine the word vibe is that they think typing a user story into a chat box has an incredible vibe. It does not.

Impressive curling wood in this fire and great crab haul on Camano Island.

This looks interesting, is it possible people will stop asking about unexpected bills on Reddit with this new AWS Free Tier? docs.aws.amazon.com/awsaccountbi...

If you're in Seattle, I'll be presenting at SeattleJS Wednesday July 9th at 5:30 pm. It's an existential talk about speedrunning oncall. lu.ma/SeattleJS-20...

Using every trick I have, I'm able to get Node 22 Lambda Init Duration down to ~190 ms with 1 V3 JS SDK client, and ~275 ms using that client to make 1 service call during Init. Sub 300 ms baby. Documenting it now.

Today I saved 18K on my bundle size. github.com/aws/aws-sdk-...

My tour dates for 2025. Momento BuffConf, July 30-31, Seattle buffconf.gomomento.com CascadiaJS, Sept 17-20, Seattle cascadiajs.com/2025 Re:invent 2025, Dec 1-5, Las Vegas reinvent.awsevents.com If you're at these events and hear a doppler shifted voice or see a motion blur I'm nearby.

I'm convinced that my older brother is scrambling to write as much dirty python code as he can while visiting Iowa because it wouldn't pass California emissions.

Had to adjust the pizza aperture to get it to all fit in the pan. Bonus tip: if y'all aren't reheating your pizza in a pan with a little olive oil for a crispy delicious crust, you haven't lived.

I've rediscovered my Darkwing Duck fanny pack from the early '90s. I realize it's impossible, but try not to get too jealous.

Speaking for the trees in my finest Rastafarian camo. Happy Father's Day!

My tell that you aren't a cyclist is when you see me leave with my helmet you tell me to "be safe out there".

Adding a pop of color to AWS console favicons to quickly tell what account and role you are in requires a devilish combination of Canvas, CORS and MutationObservers. 😈

Did an experiment to see if Lambda creates the log group/log stream before it starts your function, or does it async. I've concluded it is async and doesn't impact your cold start or duration times.

Windowsill batching has reduced my trips to the dishwasher by 10x.

Sometimes I need my glasses to find my glasses in the morning.

Today in small environmental wins: the person who delivers the paper in our neighborhood kept tossing the bag handles into our street. This has been ongoing for years. Earlier this week, I met them in the street at 4am and told them what I'd do if I found 1 more. It hasn't happened since.

TIL about service quota request templates for organizations. On new account creation you can increase service quotas via a template: docs.aws.amazon.com/servicequota...

The latest cover for Cold Start Aficionado magazine. w/ @ajs.bsky.social

I'm old enough to know that the McIntosh was not a very tasty apple.

Wearing my red 'stocks at the Red Sox game. Beautiful day at the green monster.

Finally figured out the magic query in CWL insights to get coldstart stats by lambda runtime. The trick is to group by @logStream since INIT_START doesn't have a requestId. There are 2 versions in this gist, v1. with lambda runtime only, v2. with software version gist.github.com/perpil/abfba...

It's curious that some of the Lambda env variables like AWS_LAMBDA_LOG_GROUP_NAME and AWS_LAMBDA_LOG_STREAM_NAME are missing when building a Lambda extension. INIT_START logs appear before the extension logs in the logstream, so probably available unless they are creating the logstream async.

TIL the word carcinisation. Which means to become more crab. Relevant because I'm attempting to write some rust and it's not going well. en.wikipedia.org/wiki/Carcini...

Playing around with embedding a terminal directly into GitHub so when you click speedrun buttons, the result is executed inline. No more faffing with copying and pasting.

Here's me going hard on the green to look Irish while playing Celtic music for a fundraiser. We went by the name: The Noisemakers Downstairs.

I've done some more digging into the 50 ms performance regression in Lambda coldstarts between node 20 and 22. It's still related to using the AWS Javascript SDK v3, but the fix might be more impactful if done at the node.js level so I cut an issue. github.com/nodejs/node/...

If the AWS Console was sane, when you signin with SSO and your session times out, it would either redirect you to your SSO start url or provide a SSO shortcut link to signin again. Instead, it asks you to signin with an IAM user/root user and can't remember the AWS account were in 🫠.

My beard is gaining strength. It was a flat La Croix Tangerine, now it is a 2-liter of Orange Crush.