You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful if your readme would contain a section about the benchmark scope.
In it's current state the scope is very minimal (it seems like the benchmark only benches a simple get request with no database connection or other meaningful backend work).
So I propose to either disclaim that no real world scenario is used, or explicitly state which scenarios you are benchmarking.
Thank you.
The text was updated successfully, but these errors were encountered:
You are totally right. The scenario here is not very meaningful, I mean is not very relative to anything in real life. The idea is to define a way to reflect the widest majority on real life workload, but this is planned.
Thanks for your reply, I honestly applaud your effort so far and wish you good luck going forward. Just had a look at the-benchmarker/web-frameworks#3958 and it sounds reasonable, just far beyond my spare time :-)
It would be helpful if your readme would contain a section about the benchmark scope.
In it's current state the scope is very minimal (it seems like the benchmark only benches a simple get request with no database connection or other meaningful backend work).
So I propose to either disclaim that no real world scenario is used, or explicitly state which scenarios you are benchmarking.
Thank you.
The text was updated successfully, but these errors were encountered: