Open AgarwalPragy opened 1 year ago
The current docs page only reports Requests per second, which is definitely a very important metric for web frameworks. However, latency is also very important!
The current benchmarks suite already reports the latency details - it will be really nice if the results can be included in the docs.
Why not just let the reader run the benchmarks themselves?
No response
[!NOTE] While we are open for sponsoring on GitHub Sponsors and OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship. Check out all issues funded or available for funding on our Polar.sh Litestar dashboard If you would like to see an issue prioritized, make a pledge towards it! We receive the pledge once the issue is completed & verified This, along with engagement in the community, helps us know which features are a priority to our users.
[!NOTE] While we are open for sponsoring on GitHub Sponsors and OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh Litestar dashboard
@peterschutt do you have the results file from the latest run? If yes, I will be happy to convert that into a graph and update the docs :)
Sorry @AgarwalPragy I don't.
Summary
The current docs page only reports Requests per second, which is definitely a very important metric for web frameworks. However, latency is also very important!
The current benchmarks suite already reports the latency details - it will be really nice if the results can be included in the docs.
Why not just let the reader run the benchmarks themselves?
Basic Example
No response
Drawbacks and Impact
No response
Unresolved questions
No response