Skip to content
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

Connection Pool Lock Performance #39

Open
wuttem opened this issue Aug 20, 2018 · 0 comments
Open

Connection Pool Lock Performance #39

wuttem opened this issue Aug 20, 2018 · 0 comments
Labels
api: bigtable Issues related to the Bigtable API. type: question Request for information or clarification. Not an issue.

Comments

@wuttem
Copy link

wuttem commented Aug 20, 2018

Is there any reason why the ConnectionPool of this Library is locked so that every Bigtable Connection in it can only be used once ? If i understand correct, the Bigtable Connection itself is thread safe and may be used by more than one thread at a time:
googleapis/google-cloud-python#3272
I have a case where a have more worker threads than connections in the pool and i suspect the locking to cause performance issues if threads are waiting on a connection from the pool.

@tseaver tseaver added the type: question Request for information or clarification. Not an issue. label Aug 20, 2018
@meredithslota meredithslota added the api: bigtable Issues related to the Bigtable API. label Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigtable Issues related to the Bigtable API. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

3 participants