How can i configure mongodb's pool connection for support 1100 threads per seconds?
I tried some configurations like bellow without sucess.
connectionsPerHost = 200
threadsAllowedToBlockForConnectionMultiplier = 5
Can someone help me?
Thanks.
Asked
Active
Viewed 69 times
-1
Stennie
- 63,885
- 14
- 149
- 175
Bernardo Maia
- 99
- 1
- 6
-
Are you sure your computer will even survive that? – Sammaye Jul 26 '15 at 01:46
-
I think yes because my computador works well with 900 threads. – Bernardo Maia Jul 26 '15 at 15:55
-
What are your specific versions of MongoDB Java driver & server? – Stennie Jul 27 '15 at 02:03
-
1Please clarify what you mean by "1100 threads per seconds". It doesn't make sense as written. – jyemin Jul 27 '15 at 13:11
1 Answers
1
It won't.
That number of threads may be prejudicial, there's a lot of techniques to calculate some ideal number, and none of them get even close to 1100. If you're looking to attend a large number of users you should work with server redundancy. You won't get speed because 99.9% (really) of your threads will be locked waiting for a resource become available.
I've worked with java in fast processing, using distributed systems and threads, we used 0mq(tcp alternative) to acelerate communication and get more use of the threads, but we found that moderate number of threads was the ideal (if I remember correctly, 12).
Instead of letting hundreds of threads do the job, try to keep a limited number of workers threads, you won't have more resources anyway. The ideal for this kind of application would be have many servers attending your users.
Pedro Ivan
- 322
- 1
- 14