0
# A Web Server Called *Ebb*
0
-Ebb aims to be a very small and fast web server specifically for hosting
0
+Ebb aims to be a small and fast web server specifically for hosting
0
web frameworks like Rails, Merb, and in the future Django.
0
It is not meant to be a full featured web server like Lighttpd, Apache, or
0
-Nginx. Rather it should be used in multiplicity behind a load balancer and
0
-a front-end server. It is not meant to serve static files in production.
0
+Nginx. Rather it should be used in multiplicity behind a
0
+[load balancer](http://brainspl.at/articles/2007/11/09/a-fair-proxy-balancer-for-nginx-and-mongrel)
0
+and a front-end server. It is not meant to serve static files in production.
0
@@ -36,13 +37,13 @@ forthcoming.
0
-The Ruby binding is available as a Ruby Gem. It can be install simply by
0
+The Ruby binding is available as a Ruby Gem. It can be install by executing
0
Ebb depends on having glib2 headers and libraries installed. (Easily available
0
+on any UNIX system.) A manual downloads can be found at
0
+the [RubyForge project page](http://rubyforge.org/frs/?group_id=5640).
0
@@ -52,6 +53,11 @@ for quick and beautiful code, but for production web servers that might handle
0
thousands of requests a second, an attempt should be made to be as efficient
0
as possible in processing connections.
0
+Following are some benchmarks. Please take these measurements with a grain
0
+of salt. Benchmarks like these are notorious for presenting an inaccurate
0
+or highly slanted view of how software performs.
0
+The code for these can be found in the `benchmark` directory.
0

0
This shows how the web servers perform with respect to throughput (using a
0
@@ -63,11 +69,10 @@ A simple concurrent clients benchmark serving a *hello world* page.
0

0
-Ebb processes upload before handing it over to the web application. This
0
+Ebb processes uploads before handing it over to the web application. This
0
allows Ebb to continue to process other clients while the upload is in
0
-progress. The large difference here is merely because Ebb's internal request
0
-buffer is set at 40 kilobytes before it writes to file. (Improvement can
0
+progress. The cliff at 40k here is because Ebb's internal request
0
+buffer is set at 40 kilobytes before it writes to file.
Comments
No one has commented yet.