You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the aiohttp uses standard logging for tracking the library activity, But the logging module is threading safe, namely it contains many acquire and release lock operations. will this cause a bad performance to aiohttp in high concurrency environment?
The text was updated successfully, but these errors were encountered:
GitMate.io thinks the contributor most likely able to help you is @asvetlov.
Possibly related issues are #2956 (Enable logging when aiohttp.web is used as a program), #843 (ImportError: No module named 'aiohttp'), #474 (Does aiohttp support awss3?), #2963 (aiohttp doesn't use system settings), and #1850 (how to specify log request format in aiohttp).
I noticed that the aiohttp uses standard logging for tracking the library activity, But the logging module is threading safe, namely it contains many acquire and release lock operations. will this cause a bad performance to aiohttp in high concurrency environment?
The text was updated successfully, but these errors were encountered: