Turn traffic into specs · generate a plan
Cloud servers get bought wrong in two ways: too small to hold traffic, or oversized and wasteful. The goal was to convert daily PV, concurrency and data volume into explicit specs.
Traffic is split into four buckets - CPU, memory, disk IO, bandwidth - each mapped to a range via empirical coefficients. Peak factors and growth rates then produce a scaling ladder and an order-ready specification.
Common PHP/MySQL bottlenecks are encoded as rules (connections, opcache, slow queries, inodes); each plan marks its bottleneck and the order in which to optimise.
Download source ↓ (free with an account)