https://old.reddit.com/r/golang/comments/b481q7/a_warning_about_githubcomkatarasiris/ (archive)

iris author continues to edit issues and ban users that point out legal or technical problems with his framework. Go community in general shuns the project for all the continued wrongdoings of the author.

The lib's README claims to be the fastest and links to https://github.com/the-benchmarker/web-frameworks as proof. But when someone pointed out the very linked benchmark says otherwise, the issue was deleted and the user banned from https://github.com/kataras/iris/.

I suggest that iris should be removed from https://github.com/the-benchmarker/web-frameworks since giving it any exposition is just a waste of everyone's time. After so many years of community backlash the author still hasn't learned and can't even respect the very benchmark project he links on his repo.

Hi,

This PR aims to implements (or check) whole CPU usage, it closes #69

This feature COULD be :

• SO_REUSEPORT via spawn/fork

• a custom implementation

• ...

• [x] nim

  • [x] jester

• [x] elixir

  • [x] plug
  • [x] phoenix

• [x] go

  • [x] fasthttprouter
  • [x] violetear
  • [x] kami
  • [x] gorilla-mux
  • [x] gin
  • [x] chi
  • [x] beego
  • [x] gf
  • [x] echo

• [ ] kotlin

  • [ ] ktor

• [ ] swift

  • [ ] kitura
  • [ ] perfect
  • [ ] vapor

• [x] php

  • [x] symfony
  • [x] zend-framework
  • [x] laravel
  • [x] lumen
  • [x] zend-expressive
  • [x] slim

• [ ] scala

  • [x] akkahttp
  • [x] http4s

• [ x] rust

  • [ ] iron
  • [x] gotham
  • [ ] rocket
  • [ ] actix-web
  • [ ] nickel

• [ ] objc

  • [ ] criollo

• [x] python

  • [x] aiohttp
  • [x] tornado
  • [x] flask
  • [x] django
  • [x] vibora
  • [x] molten
  • [x] hug
  • [x] fastapi
  • [x] quart
  • [x] responder
  • [x] cyclone
  • [x] bocadillo
  • [x] sanic
  • [x] bottle
  • [x] falcon
  • [x] japronto
  • [x] starlette

• [] crystal

  • [x] onyx
  • [x] orion
  • [ ] athena
  • [x] kemal
  • [x] router.cr
  • [x] spider-gazelle
  • [x] lucky
  • [x] amber

• [ ] csharp

  • [ ] aspnetcore

• [x] node

  • [x] polka
  • [x] restana
  • [x] turbo_polka
  • [x] restify
  • [x] foxify
  • [x] express
  • [x] koa
  • [x] rayo
  • [x] muneem
  • [x] fastify
  • [x] hapi

• [x] java

  • [x] act

• [x] cpp

  • [x] evhtp

• [x] ruby

  • [x] hanami
  • [x] rails
  • [x] flame
  • [x] agoo
  • [x] roda
  • [x] sinatra
  • [x] rack-routing
  • [x] cuba

• [ ] c

  • [x] agoo-c
  • [ ] kore

Regards,

Hi,

As a standard tool, we decide to go on wrk.

This benchmarking tool give us a lot of useful informations.

• Global (per scenario / route to test)
  • Duration
  • Number of requests
  • Total bytes received
  • Number of error (socket / read / write / http / timeout)
  • Number of
• Latency
  • Minimum
  • Maximum
  • Average
  • Standard deviation
• Percentile
  • 50
  • 90
  • 99
  • 99.999

ALL informations SHOULD be displayed, but COULD be used to determine ranks (I mean display is OK, but to keep it simple now we SHOULD only use 1 metric to rank).

@OvermindDL1 What do you think about talking only the number of requests-per-second to rank ?

Regards,

Hi @tbrand,

Some services (which are in the marketplace) are more usable (due to github permissions) to use / enable on some group project.

For example, using https://dependabot.com (to manage dependency) COULD only be done either on my fork or on a group project.

Do you mind if I create a group in order to migrate this project ?

It will be very helpful for maintainers.

Regards,

Hi,

This PR run all frameworks into docker containers.

In order to build and run :

shards install && shards build --release --no-debug # <- build all tools
bin/neph # <- build and run all containers
bin/benchmarker # <- run benchmarks

@tbrand I have disabled crillo, since only on OS X.

Regards,

Hi,

Results are actually computed from a local docker. This decision has been taken to facilitate frameworks addition, but mess-up the results. The final goal of this tool is to present closest to (as we can) production results.

The idea behind this PR is to run on a cloud, for this DigitalOcean

Frameworks :

• C
  • [ ] agoo-c
  • [ ] kore
• C++
  • [ ] evhtp
• C#
  • [ ] asp NET core
• Crystal
  • [ ] amber
  • [ ] athena
  • [ ] kemal
  • [ ] lucky
  • [ ] onyx
  • [ ] orion
  • [ ] raze
  • [ ] router.cr
  • [ ] spider-gazelle
• Elixir
  • [ ] phoenix
  • [ ] plug
• Go
  • [ ] beego
  • [ ] chi
  • [ ] Eecho
  • [ ] fasthttprouter
  • [ ] gf
  • [ ] gin
  • [ ] gorilla-mux
  • [ ] gorouter
  • [ ] kami
  • [ ] violetear
• Java
  • [ ] act
  • [ ] sprint-boot
• Kotlin
  • [ ] ktor
• Nim
  • [ ] jester
• Node
  • [ ] express
  • [ ] fastify
  • [ ] foxify
  • [ ] hapi
  • [ ] koa
  • [ ] muneem
  • [ ] polka
  • [ ] rayo
  • [ ] restana
  • [ ] restify
  • [ ] turbo_polka
• Objective C
  • [ ] Criollo
• PHP
  • [ ] laravel
  • [ ] lumen
  • [ ] slim
  • [ ] symfony
  • [ ] zend-expressive
  • [ ] zend-framework
• Python
  • [ ] aiohttp
  • [ ] bocadillo
  • [ ] bottle
  • [ ] cyclone
  • [ ] django
  • [ ] falcon
  • [ ] fastapi
  • [ ] flask
  • [ ] hug
  • [ ] japronto
  • [ ] masonite
  • [ ] molten
  • [ ] quart
  • [ ] responder
  • [ ] sanic
  • [ ] starlette
  • [ ] tornado
  • [ ] vibora
• Ruby
  • [ ] agoo
  • [ ] cuba
  • [ ] flame
  • [ ] hanami
  • [ ] rack-routing
  • [ ] rails
  • [ ] roda
  • [ ] sinatra
• Rust
  • [ ] actix-web
  • [ ] gotham
  • [ ] iron
  • [ ] nickel
  • [ ] rocket
• Scala
  • [ ] akkahttp
  • [ ] http4s
• Swift
  • [ ] kitura
  • [ ] kitura-nio
  • [ ] perfect
  • [ ] vapor

Display comprehensive results

... has to be defined ...

Regards,

So my new server is setup, nice and empty and ready to run tests on (for now), so I'm playing with it. :-)

8-core (16-hyperthreads), 3.7ghz, 16gigs ram (for now), etc... etc...

First, the current result sets that are currently built into this git project are not indicative of the actual through-put that a server can sustain as it always tests a simple iteration of command and how fast they complete rather then how long each request takes, the average, the longest a request took, etc... etc...

So I whipped up a quick script to test the statistical parts in far far greater detail than this current git HEAD does, these are the results for a set of servers. I used rust, crystal, go, python, elixir, and node for the servers, mostly because I haven't installed (or figured out how, depending) the rest of the stuff, plus these run the fastest overall. I did have an issue with server_python_japronto, it refused to run... The server_python_flask did not install flask, I had to do that manually, that should be fixed... japronto does not seem to be in pip, so it remained missing. I'll post the results here as I get them (it outputs markdown format so the posts will be a run with a bit of description at the top of each).

Hi @Fenny,

You inform me that the is some stories about uWebSocket @see https://medium.com/@rockstudillo/beware-of-uwebsockets-js-b51c92cac83f

Thanks for notification :stuck_out_tongue:

/cc @alexhultman @dalisoft @aadityataparia @jkyberneees

The idea here is to determine if uWebSocket based frameworks could be listed here

Personally, I have no idea of how npm registry works

Hi, I had some time to check the benchmark of Laravel and Flask on my computer i7-7600U, 2.8x4 GHz and here is the result: https://gist.github.com/doanguyen/a81cccb4e884c63422e2c5ae3e846d18

It shows the total different outcomes, Laravel serves only 87 req/s and Flask at best is 8506 req/s, I did some research and it looks similar to some other benchmarks, for instance, https://medium.com/@mihaigeorge.c/web-rest-api-benchmark-on-a-real-life-application-ebb743a5d7a3

Do you have any clue what's happening?

Added frameworks:

• Phoenix
• Plug (using :plug_cowboy)
• cowboy (using the standard :cowboy API)
• cowboy_stream (using :cowboy low-level Stream API)

I am not 100 % familiar with this project so I tried to replicate settings from other languages/frameworks but I am not sure I did it correctly.

Closes #2197 Closes #1353 Closes #89

Hello,

As our community is growing fast (at least I hope, so :stuck_out_tongue_winking_eye:), it will be useful to choose a code of conduct, at least to be warm to new comers

@tbrand @aichholzer @OvermindDL1 any thoughts ?

Regards,

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | hyperf/framework (source) | require | major | ~2.2.0 -> ~3.0.0 |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | fastify (source) | ~4.10.0 -> ~4.11.0 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | com.hexagonkt:http_server_netty_epoll (source) | 2.3.0 -> 2.3.1 | | | | | | com.hexagonkt:http_server_netty (source) | 2.3.0 -> 2.3.1 | | | | | | com.hexagonkt:http_server_jetty (source) | 2.3.0 -> 2.3.1 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| | node | final | major | 16.19-alpine -> 19.3-alpine |

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.