pauloaguia: That's right. Because, given the nature of web-based request-response application, there are no online users at all - when a page is generated and sent, the user is "disconnected". It is, in most cases, the system level issue (BrainKing background processes etc.) which can (but it can never be said for sure) cause an increased allocation of resources which are always limited. But the expansion thing I have mentioned is more about "the OS could recognize that a smart and instant low-level reconfiguration is required and should do it itself" which is not possible, of course. It's more complicated (Abigail please don't start a too technical discussion here ).
I think the blog is a better place to post a detailed overview, which is what I plan to do soon.