> That's still an architectural thing. If CPU isn't an issue, why would you be running your application server on a different machine from your database? Becau

> That's still an architectural thing. If CPU isn't an issue, why would you be running your application server on a different machine from your database? Because that'll be too much of a scalability limitation. Rails etc are rather CPU heavy. In cloud environments it's also typically much more feasible to scale the stateless parts up and down than the database. > Even if you have it on another machine, it's on the same switch, right (also an architectural choice)? Yep, was on the same switch in my example. > So latency should be sub millisecond, and irrelevant for a single request. In my testcase it was well below a millisecond (2.8k QPS on a single non-pipelined connection would not be possible, it implies a RTT <= 0.35ms), but I don't at all agree that that makes it irrelevant for a single request.