Go Web Frameworks: A benchmark only comparison

blov · · 1299 次点击    
这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
<p>Hello, yesterday I did a comparison of the web frameworks written in go, the results are controversially. I though that the http-router is the faster but it&#39;s not (?) . The winner seems to be a framework called &#39;Iris&#39; I didn&#39;t knew it until yesterday, second is the framework &#39;Gin&#39; and the http-router is third. My github fork of the <a href="https://github.com/julienschmidt/go-http-routing-benchmark/" rel="nofollow">https://github.com/julienschmidt/go-http-routing-benchmark/</a> is here: <a href="https://github.com/goc0der/go-http-routing-benchmark/" rel="nofollow">https://github.com/goc0der/go-http-routing-benchmark/</a> . Take a look and let&#39;s discuss it.</p> <hr/>**评论:**<br/><br/>CaptaincCodeman: <pre><p>kataras I presume? back with a new name?</p> <p>You are still pushing your misleading benchmarks. I thought initially you were just ignorant about how to do them but now I realize you are really determined to try and mislead people. The performance of your framework really isn&#39;t bad but it is simply not what you portray it to be. You are comparing a cache when everyone else&#39;s benchmarks are measuring the router.</p> <p><a href="https://www.reddit.com/r/golang/comments/4a8yit/is_this_the_fastest_go_web_framework/" rel="nofollow">https://www.reddit.com/r/golang/comments/4a8yit/is_this_the_fastest_go_web_framework/</a></p> <p>I wouldn&#39;t go near your code in a million years because you simply don&#39;t listen to advice, try to mislead people and then insult anyone who points this out.</p> <p>Good luck with your framework.</p></pre>karnd01: <pre><p>Totally agree @CaptaincCodeman and kataras or not, posting blatant lies in my post just proves how ignorant he is.</p></pre>gocoder: <pre><p>Who am I? can you run the benchmarks first and after tell me lier? I am new gopher I dont know many people yet!</p></pre>ar1819: <pre><p>Iris is built on top of fasthttp. While its nice to see other http server implementations, it&#39;s not a fair comparison. Caching routes can lead to resources usage spiking under heavy loaded environment.</p></pre>missipi: <pre><p>Why is this removed? I just follow the link from an article</p></pre>gocoder: <pre><p>What you mean, I can see it</p></pre>gocoder: <pre><p>Hello, yesterday I did a comparison of the web frameworks written in go, the results are controversially. I though that the http-router is the faster but it&#39;s not (?) . The winner seems to be a framework called &#39;Iris&#39; I didn&#39;t knew it until yesterday, second is the framework &#39;Gin&#39; and the http-router is third. My github fork of the <a href="https://github.com/julienschmidt/go-http-routing-benchmark/" rel="nofollow">https://github.com/julienschmidt/go-http-routing-benchmark/</a> is here: <a href="https://github.com/goc0der/go-http-routing-benchmark/" rel="nofollow">https://github.com/goc0der/go-http-routing-benchmark/</a> . Take a look and let&#39;s discuss it.</p></pre>missipi: <pre><p>Ok now I can see it thanks!!</p></pre>

入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889

1299 次点击  
加入收藏 微博
暂无回复
添加一条新回复 (您需要 登录 后才能回复 没有账号 ?)
  • 请尽量让自己的回复能够对别人有帮助
  • 支持 Markdown 格式, **粗体**、~~删除线~~、`单行代码`
  • 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
  • 图片支持拖拽、截图粘贴等方式上传