<story><title>AWS API Performance Comparison: Serverless vs. Containers</title><url>https://www.alexdebrie.com/posts/aws-api-performance-comparison/</url></story><parent_chain></parent_chain><comment><author>bastawhiz</author><text>Perhaps I misread, but it sounds like the author never managed to get Fargate to run without even a minimum of 3% failures?&lt;p&gt;That to me sounds like an astoundingly high number, especially for the amount of resources dedicated to the test (400GB of memory and 200 CPUs). Hell, if you&amp;#x27;re monitoring uptime, that&amp;#x27;s one nine (97% success).&lt;p&gt;I can&amp;#x27;t believe that this is a well-configured setup. Running 50 instances with four CPUs each at a total of ~100rps means that half of the CPUs are probably doing exactly nothing (and if my understanding is correct and they&amp;#x27;re using Flask in a single-threaded way, 150 of the 200 CPUs are going to be idle).&lt;p&gt;Triggering SNS is an API call. Assuming that&amp;#x27;s all the test application is doing, you hardly need one server to do this. I&amp;#x27;d bet that you could make 100 simultaneous API calls from a stock Macbook Pro with a small handful of Node or Go processes without even making your CPU spin up.&lt;p&gt;If Fargate can&amp;#x27;t handle 100rps (to make a single API call per request) with &amp;lt;10 instances, it&amp;#x27;s a useless product. But I find it hard to believe that Amazon would put something so absolutely incapable into the wild. With the specs the author put up, that&amp;#x27;s the equivalent of ~$10&amp;#x2F;hr (if I&amp;#x27;m reading their pricing page correctly). You could run 380 A1 instances, 58 t3.xl instances, or two m5a.24xlarge instances for that price.</text></comment>
<story><title>AWS API Performance Comparison: Serverless vs. Containers</title><url>https://www.alexdebrie.com/posts/aws-api-performance-comparison/</url></story><parent_chain></parent_chain><comment><author>zokier</author><text>This benchmark is all over the place; there are way too many variables changing to make any sorts of conclusions. You have flask-gunicorn-meinheld stack on the fargate side, all bits that might impact performance. Then there are the failing requests that alone would disqualify the comparison. I would also assume ApiGW to be slower than plain ELB, although I don&amp;#x27;t know for sure and this comparison certainly did give any information about that. No comparison of different lambda&amp;#x2F;fargate instance types, nor any mention about costs. Obviously just throwing more money should get better perf, so perf&amp;#x2F;$ is sort of important.</text></comment>