4 ms·
That graph is really confusing, is the x axis a progression of processing times from 0 up to ~1000ms? If so then wouldn't it mean that Echo-2-fasthttp has nearl
by gelatocar 10y ago
That graph is really confusing, is the x axis a progression of processing times from 0 up to ~1000ms? If so then wouldn't it mean that Echo-2-fasthttp has nearly as good requests/second?
- mkishi 10y agoIt is confusing. They meant the benchmark used a 500ms "workload" (sleep) per request handler -- x isn't really an axis.
- Svenskunganka 10y agoThe graph at their GitHub page might be a bit easier to understand: https://github.com/kataras/iris https://github.com/kataras/iris There's a bit more detailed bench here: https://github.com/smallnest/go-web-framework-benchmark https://github.com/smallnest/go-web-framework-benchmark
- deleted 10y ago[deleted]
- kataras 10y agoI dont want to interrupt you guys, just writing this info. I will not try to do criticism on other comments, you're free to tell everything about the project, but I think you should read the README first and navigate to the benchmark suite (which is not mine) https://github.com/smallnest/go-web-framework-benchmark https://github.com/smallnest/go-web-framework-benchmark . He explains why this is the most realistic benchmark suite so far. Thanks you for using (or talking about) Iris!