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
Poor performance at new database libs. #586
Comments
@rrguardo can you provide a sample code to reproduce this issue? |
@anandology Just now read the message, will provide the code in next 24-48 hours. |
Was working in distinct scripts to test the problem and until now, I am not able to replicate it locally in ubuntu OS using similar services (gevent StreamServer). Part of the team believe that problem could be at online servers libs that use FreeBSD. We are yet researching and busy with other tasks. |
Close due to no sample code to reproduce the issue. Feel free to reopen with sample code. |
This old libs combinations works perfect:
If the database pool is enable in threaded (greenlets) services, the database libs works perfect, the service is able to process huge amount of request and connections without delays. The redis default cache pool usually fail before the database pool at those libs.
But with new libs like below, the database pool become slow, even with small service loads we can observe more than 2 seconds delays at database libs and with normal load more than 30 seconds delay at pool processing queries:
mysqlclient get the best performance but yet we observe some bottleneck at db libs that was not present at old libs. (database pool maxconnections apparently is not working, maybe it is not compatible with webpy+dbutils combination)
The text was updated successfully, but these errors were encountered: