6 ms·
Huh. I'm not sure I saw that particular project during my search. It looks neat! Without having looked in detail at httprouter, I think the most obvious reason
by zenazn 12y ago
Huh. I'm not sure I saw that particular project during my search. It looks neat!
Without having looked in detail at httprouter, I think the most obvious reason it might not be sufficient is that it doesn't support regular expressions. This might not be a dealbreaker, but I'm fond of the occasional regex route, and I'd have to think long and hard about whether it's worth giving up for a faster router. And plus, I'm still not sure router speed actually matters for most applications.
In any event, I do have a long plane trip coming up, and I'm sure Goji will grow itself something at least slightly more efficient than a linear scan then. I'm think Goji's router and middleware stack are already zero-allocation, so it'll just be finding a way to binary search through routes.
- Matrixik 12y agoYou can find benchmarks in pull request for https://github.com/cypriss/golang-mux-benchmark https://github.com/cypriss/golang-mux-benchmark: https://github.com/cypriss/golang-mux-benchmark/pull/5 https://github.com/cypriss/golang-mux-benchmark/pull/5 (the last one)