<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compute on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/compute/</link><description>Recent content in Compute on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 29 Apr 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/compute/index.xml" rel="self" type="application/rss+xml"/><item><title>Alibaba Cloud Full Stack (2): ECS — Compute That Actually Makes Sense</title><link>https://www.chenk.top/en/aliyun-fullstack/02-ecs-compute/</link><pubDate>Wed, 29 Apr 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-fullstack/02-ecs-compute/</guid><description>&lt;p>The first ECS instance I ever launched was wildly over-provisioned. I picked the biggest instance I could find — an &lt;code>ecs.r6.8xlarge&lt;/code> with 32 vCPUs and 256 GiB RAM — to run a Flask app that served maybe 20 requests per minute. I burned through credits in a week, panicked, learned how to downsize online, and discovered my app ran perfectly on a 2-vCPU box costing 94% less. Right-sizing matters more than raw power, and understanding the compute layer is the single most useful thing you can learn about any cloud platform.&lt;/p></description></item></channel></rss>