Benchmarking Nginx on a prehistoric PIII 500

[Denis Arh]

I really think the environment itself is not the issue. It was testet on
VMWare because it was easier to set-up at the moment. All testing servers
had the same conditions, and adding the benchmarking tool to the whole mess
did only create more realistic conditions (there is usually a few other
services running on the VPS)

Yes, I could do the tests again, removing all disturbing factors (another
machine for the benchmarking tool, dedicated box for both of them), but this
would only create a perfect conditions for all of the tested software and
I'm positive that this would not do anything else than raise the final
numbers by same factor for all.

And I think I did a much better job here then most of the developers of the
testes software (by the number different of servers used, specifying what
hardware I've used and most finally providing the config files...)

About the version: VMWare Workstation 6.0.1 build-55017.

--
Denis

On Fri, Mar 14, 2008 at 4:51 AM, Denis S. Filimonov <den.lists at gmail.com>
wrote:

> On Thursday 13 March 2008 23:31:27 Cliff Wells wrote:
> > On Thu, 2008-03-13 at 19:54 -0500, Denis S. Filimonov wrote:
> > > I'm surprised noone has asked the most obvious question yet: Why
> vmware?
> > > It's a huge unknown factor in the measurement which renders the whole
> > > experiment questionable at best.
> >
> > I think this is actually a good benchmark specifically because it's in
> > VMware (although I think Xen or OpenVZ would have been more
> > appropriate).  It's not a pure HTTP server test, rather a test of how
> > the various servers operate in the constrained environment of a VPS.
> > With the massive increase in VPS hosting and the fact that lots of
> > people utilizing VPS hosting would benefit from a lightweight HTTP
> > server makes this particular benchmark quite useful.
> >
> If that was the intent, it should be reflected in the title, because now
> it's
> outright misleading. Also the version of VMWare is essential.
>
> --
> Denis.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080314/61001922/attachment.html>