6 replies

1. cthos 🐱 36 min later

   @zachleat uhhhhhh “sure more cpu means more money but faster execution time eh eh?” Sure seems like a dark pattern when they round the execution times up, right?

   1. Zach Leatherman 48 min later

      @cthos yeah, that part but also these are maximums—it’d be nice to see CPU or memory utilization metrics at the current vCPU setting

      1. cthos 🐱 54 min later

         @zachleat The math does get a little fuzzy, even AWS has some "interesting" guidance for this: https://docs.aws.amazon.com/lambda/latest/operatorguide/computing-power.html

2. Zach Leatherman 2 hr later

   I made a little chart comparing how a few different hosts charge for serverless execution time (normalized to hours of usage) and the vCPU default can cost you a lot of unnecessary money if you’re not paying attention!

   1. genehack 10 hr later

      @zachleat thanks for putting together! this is a nitpick, but your legend would be easier to read sorted by service, then size, versus the current pseudo random order.

      1. Zach Leatherman 19 hr later

         @genehack yeah, 100%.