-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Improve performance of fetching the content-length for web responses #9448
Conversation
Co-authored-by: Sam Bull <git@sambull.org>
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #9448 +/- ##
==========================================
- Coverage 98.58% 98.58% -0.01%
==========================================
Files 107 107
Lines 35012 35010 -2
Branches 4146 4145 -1
==========================================
- Hits 34517 34515 -2
Misses 330 330
Partials 165 165
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Backport to 3.10: 💚 backport PR created✅ Backport PR branch: Backported as #9449 🤖 @patchback |
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #9450 🤖 @patchback |
…e content-length for web responses (#9449) Co-authored-by: J. Nick Koston <nick@koston.org>
…e content-length for web responses (#9450) Co-authored-by: J. Nick Koston <nick@koston.org>
What do these changes do?
Small performance improvement for web responses ~1.8% speed up from avoiding all the multiple super calls
ref #2779 #2779 (comment)
Are there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no