Page Discussion History

Difference between revisions of "Main"

Line 19: Line 19:
[http://nginx.net/nginx-venture-funding.html Read entire story]
[http://nginx.net/nginx-venture-funding.html Read entire story]
<p style="margin-top: 3em;">
<span class="plainlinks" style="float: left; margin-top: 5px; margin-right: 10px;">
[http://en.wikipedia.org/wiki/Vostok_1#Launch http://wiki.nginx.org/images/c/ca/Vostok1.png]
<h1>Nginx 1.0 is released!</h1>
[http://en.wikipedia.org/wiki/Vostok_1#Launch Here we go!]<br />
[http://www.nginx.org/en/download.html nginx-1.0.0] stable version has been released.<br />
The repository is available at svn://svn.nginx.org.<br />
<br />a
Nginx development started about 9 years ago. The first public version 0.1.0 was released on October 4, 2004. Today, it serves [http://w3techs.com/technologies/overview/web_server/all 10.2% of all known websites] and [http://w3techs.com/technologies/breakdown/ws-nginx/top_level_domain 56.1% of all Russian sites] according to w3techs.<br />
<br />
The January 2012 survey undertaken by Netcraft revealed that Nginx served [http://news.netcraft.com/archives/2011/04/06/april-2011-web-server-survey.html 8.5% of the million busiest sites] during the survey period and [http://news.netcraft.com/archives/2011/04/06/april-2011-web-server-survey.html 12.2% of all active sites] during the same period.

Revision as of 19:11, 21 January 2012

Nginx is a free, open-source, high-performance HTTP server and reverse proxy, as well as an IMAP/POP3 proxy server. Igor Sysoev started development of Nginx in 2002, with the first public release in 2004. Nginx now hosts nearly 12.18% (22.2M) of all domains worldwide. As Netcraft predicted, Nginx now surpasses Microsoft IIS as the second most popular web server.

Nginx is known for its high performance, stability, rich feature set, simple configuration, and low resource consumption.

Nginx is one of a handful of servers written to address the C10K problem. Unlike traditional servers, Nginx doesn't rely on threads to handle requests. Instead it uses a much more scalable event-driven (asynchronous) architecture. This architecture uses small, but more importantly, predictable amounts of memory under load.
Even if you don't expect to handle thousands of simultaneous requests, you can still benefit from Nginx's high-performance and small memory footprint. Nginx scales in all directions: from the smallest VPS all the way up to clusters of servers.

Nginx powers several high-visibility sites, such as WordPress, Hulu, Github, Ohloh, SourceForge, WhitePages and TorrentReactor.

Nginx lands $3M in funding, plans to open San Francisco headquarters

Open source web server developer NGINX has received $3 million in a fully subscribed Series A round. Today NGINX powers over 40,000,000 domains on the Internet, and over 20% of the top 1000 busiest websites around the world, including Facebook, Zappos, Groupon, LivingSocial, Hulu, TechCrunch, Dropbox and WordPress.

"Several of the companies we invested in were able to solve significant scaling issues by switching their web platforms to NGINX," said Thomas Gieselmann of BV Capital. "NGINX transparently and effectively enables the growth of the largest sites on the Internet today."

Read entire story


Nginx book is available!

Clement Nedelcu has written the first English book covering Nginx including such topics as downloading and installing Nginx, configuring and using modules, and much more. It provides step-by-step tutorials for replacing your existing web server with Nginx. With commented configuration sections and in-depth module descriptions, you will be able to make the most of the performance potential offered by Nginx.

I ran a simple test against Nginx v0.5.22 and Apache v2.2.8 using ab (Apache's benchmarking tool). During the tests, I monitored the system with vmstat and top. The results indicate that Nginx outperforms Apache when serving static content. Both servers performed best with a concurrency of 100. Apache used four worker processes (threaded mode), 30% CPU and 17MB of memory to serve 6,500 requests per second. Nginx used one worker, 15% CPU and 1MB of memory to serve 11,500 requests per second.

-- Linux Journal

There are several translations of the information on this wiki. If you can help translate into your native language, please feel free to contribute.