-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
DNM: Explore performance of adding a Cython WebSocket frame parser #9541
Conversation
CodSpeed Performance ReportMerging #9541 will improve performances by 30.94%Comparing Summary
Benchmarks breakdown
|
❌ 10 Tests Failed:
View the top 3 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
The code is nearly identical. I wonder if a pxd file would make more sense. Then we only have to maintain that and keep it in sync with the python code. |
Maybe move |
It looks like that would work. Would have to move around some code first as So maybe move them all to |
I like that design better because we end up with ~100 lines of cython typing to maintain and the python code is the same and we don't have a copy |
pxd is probably the way to do since the time in |
PXD only approach seems to be more than good enough and has far less maint burden #9543 |
DNM: this is a rough version to check performance
It works out to ~30% faster.... I'm not sure if its worth it or not to have to maintain the parse_frame function twice