-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qh3 performance benchmark example #63
Comments
I have been trying to push/pull higher bandwidth through qh3 .. I suspect I can speed things up with a custom reader but right now i am just processing quic_event_received and end up copying event data and buffered data more than would be ideal.. however this py-spy output seems to show the qh3 layer is consuming the most cpu ... this is single threaded on a Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz and the consuming side is almost at 100% cpu. I am running with 4 quic streams and only getting around 256Mbps over loopback. Much less than possible/expected. Thank you for any thoughts or requests for additional data |
this is py-spy speedscope capture for my publisher and subscriber can be viewed here: https://speedscope.app |
I'll see what I can do to improve the bottlenecks. regards, |
another observation is that when i run my publisher (primarily calling create_wt_stream() send_stream_data() transmit() ), the cpu use steadily increases over time. I have been looking for leaks with memray, but nothing obvious yet.. There is definitely something getting slower over time which makes me think some kind of leak or increasingly inefficient search(?)
memray-flamegraph-pub_example.py.47978.html.txt (note: need to download and rename .html) I wonder if I am not closing my streams cleanly?
|
This is a feature request but I imagine would also be useful as part of the project ci/cd process. To see if any changes help or hurt end to end performance.
The text was updated successfully, but these errors were encountered: