Show HN: Go HTTP Request Router Benchmark
1–10 of 21 posts
Re: Show HN: Go HTTP Request Router Benchmark
#2Would 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
#3What about Revel framework?
Re: Show HN: Go HTTP Request Router Benchmark
#4What about Revel framework?
Revel is a bit too magic. It is hard to benchmark the routing alone.
Re: Show HN: Go HTTP Request Router Benchmark
#5Would 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
#6So the one you recommend is the one you wrote yourself?
Re: Show HN: Go HTTP Request Router Benchmark
#7So 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.
Re: Show HN: Go HTTP Request Router Benchmark
#8It's currently very hard to digest any information from this. Some bar-charts would be helpful.
Re: Show HN: Go HTTP Request Router Benchmark
#9So the one you recommend is the one you wrote yourself?
I don't mind someone recommending their own work when the rationale is backed by hard data.
Re: Show HN: Go HTTP Request Router Benchmark
#10So 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.