go-web-framework-benchmark

Serving a social network is not the case where you'd want just one server. Mainly due to reliability concerns, spikes in traffic and different patterns at different times. But if you like the idea of ignoring best practices, there are EC2 instances with 192 vCPUs that go for several thousands an hour. And taking as example Golang benchmarks https://github.com/smallnest/go-web-framework-benchmark where it's not uncommon to be able to serve 6 digits of 30ms requests per second with just 4 cores. Then the conclusion is, the limit is the sky, if you are stubborn enough.

Express is a slowest solution on the market. Fastify can handle as much as 60k (!) requests per second per core(!): https://www.fastify.io/benchmarks/ For example, go can handle about the same amounts (be advised that this tests are for 4 cores, so results have to be divided): https://github.com/smallnest/go-web-framework-benchmark

Compares to the other frameworks, the test code is here: https://github.com/smallnest/go-web-framework-benchmark

Yes. You are right about that, but we think a bit differently. we think that would be a good chance for contributors that want to contribute to Go projects or frameworks, also tell that we are trying to build something better and surely we have a vision. For the benchmark, we already opened a PR (https://github.com/smallnest/go-web-framework-benchmark/pull...) after running it locally. Thanks For your feedback

Yes, and there is already an opened Pull Request to https://github.com/smallnest/go-web-framework-benchmark/pull...

With the performance coming from being based on fasthttp, what does the framework offer on top? The README doesn't really mention any features explicitly (other than soft ones like "secure" and "fast"). A comparison with other fasthttp-based frameworks like https://github.com/savsgio/atreugo or https://github.com/gofiber/fiber would also be interesting. Or maybe a benchmark along the lines of https://github.com/smallnest/go-web-framework-benchmark. Looking at the commit history (7 commits, most of them from yesterday), the open issues (no way to define URL path variables yet, https://github.com/abahmed/gearbox/issues/15), and the release being v0.0.1, maybe it's a bit too early for a ShowHN? But if you have a vision of how it will be different and better than existing frameworks and the willingness to keep working on your project, then ho

I 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 . He explains why this is the most realistic benchmark suite so far. Thanks you for using (or talking about) Iris!

The graph at their GitHub page might be a bit easier to understand: https://github.com/kataras/iris There's a bit more detailed bench here: https://github.com/smallnest/go-web-framework-benchmark