CodSpeed Performance Report

Merging #9671 will not alter performance

_{Comparing race_safe_waiter (72c1cba) with master (5b654d5)}

Summary

✅ 13 untouched benchmarks

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.65%. Comparing base (5b654d5) to head (72c1cba).
Report is 585 commits behind head on master.

✅ All tests successful. No failed tests found.

@@           Coverage Diff            @@
##           master    #9671    +/-   ##
========================================
  Coverage   98.65%   98.65%            
========================================
  Files         116      116            
  Lines       35482    35594   +112     
  Branches     4211     4221    +10     
========================================
+ Hits        35003    35116   +113     
  Misses        321      321            
+ Partials      158      157     -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

#9670 No longer reproducible with these changes .. but now we can go over the limit.

Previously it was over-enforcing. Now its under-enforcing

The core problem is we have three sources of truth for limits and there is no synchronization between them

self._acquired, self._acquired_per_host, self._waiters

Any await after calling self._available_connections invalidates it because it could change after that

This is turning out to be really hard to fix with the current design

Still a tiny perf regression in _get from calling it more often

Testing looks good, and it looks like we aren't regressing performance now

Backport to 3.10: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 37d9fe6 on top of patchback/backports/3.10/37d9fe68387e3672604ff5b183f48538bca34f16/pr-9671

Backporting merged PR #9671 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.10/37d9fe68387e3672604ff5b183f48538bca34f16/pr-9671 upstream/3.10

4. Now, cherry-pick PR Refactor connection waiters to be cancellation safe #9671 contents into that branch:

   $ git cherry-pick -x 37d9fe68387e3672604ff5b183f48538bca34f16

   If it'll yell at you with something like fatal: Commit 37d9fe68387e3672604ff5b183f48538bca34f16 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 37d9fe68387e3672604ff5b183f48538bca34f16

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Refactor connection waiters to be cancellation safe #9671 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/37d9fe68387e3672604ff5b183f48538bca34f16/pr-9671

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

Backport to 3.11: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 37d9fe6 on top of patchback/backports/3.11/37d9fe68387e3672604ff5b183f48538bca34f16/pr-9671

Backporting merged PR #9671 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.11/37d9fe68387e3672604ff5b183f48538bca34f16/pr-9671 upstream/3.11

4. Now, cherry-pick PR Refactor connection waiters to be cancellation safe #9671 contents into that branch:

   $ git cherry-pick -x 37d9fe68387e3672604ff5b183f48538bca34f16

   If it'll yell at you with something like fatal: Commit 37d9fe68387e3672604ff5b183f48538bca34f16 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 37d9fe68387e3672604ff5b183f48538bca34f16

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Refactor connection waiters to be cancellation safe #9671 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/37d9fe68387e3672604ff5b183f48538bca34f16/pr-9671

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.