go-http-routing-benchmark

I wonder if the new version takes the opportunity to make the muxer faster. I needed a path matcher / muxer and I settled on forking julienschmidt/httprouter [1] into my own project, pathmatcher [2]. What I like about the original it is that it uses a trie for mapping paths to handlers, which can look up routes very quickly [3], and is optimized for low/zero allocations. My changes generalizes it (the 'handler' value can be any generic type) and exposes the underlying data structure so you can do non-http.Handler things with it if you want. [1]: https://github.com/julienschmidt/httprouter [2]: https://github.com/infogulch/pathmatcher [3]: https://github.com/julienschmidt/go-http-routing-benchmark

Gin uses HttpRouter (https://github.com/julienschmidt/httprouter) which is heavily optimized for performance, as can seen here: https://github.com/julienschmidt/go-http-routing-benchmark. As the author has noted on the page that "a comparison with other frameworks is coming soon" personally I would play safe and stick with HttpRouter for now and if it makes sense rewrite routing and switch to Lion once the performance characteristics are available. (Or maybe the author, also the OP, could join and tell how Lion compares to HttpRouter)

Basically there aren’t much reasons besides security considerations to use net/http multiplexer at all. The baseline was profiled under STATICALL as the default net/http multiplexer does not support dynamic paths http://golang.org/pkg/net/http/#ServeMux. The benchmark is named BenchmarkHttpServeMux_StaticAll you can read the code at https://github.com/julienschmidt/go-http-routing-benchmark/b.... Frankly, net/http it not a very good http router. The results show that julienschmidt/httprouter trie based implementing outperforms net/http by 60x.

I ran it against: https://github.com/julienschmidt/go-http-routing-benchmark which is a pretty thorough benchmark for Go multiplexers. The author's own framework is always fastest and takes the least amount of memory (there's nothing suspicious about it, it really is the fastest). The test does a good job of showing just how horribly slow some of these, like Gorilla or Martini, really are. Anyways, Bone seems better than the horrible ones, but it's far from the fastest. A snapshot: HttpRouter_GithubStatic 20000000 61.7 ns/op 0 B/op 0 allocs/op Bone_GithubStatic 100000 12441 ns/op 2880 B/op 60 allocs/op HttpRouter_GithubParam 5000000 341 ns/op 96 B/op 1 allocs/op Bone_GithubParam 500000 2684 ns/op 853 B/op 12 allocs/op It also cra

Here's a collection of Go routers benchmarked against real API sets: https://github.com/julienschmidt/go-http-routing-benchmark