> > My 5 cents about ibrowse: after switching it from standard httpc library, we > found *significant* cpu consumption (almost twice). Our profiler shows that > the bottle-neck is HTTP headers parsing. Is it possible to optimize that > stuff? Probably switching to erlang:decode_packet makes sense. What profiler do you use?