@raggi @zwily @phusion_nl it's all about concurrent request capacity, not bandwidth
-
-
@bascule@zwily@phusion_nl my point is, rails cpu bound max response rate is trivial to generate. you *always* have a queue problem after -
@raggi@bascule@phusion_nl For our rails app, memory is usually the bottleneck before CPU, giving a hard limit to procs/box -
@zwily@bascule@phusion_nl right, it's hard to fill a box for max queue size, but, losing 50% of a queue that's 1000x too small....
End of conversation
New conversation -
-
-
@bascule@zwily@phusion_nl if each request starts timing out you're still DoS'dThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.