Sunday, October 16, 2011

Writing a minimalistic web-server using event machine

I wanted a small and efficient web-server that can handle large amount of http request that is easy to play around with. The EventMachine is a good candidate together with the http parser provided by Thin. I didn't know much about thin when I started this exercise, but it is also built on top of EventMachine and is gaining in popularity according to this State of the stack article.

But anyway, if you want a simple bare-bones web server with no fluff, continue reading...

Before we start with the actual implemtnation, we need to install some ruby gems. This is easily done by running the following commands in your shell

gem install eventmachine
gem install thin

The server is pretty standard setup using eventmachine and looks like this

# FILE: server.rb

require 'rubygems'
require 'eventmachine'
require_relative './thin_http_parser.rb'

# Freeze some HTTP header names & values
KEEPALIVE = "Connection: Keep-Alive\r\n".freeze

class RequestHandler < EM::Connection
  def post_init
    @parser =

  def receive_data(data)
    handle_http_request if @parser.parse(data)

  def handle_http_request
    p [@parser.env, @parser.body.string]
    keep_alive = @parser.persistent?

    data = "OK"
    send_data("HTTP/1.1 200 OK\r\nContent-Type: text/html\r\nContent-Length: #{data.bytesize}\r\n#{ keep_alive  ? KEEPALIVE.clone : nil}\r\n#{data}")
    if keep_alive

host,port = "", 8083
puts "Starting server on #{host}:#{port}, #{EM::set_descriptor_table_size(32768)} sockets" do
  EM.start_server host, port, RequestHandler
  if ARGV.size > 0
    forks = ARGV[0].to_i
    puts "... forking #{forks} times => #{2**forks} instances"
    forks.times { fork }

At last, we need an http parser. I tried both writing my own in pure ruby and the EM::P::HeaderAndContentProtocol parser. But in then end I used the thin parser since it was the fastet parser and it is easy to integrate. This is the code for the parser

# FILE: thin_http_parser.rb

require 'rubygems'
# Uncomment this line if 'thin_parser' is not found
# require 'thin' 
require 'thin_parser'
require 'stringio'

# Freeze some HTTP header names & values
HTTP_1_0          = 'HTTP/1.0'.freeze
KEEP_ALIVE_REGEXP = /\bkeep-alive\b/i.freeze
CLOSE_REGEXP      = /\bclose\b/i.freeze

# Freeze some Rack header names
RACK_INPUT        = 'rack.input'.freeze

# A request sent by the client to the server.
class RequestParser
  INITIAL_BODY      = ''

  # Force external_encoding of request's body to ASCII_8BIT
  INITIAL_BODY.encode!(Encoding::ASCII_8BIT) if INITIAL_BODY.respond_to?(:encode!)

  # CGI-like request environment variables
  attr_reader :env

  # Unparsed data of the request
  attr_reader :data

  # Request body
  attr_reader :body

  def initialize
    @parser   =
    @data     = ''
    @nparsed  = 0
    @body     =
    @env      = {
      RACK_INPUT        => @body,

  # Parse a chunk of data into the request environment
  # Returns +true+ if the parsing is complete.
  def parse(data)
    if @parser.finished?  # Header finished, can only be some more body
      body << data
    else                  # Parse more header using the super parser
      @data << data
      @nparsed = @parser.execute(@env, @data, @nparsed)

    if finished?   # Check if header and body are complete
      @data = nil
      true         # Request is fully parsed
      false        # Not finished, need more data

  # +true+ if headers and body are finished parsing
  def finished?
    @parser.finished? && @body.size >= content_length

  # Expected size of the body
  def content_length

  # Returns +true+ if the client expect the connection to be persistent.
  def persistent?
    # Clients and servers SHOULD NOT assume that a persistent connection
    # is maintained for HTTP versions less than 1.1 unless it is explicitly
    # signaled. (
    if @env[HTTP_VERSION] == HTTP_1_0

    # HTTP/1.1 client intends to maintain a persistent connection unless
    # a Connection header including the connection-token "close" was sent
    # in the request
      @env[CONNECTION].nil? || @env[CONNECTION] !~ CLOSE_REGEXP
The server is started by running
ruby server.rb

It is also possible to fork the process in order to increase the performance by adding an integer at the end of the start line. If I want to start 4 instances of server, I currently run

ruby server.rb 2

There is not much of an idea to run a lot more instances than you have cores on the machine, since it will only slow things down. And be aware that "fork" doesn't work out of the box on windows OS.

With this setup, I easily get 100.000+ reqs/seconds using ab with keep-alive switch (-k) on a medium core i5 processor.

To summarize my little hacking is that I really enjoy the simple and yet powerful API that EventMachine offers. You can really write compact code and yet good performing servers with Ruby and EventMachine


  1. Please post your whole ab command please. I've tried with below command and get:

    ab -k -c 50 -n 100000

    Requests per second: 28541.31 [#/sec] (mean)

  2. really enjoyed reading your different articles. They are so informative and thanks man for code for the parser ....

  3. Excellent, Nils, great work.
    I get 20K rps with epoll without forking.

    But I cannot fork if I use epoll. And without epoll, I cannot have more than a few hundred file descriptors (otherwise it is sloooow), so 100,000 rps is not very usefull.

    I don't think there is any solution, unfortunately. Again, great work.

  4. To increase the performance, you need to comment out the "p [@parser.env, @parser.body.string]" at line 18 in server.rb.... Just removing that line almost doubles the performance.

  5. I found this post very exciting. I think you will have any other post on this topic? I am also sending it to my friend to enjoy your working style. Cheers!

  6. Thanks for excellent blog.I'm happy to find useful blog share in my friends. THANK YOU
    Mindfulness Courses Dublin

  7. spiegelklemTerrific way of expressing those things in your post. Clear cut meanings.

  8. ello there, just became aware of your blog through Google, and found that it's really informative. I'm gonna watch out for brussels. I will appreciate if you continue this in future. Lots of people will be benefited from your writing.
    Mindfulness Courses Dublin

  9. Thank you for the work you have put into your nice blog. We will bookmark to your blog because it is very informational. We love the site and will come back to see your new posts.
    Pre Marriage Courses

  10. I enjoyed your entries on Toxic Words - such great thoughts and a wonderful reminder to watch the words I use - to be positive and kind and use words to build up rather than tear down. :)
    verhuizen hoorn

  11. This website has very good content. Thank you for the great article I did enjoyed reading it, I will be sure to bookmark your blog and definitely will come back from again

  12. Computers themselves, and software yet to be developed, will revolutionize the way we learn.

  13. Incredible post! I am really getting prepared to over this data, is exceptionally useful my companion. Likewise extraordinary blog here with the majority of the significant data you have. Keep doing awesome doing here.

  14. The pursuit of truth and beauty is a sphere of activity in which we are permitted to remain children all our lives.

  15. Its wonderful blog really very nice site and blog facility.every title is very nice and very fatastic concept. Thanks for sharing the information.

  16. Thank you for the work you have put into your nice blog. We will bookmark to your blog because it is very informational. We love the site and will come back to see your new posts.
    hardsten keukenblad

  17. You got an extremely helpful website I actually have been here reading for regarding an hour. I’m an initiate and your success is incredibly a lot of a concept on behalf of me.

  18. I find some interesting details from your blog. It helps me very much. Keep posting such stuff continuously.
    GED Online Diploma

  19. I was about to say something on this topic. But now i can see that everything on this topic is very amazing and mind blowing, so i have nothing to say here. I am just going through all the topics and being appreciated. Thanks for sharing.

  20. Thanks for sharing so significative article with us. I agree with your idea competely.I am looking forward to another great article from you.
    stenen keukenwerkblad