-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
'mongodb' client is not honoring the maxPoolSize=XX for the number of client connections. #317
Comments
@allanbank Is this still an issue or does the client initialize once per YCSB run properly? Thanks. |
I will try and check this weekend. |
@manolama , the issue is current implementation of MongoDB adapter is it is using 100 connections by default. Even though "100 connections is enough", it bites when one tries to benchmark with lots of clients (e.g. 500 or 1000) on a multicore machine (e.g. 70 cores). On contrary, What do you think of creating a common property Certain implementations (e.g. Mongo) would just leverage existing implementation (e.g. Having a common property would enable comparison in a controlled environments and it would simplify results comparison. PS. I think it makes sense to use |
'mongodb' client is not honoring the maxPoolSize=XX for the number of client connections. Instead it is opening a connection per YCSB client thread.
The text was updated successfully, but these errors were encountered: