This is a list of ceilings that will be bumped into assuming service continues growth. First limiting factor appears to be disk space, which needs attention at or before 4x growth. (Estimate: 1 to 1.5 years fromn now, unless things get exciting.) All resources can be expanded as necessary, and all should give ample warning before being maxed out. Ultimately, CPU time takes most effort to expand.
Human ----- Supply: 1 person + friends of service Detail: Administrative support, misc. Today : less than or equal to 1 person Limit : not in forseeable future, due to full automation Bandwidth --------- Supply: T1 or better. Demand: SMTP messge costs 2KB , HTTP uses 3KB Today : 1000 messages, 2000 page views = 8000 KB/day Limit : more than 10x Time (CPU) ---------- Supply : one not-so-fast CPU Demand, htdig : 10 hr / week Limit, htdig : 17x Demand, mhonarc : nearly full time Limit, mhonarc : 10x (*) Demand, other : neglible Storage ------- Supply : 12 gig partition (**) Demand : MHonArc and HTDig are both hogs Today : almost 3 gigs used in a measly 120,000 messages Limit : 4x (*) MHonArc will gracefully degrade as capacity increase. Very difficult to estimate. Benchmarks, and looking at logs suggest lots and lots of room to grow, but depends on traffic patterns. Take with multiple grains of salt (either direction) (**) Storage. While more storage is available, currently data lives on a single 12GB partition. Today's cheap single partition expansion options top out at 25 GB (IBM) Larger storage solutions are possible, ranging from a bunch of partitions mounted to various points, to RAID array or fancy filesystems. Would like to stick to simple solution until growth forces otherwise.
