|
| 1 | +Capacity Planning |
| 2 | +***************** |
| 3 | + |
| 4 | +(Seems reasonable to have the Statistics for Engineers course be a pre-req for |
| 5 | +this course) |
| 6 | + |
| 7 | +Fundamentals of capacity planning |
| 8 | +================================= |
| 9 | + |
| 10 | +Resource usage investigation and exploration |
| 11 | +--------------------------------------------- |
| 12 | + |
| 13 | +* Examples: CPU:req/sec ratio, memory footprint:req/sec ratio, disk consumption |
| 14 | + per user/per sale/per widget, etc. |
| 15 | +* Application:Infrastructure metric relationships |
| 16 | +* 2nd order capacity (logging, |
| 17 | + metrics+monitoring systems, ancillary systems) |
| 18 | + |
| 19 | +Finding ceilings |
| 20 | +---------------- |
| 21 | + |
| 22 | +* Discovering resource limits |
| 23 | +* Comparing different hardware/instance profiles - production load versus |
| 24 | + synthetic |
| 25 | + |
| 26 | + * Benchmarking: pitfalls, limitations, pros/cons |
| 27 | + * http://www.contextneeded.com/system-benchmarks |
| 28 | + |
| 29 | +* Multivariate infra limits (multiple resource peak-driven usage) Ex: web+image |
| 30 | + uploads, caching storage+processing, etc. |
| 31 | +* Architecture analysis (anticipating the next bottleneck) |
| 32 | + |
| 33 | +Forecasting |
| 34 | +============ |
| 35 | + |
| 36 | +Linear and nonlinear trending and forecasting (“steering by your wake”) |
| 37 | +----------------------------------------------------------------------- |
| 38 | + |
| 39 | +Details of automatic forecasting and scaling |
| 40 | +-------------------------------------------- |
| 41 | + |
| 42 | +Seasonality and future events |
| 43 | +----------------------------- |
| 44 | + |
| 45 | +* Organic growth approaches (bottom-up infra driven, top-down app driven) |
| 46 | +* inorganic growth events (new feature launch, holiday effects, “going viral”, |
| 47 | + major public announcement) |
| 48 | +* Provisioning effects on timelines, financial tradeoffs |
| 49 | + |
| 50 | +Diagonal scaling |
| 51 | +================ |
| 52 | + |
| 53 | +(vertically scaling your already horizontal architecture) |
| 54 | + |
| 55 | +Reprovisioning and legacy system usage tradeoffs |
| 56 | +------------------------------------------------ |
0 commit comments