coates’s Twitter Archive—№ 8,420

…in reply to @undefined
@tiemonster actually, the bottleneck was MongoDB (locking); we were CPU-bound. Hard to capacity-plan a 15x spike at our size. Recovering (-:
On twitter.com 2011 Aug 30 Mood -1 🙁