> I guess... I was wondering more in terms of the big picture with > HTTP parsing, I/O, and response generation taken into account.
I wasn't too sure how to benchmark the entire loop. But regardless 18/20M i/s shows that it should be meaningless. It's only executed once per request, so would "waste" 1 second for 18 million requests processed. > (and there may be improvements in those areas later this year, > assuming the world doesn't end sooner...) If you are interested in general optimizations, I did spot a bunch of sub optimal patterns, such as `=~` in places where a string comparison, or `match?` would do. However many optimizations are only available on more recent rubies.
