Comments (5)
Agreed! We have very basic websocket perf testing in our benchmarking suite (you can see the output at e.g.: near the bottom of https://github.com/mtrudel/bandit/actions/runs/7838502587), but they're really intended for us to avoid performance regressions on PRs, not as 'absolute' benchmarks. They also expire from GitHub actions after a few months so they're not great to link to.
I did a run of the WS suite against Bandit and Cowboy's branch heads; you can see it here. It's not ideal (most of the charts only relate to HTTP/1 suites and don't even populate for WS), but it's a start.
If you're curious, the implementation of the benchmarking suite is over here
from bandit.
@mtrudel
Yes, I have seen those GitHub actions benchmarking. Well a suggestion would be that, you can maybe combine all of those benchmarks into a Single GitHub Action, which outputs the result artifacts, but not just in a plain CSV fashion, but also as a static website or something, and it deploys that to GitHub pages. Then it would be a good way to link to it, and put in some extras such as graphs and charts.
from bandit.
Yes, I have seen those GitHub actions benchmarking. Well a suggestion would be that, you can maybe combine all of those benchmarks into a Single GitHub Action, which outputs the result artifacts, but not just in a plain CSV fashion, but also as a static website or something, and it deploys that to GitHub pages. Then it would be a good way to link to it, and put in some extras such as graphs and charts.
Sounds great; a PR for this would be very welcome! I personally am not planning to spend any meaningful amounts of time on measurement or project PR for a while (I try to rotate through all of the aspects of the project in turn, and perf just got a big chunk of my time around this time last year).
If you want to take this on, I'd be more than happy to accept the work on a separate PR. In the meantime, I'm going to close this issue for project hygiene reasons. Thanks for the issue!
from bandit.
@mtrudel Sure, no problem. Just so we don't pollute the Issues with discussion, maybe you can open up the discussions section for this repository, so all related talks can be made there.
from bandit.
Yes, I have seen those GitHub actions benchmarking. Well a suggestion would be that, you can maybe combine all of those benchmarks into a Single GitHub Action, which outputs the result artifacts, but not just in a plain CSV fashion, but also as a static website or something, and it deploys that to GitHub pages. Then it would be a good way to link to it, and put in some extras such as graphs and charts.
Sounds great; a PR for this would be very welcome! I personally am not planning to spend any meaningful amounts of time on measurement or project PR for a while (I try to rotate through all of the aspects of the project in turn, and perf just got a big chunk of my time around this time last year).
If you want to take this on, I'd be more than happy to accept the work on a separate PR. In the meantime, I'm going to close this issue for project hygiene reasons. Thanks for the issue!
I have worked on it here: #300
from bandit.
Related Issues (20)
- Server appears to hang after some period of uptime HOT 11
- Increased memory usage after switching from Cowboy to Bandit HOT 31
- gzip compressed requests HOT 5
- Plug.BadRequestError and Plug.TimeoutError HOT 16
- Dealing with "request line read error" HOT 11
- Detailed Benchmark Comparison (not just Cowboy, but Go/Java/etc) HOT 4
- Password for key in SSL HOT 4
- Plug.Conn.chunk does not send the chunk to client HOT 3
- Unknown adapter Bandit.Adapter after update to Bandit 1.4.0 HOT 3
- Content-Length header gets overridden HOT 3
- High Memory usage for DelegatingHandler.init/1 HOT 24
- Missing measurements in telemetry events HOT 6
- Plug.Conn is not closed when user closes the browser's tab (SSE) HOT 14
- High CPU usage HOT 2
- Compression configuration options HOT 1
- Clearing process dictionary breaks on some keys HOT 2
- Bandit + Phoenix LiveView on Safari iOS Fails to Reconnect HOT 2
- More examples in documentation HOT 1
- Otel question HOT 2
- Reproducible: Server hangs on every other request HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bandit.