8000 gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. by alex-kowalczyk · Pull Request #112191 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. #112191

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

Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update Doc/library/asyncio-eventloop.rst
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
  • Loading branch information
kumaraditya303 and willingc authored Jun 24, 2024
commit 751c584194e7e102b35464fb6948a3aafa401870
2 changes: 1 addition & 1 deletion Doc/library/asyncio-eventloop.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1151,7 +1151,7 @@ DNS
Both *getaddrinfo* and *getnameinfo* internally utilize their synchronous
versions through the loop's default thread pool executor.
When this executor is saturated, these methods may experience delays,
which can manifest as "DNS timeouts" in higher-level networking libraries.
which higher-level networking libraries may report as increased timeouts.
To mitigate this, consider using a custom executor for other user tasks,
or setting a default executor with a larger number of workers.

Expand Down
Loading
0