Milestone: #4 on Netcraft

Server NGINX
1

I usually pretend not to care about such things, but Igor deserves some
congratulations here…

http://survey.netcraft.com/Reports/200806/

  1. Apache - 84 million domains
  2. Microsoft IIS - 61 million
  3. Google - 10 million
  4. nginx - 2 million

So, what’ll it take to get to #3? An O’Reilly book?

Evan

2

So, what’ll it take to get to #3? An O’Reilly book?
8 million domains / hosts :wink:

Congratulations!

Martin

3

On Die 03.06.2008 23:27, Evan M. wrote:

So, what’ll it take to get to #3? An O’Reilly book?
Woha, super juhuuu ;-)))))
I’am very happy abou this even they means not all physically ;-))

Thanks and gratulation to all which have worked that this very great
product comes to fly ;-))

Aleks

4

Evan M. <emmiller+gmane@…> writes:

I usually pretend not to care about such things, but Igor deserves some
congratulations here…

http://survey.netcraft.com/Reports/200806/

  1. Apache - 84 million domains
  2. Microsoft IIS - 61 million
  3. Google - 10 million
  4. nginx - 2 million

I think this big jump is related to the fact that wordpress.com dropped
litespeed for nginx.

Another thing that reinforces this hypothesis is that litespeed’s stats
are now
less than 1/10 of what they were in may. I didn’t think that litespeed
had so
little adoption.

I suppose that (for now) lighttpd is still more popular than nginx if
you don’t
consider the wordpress bias.
Still, that’s a great result for nginx.
Congratulations to Igor!

Luigi

5

My feeling about the nginx project is that it is under-marketed and very
large amounts of lighttpd (and apache) users are still unaware of it.
Many would switch to it in the blink of an eye.

lighttpd and nginx can no longer be compared. lighttpd has stagnated
almost to a complete (public) halt during the past year or so, it hardly
receives any fixes or improvements (with the exception of one
extremely-overdue release in March). The long promised version 1.5
has not been coming through, either.

nginx on the other hand, subjectively, is a superior product both from
code quality / organization and from the awesome features / flexibility
and stability it provides - when compared to its direct and indirect
competitors. It is clearly written with care, passion and dedication
that few programmers posses – you just know that when you take a good
look at it.

Last but not least, and certainly one of the most important aspects, at
least for me, is that nginx receives constant fixes and enhancements -
and has been receiving fixes and enhancements ever since the project
became public, on a consistent and almost clockwork basis.

A big thanks to Igor and his employer for releasing this great piece of
software to the public and working to maintain it so diligently ever
since!

And with all this said, spread the word of nginx to everyone you know -
write and post about it everywhere. Let’s bring it to the top 2, where
it belongs.

Marc

6

Wednesday 04 June 2008 14:47:15 Just Marc napisał(a):

My feeling about the nginx project is that it is under-marketed and very
large amounts of lighttpd (and apache) users are still unaware of it.
Many would switch to it in the blink of an eye.

lighttpd and nginx can no longer be compared. lighttpd has stagnated
almost to a complete (public) halt during the past year or so, it hardly
receives any fixes or improvements (with the exception of one
extremely-overdue release in March). The long promised version 1.5
has not been coming through, either.

I heard one smart sentence about Rails - they became popular because of
good
webpage and screencast :wink:

However - we have got all our installations on nginx - is there any
place
where we can put info about it?

–
Rafał Zawadzki
System Architect

tel +48 22 8430101
mobile +48 600 883 759
skype id blvszcz
jabber id [email protected]

7

Rafa? Zawadzki wrote:

Wednesday 04 June 2008 14:47:15 Just Marc napisa?(a):

My feeling about the nginx project is that it is under-marketed and very
large amounts of lighttpd (and apache) users are still unaware of it.
Many would switch to it in the blink of an eye.

Nginx has still got some gremlins in it’s use of variables for vhost
definitions so you end up having to create a new vhost definition for
every vhost rather than just using an include template with lots of
variables in it. eg you can’t say: “access_log
/var/log/nginx/$server_name.access_log”

I think little stuff like this is holding back nginx more than you might
imagine… (my 2p…)

Ed W

(P.S. Thinking compile time variables here, not per hit variable
evaluation. Point is to setup a template vhost and then re-use it again
and again for all customers without needing to write a script)

8

On Jun 4, 2008, at 10:49 AM, Cliff W. wrote:

01.2007 lighttpd 172819
02.2007 lighttpd 702712

There is no “bias”. The reports are equally precise and equally
misleading for all server software.

Agreed. All of godaddy’s parked domains (and there are 10s of
millions) are on IIS (I believe) for example.

9

On Wed, 2008-06-04 at 11:27 +0000, Luigi Perroti wrote:

  1. Google - 10 million
  2. nginx - 2 million

I think this big jump is related to the fact that wordpress.com dropped
litespeed for nginx.

Absolutely.

I suppose that (for now) lighttpd is still more popular than nginx if you don’t
consider the wordpress bias.

Of course not. Virtual hosts are counted for all servers, not just
Nginx. You’ll notice that Lighttpd made a huge jump back in Feb 2007
when it was picked up by a company hosting thousands of domains (I
forget who it was, but I’m sure someone here can recall):

01.2007 lighttpd 172819
02.2007 lighttpd 702712

There is no “bias”. The reports are equally precise and equally
misleading for all server software.

Regards,
Cliff

10

Cliff W. wrote:

I suppose that (for now) lighttpd is still more popular than nginx if you don’t
consider the wordpress bias.
Of course not. Virtual hosts are counted for all servers, not just
Nginx. You’ll notice that Lighttpd made a huge jump back in Feb 2007
when it was picked up by a company hosting thousands of domains (I
forget who it was, but I’m sure someone here can recall):
01.2007 lighttpd 172819
02.2007 lighttpd 702712
There is no “bias”. The reports are equally precise and equally
misleading for all server software.

Given that context, one could easily argue that the Wordpress switch is
more interesting in the way of actual server usage than Lighty being
used for parking domains…

I agree these are all statistics, and have to be taken as such, but I
personally think that hosting a huge number of blogs on a server tells
me more about the capabilities than serving a lot of one page static
html sites :stuck_out_tongue:

Next up will have to be beating out the “Unknown” spot (some ~5 million
sites)!

Cheers!

11

On Jun 4, 2008, at 10:52 AM, Ed W wrote:

Nginx has still got some gremlins in it’s use of variables for vhost
definitions so you end up having to create a new vhost definition
for every vhost rather than just using an include template with lots
of variables in it. eg you can’t say: “access_log /var/log/nginx/
$server_name.access_log”

lord would i love to be able to use variables in log definitions. o
how my life maintain files would be easier.