No, that's for a production website and requires setup. They just need to replace webrick with thin.
> gem install thin
then
> thin start
instead of
> ./script/server
Simple.
httperf --hog --num-conns 1000 --num-calls 1000 --burst-length 20 --port 3000 --rate 1000 --uri=/pong
The best I got was 258 requests / sec and 13.5 average responses / sec. The chart on the website plots responses / sec. So thin seems to perform worse. I'm guessing that we're running into the limit of 1024 file descriptors. I didn't test with the libev version of Snap, so my testing had that limit too, but my guess is that Snap is faster and manages to stave off the limit long enough to serve a reasonable number of requests. But I don't know for sure.
script/server -e production
Running in development mode severely hampers Rails' performance.
Better would be to just limit the test to single-process/single-thread. The idea should be to compare web frameworks not web servers.
> thin -e production -s 4 start
The problem is that each process listens on its own port. They can't all listen on port 3000, so you need some sort of proxy to parcel out the requests.