Live data from Hacker News

Show HN: Go HTTP Request Router Benchmark

github.com

1–10 of 21 posts

Re: Show HN: Go HTTP Request Router Benchmark

#2
Would be great to see a benchmark of how much time is actually spent in routing compared to all the other disciplines involved in responding to a HTTP request. For any interesting application, I suspect routing will be the least of your troubles in regards to performance.

Re: Show HN: Go HTTP Request Router Benchmark

#5
post #2

Would be great to see a benchmark of how much time is actually spent in routing compared to all the other disciplines involved in responding to a HTTP request. For any interesting application, I suspect routing will be the least of your troubles in regards to performance.

For most web-apps this is definitely true. But an efficient router doesn't hurt either. If the router scales well, the routing part will never become your bottleneck. If the router is also memory efficient, it can reduce the amount of time the Garbage Collector needs.

Re: Show HN: Go HTTP Request Router Benchmark

#10
post #6

So the one you recommend is the one you wrote yourself?

I'd recommend Goji to most users. The one I wrote has better performance, but also less features.

Goji does very well given it includes a request context implementation as well. I've been porting over an existing net/http + gorilla/mux app and like its design.
Post reply on HN