Big-O growth, RAID capacity, storage growth, latency and throughput budgets, Little's law, queueing, Erlang and SLA downtime.
payments ON MAINNET (real money) · 10 live endpoints
| Endpoint | Price | What it answers |
|---|---|---|
GET /big-o | $0.02 | Compare growth classes (n, n log n, n^2, 2^n, n!) at a given n: operation counts, run time, largest n a time budget allows. |
GET /capacity-planning | $0.02 | Units needed for a peak load at a target utilisation plus N+k redundancy, utilisation after failures, and growth projection. |
GET /erlang-staffing | $0.02 | Erlang B and C: trunks for a blocking target, or agents for a service level such as 80 percent answered in 20 seconds. |
GET /latency-budget | $0.02 | Add up serial stage latencies against a target (share per stage, slack, bottleneck) and compute tail amplification from fan-out. |
GET /littles-law | $0.02 | Little's law L = rate x time in system: solve for concurrency, throughput or latency given any two; sizes pools. |
GET /queue-model | $0.02 | M/M/1 and M/M/c queue: utilisation, probability of waiting (Erlang C), queue length, wait and response time, tail odds. |
GET /raid-capacity | $0.02 | RAID 0/1/5/6/10 and ZFS RAID-Z usable capacity, efficiency, fault tolerance, write penalty and rebuild read-error risk. |
GET /sla-downtime | $0.02 | SLA availability (99.9 percent, three nines) to allowed downtime per day, month and year; series and parallel composition. |
GET /storage-growth | $0.02 | Compound storage growth: size after N months, raw capacity with replication and overhead, months to double, months until full. |
GET /throughput-budget | $0.02 | Requests per second times payload size to Mbps with peak factor, protocol overhead and link headroom; or IOPS to MB/s. |
GET /catalog returns this list as JSON. Activity hub · uptime.
Textbook formulas computed locally, provided as is. Queueing results assume Poisson arrivals and exponential service times; RAID rebuild risk uses an assumed unrecoverable read error rate; Big-O operation counts ignore constants and hardware. Use measured data for real capacity decisions, and treat results as planning estimates, not guarantees. Transfer-time, TCP window and propagation-delay maths live in the network-calc shelf and are not repeated here. Every paid response carries a disclaimer field.