5 comments

  • netik 25 minutes ago
    This a bit of a “yeah, so?” Statement.

    You can configure teardown and minimum workers, and with a busy site, most of the time requests aren’t going to stop enough for this to matter.

    • seanw265 19 minutes ago
      Yes for sure, if your web function is very active this is less of an issue. But not every workload fits that mold.

      Also: afaict idle time before teardown is not configurable.

  • catlifeonmars 31 minutes ago
    Does the ~7 minutes get amortized over sustained load (due to container reuse)? I feel like the article doesn’t consider the shape of the traffic and workloads in its analysis of why lambda is not a good fit.
    • seanw265 4 minutes ago
      In general I think the answer to your question is yes. If you have sustained load, the environment will often be reused. When that happens, there is little “idle” time that you’re billed for.

      I don’t mean to imply that Lambda Web Functions are a bad fit for every workload, just that they are a bad fit for our workload as a result of this behavior.

  • hoppp 40 minutes ago
    Isn't that a configurable parameter?
    • seanw265 29 minutes ago
      Not as far as I can tell. Web Functions let you configure concurrency, maximum environment count, and request rate limits, but there's no setting for how long an environment stays alive after its last request. The configurable timeout applies to individual requests, not the environment itself.

      I measured between 5 and 7 minutes of idle time (after the last request had ended) across six environments. I was able to cut this short by exiting the process myself, but AWS records this as a runtime error so IMO it's not suitable to rely on in production.

      Here's the AWS scaling documentation. I'm happy to be corrected if I missed anything.

      https://docs.aws.amazon.com/lambda/latest/dg/web-functions-s...

    • ceejayoz 39 minutes ago
      Yes. Buried several paragraphs past the headline is a note saying "AWS documents this behavior."

      This is marketing for a Lambda competitor.

      • Hnrobert42 30 minutes ago
        Hmm. Are you sure? The article says AWS documents the behavior, but there is no way to configure it. They tried forcing an early shutdown, but that caused AWS to record an error event.
      • stymaar 30 minutes ago
        What's the default though? Because if the 7min thing happen with default settings, then it's definitely blog post worthy.
      • seanw265 22 minutes ago
        [dead]