Thanks! It has been some time since we ran the profiler on the Ruby code, but AFAIR it was doing a lot of parsing; also it extensively used a logging gem that

Thanks! It has been some time since we ran the profiler on the Ruby code, but AFAIR it was doing a lot of parsing; also it extensively used a logging gem that was dumping Ruby objects to strings. We could have just used another logging library and rewritten the parsing code to C, but when we checked the numbers the potential improvements didn't seem good enough. Erlang probably would have worked too, but we already had some code in Go.