The comparison with AWS Lambda seems to ignore the AWS memory snapshot option called "SnapStart for Python". I'd be interested in seeing the timing comparison extended to include SnapStart.
Python Workers use snapshots by default and unlike SnapStart we don't charge extra for it. For many use cases, you can run Python Workers completely for free on our platform and benefit from the faster cold starts.
They are comparing the baseline product of all three platforms. Why should we take paid add ons into account for 1 platform.
As I mentioned, if you are ok with paying, then you should also compare Provisioned concurrency on AWSbas well, which has 0 cold start (they keep a prewarmed lambda for you).
Product comparisons are not purely technical in nature. As a user, if im paying extra, I would much rather the 0 cold start than just a reduced cold start especially with all these additional complexities.
> AWS Lambda (No SnapStart) Mean Cold Start: 2.513s Data Points: 1008 > AWS Lambda (SnapStart) Mean Cold Start: 0.855s Data Points: 17 > Google Cloud Run Mean Cold Start: 3.030s Data Points: 394 > Cloudflare Workers Mean Cold Start: 1.004s Data Points: 981