Davi Arnaut wrote:
This is true for expensive hardware and very well designed operating
systems and file systems.. and the space is not infinite.
Not at all - commodity hardware will serve just as well.
The real killer in this case is the slow client, which can be one, two
or three orders of magnitude slower than the average client. This means
that it will hog one, two or three orders of magnitude more of the
server backend's resources than the average request, and this is where a
cache can be most effective.
In terms of space, caches are not infinite in size, but then neither are
the majority of backend websites either.
But... OK. Back to the topic I thought that one of the key points of
async/event based servers were that we use software to scale and not
hardware (so that hardware is not the bottleneck)... like serving
thousands of slow clients from commodity hardware.
Sure, but I think the point that Brian was making was that you could
support the kind of large load sizes that are traditionally associated
with event based models using a prefork or worker setup, simply by
making sure you have enough RAM.
Very useful information to know.
Regards,
Graham
--
21 messages in org.apache.httpd.devRe: Is async the answer
