11–18 of 18 posts
If it's ephemeral to a function, it's not " storage ". It's just core memory that may or may not be backed by physical "storage" media, and is organized as a tmpfs for the user's convenience.
Earlier quoted context omitted.
How’s the overhead? Are you launching full chrome every lambda invocation?
In one lambda I can load chrome, visit a website, take a screenshot and save it to S3 in around 2s with around 280mb memory used. You could keep chrome open and reuse it if available, but you can't count on it with lambda being stateless. I use this Chromium binary https://www.npmjs.com/package/chrome-aws-lambda
/tmp is ephemeral in the sense that it dies with the Lambda instance, but it is also persistent between multiple serial invocations landing on that instance, even if the instance is frozen and thawed between some of those invocations.
The process memory state on the instance (set up during the Init phase) is also available between invocations.
https://docs.aws.amazon.com/lambda/latest/dg/runtimes-contex...
I remember when I was breaking my head against the wall to fit puppeteer inside a lambda. Good times.
Earlier quoted context omitted.
In one lambda I can load chrome, visit a website, take a screenshot and save it to S3 in around 2s with around 280mb memory used. You could keep chrome open and reuse it if available, but you can't count on it with lambda being stateless. I use this Chromium binary https://www.npmjs.com/package/chrome-aws-lambda
> lambda being stateless /tmp is ephemeral in the sense that it dies with the Lambda instance, but it is also persistent between multiple serial invocations landing on that instance, even if the instance is frozen and thawed between some of those invocations. The process memory state on the instance (set up during the Init phase) is also available between invocations. https://docs.aws.amazon.com/lambda/latest/dg/runt…
I remember when I was breaking my head against the wall to fit puppeteer inside a lambda. Good times.
What was the use case?
Earlier quoted context omitted.
What's the use case? I see a sibling commenter mentioned puppeteer which I'm aware is essentially Chrome. Are you too referring to running puppeteer in Lambda? If so, what is the purpose?
Puppeteer-core can already fit in a lambda around 60mb and can be used for web scraping, taking screenshots, or performance testing.
Earlier quoted context omitted.
How’s the overhead? Are you launching full chrome every lambda invocation?
In one lambda I can load chrome, visit a website, take a screenshot and save it to S3 in around 2s with around 280mb memory used. You could keep chrome open and reuse it if available, but you can't count on it with lambda being stateless. I use this Chromium binary https://www.npmjs.com/package/chrome-aws-lambda