--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev+unsubscribe@googlegroups.com.
To post to this group, send email to mongo...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-dev/234fc774-e41f-4d0c-9887-06b891aa41f7%40googlegroups.com.
Hi -This feature is under active development right now.We have already transitioned the server to use ASIO based networking in the upcoming 3.6 release. However, this is still in a synchronous, thread-per-connection model. The 3.6 release will also include an experimental and unsupported version of an asynchronous ASIO based networking layer which will multiplex client connections over an adaptive pool of worker threads. In this model, if you have 40k connections but only 100 of those connections are concurrently active, the server will only have approximately 100 worker threads. We will be working to make the adaptive model fully supported, and, if possible, the default, during the next release of MongoDB after 3.6.Thanks,Andrew
On Thu, Nov 16, 2017 at 2:57 AM, <wolfk...@gmail.com> wrote:
Sorry, I mean an issue or plan to use asio to manage client->server connections
在 2017年11月16日星期四 UTC+8下午3:27:59,wolfk...@gmail.com写道:Hi official guys.Currently, connections between client and mongos/mongod is in the model of one-thread-per-connection.We may have 40k connections connected to one mongos, and 40k threads, each serve a connection. it is unacceptable and hard to say if system trash is related to too many connections.Is there a plan, or an issue, tracking this problem ?thanks!
--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev...@googlegroups.com.
To post to this group, send email to mongo...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-dev.
Awesome!If so, I just need to backport 3.6's code into my company's 3.2 branch, my company currently is using 3.2
I was wondering to implement this myself.Btw, say something unrelated, mongo's community(more precisely, mongo company) has lower acceptance to community's code contribution, compared to mariadb's community.
在 2017年11月16日星期四 UTC+8下午10:49:21,acm写道:Hi -This feature is under active development right now.We have already transitioned the server to use ASIO based networking in the upcoming 3.6 release. However, this is still in a synchronous, thread-per-connection model. The 3.6 release will also include an experimental and unsupported version of an asynchronous ASIO based networking layer which will multiplex client connections over an adaptive pool of worker threads. In this model, if you have 40k connections but only 100 of those connections are concurrently active, the server will only have approximately 100 worker threads. We will be working to make the adaptive model fully supported, and, if possible, the default, during the next release of MongoDB after 3.6.Thanks,AndrewOn Thu, Nov 16, 2017 at 2:57 AM, <wolfk...@gmail.com> wrote:Sorry, I mean an issue or plan to use asio to manage client->server connections--
在 2017年11月16日星期四 UTC+8下午3:27:59,wolfk...@gmail.com写道:Hi official guys.Currently, connections between client and mongos/mongod is in the model of one-thread-per-connection.We may have 40k connections connected to one mongos, and 40k threads, each serve a connection. it is unacceptable and hard to say if system trash is related to too many connections.Is there a plan, or an issue, tracking this problem ?thanks!
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev...@googlegroups.com.
To post to this group, send email to mongo...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-dev/234fc774-e41f-4d0c-9887-06b891aa41f7%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev+unsubscribe@googlegroups.com.
To post to this group, send email to mongo...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-dev/5feabfb0-0dba-4f65-ac97-f5a1d11c8b8b%40googlegroups.com.
Hi -This feature is under active development right now.We have already transitioned the server to use ASIO based networking in the upcoming 3.6 release. However, this is still in a synchronous, thread-per-connection model. The 3.6 release will also include an experimental and unsupported version of an asynchronous ASIO based networking layer which will multiplex client connections over an adaptive pool of worker threads. In this model, if you have 40k connections but only 100 of those connections are concurrently active, the server will only have approximately 100 worker threads. We will be working to make the adaptive model fully supported, and, if possible, the default, during the next release of MongoDB after 3.6.Thanks,Andrew
On Thu, Nov 16, 2017 at 2:57 AM, <wolfk...@gmail.com> wrote:
Sorry, I mean an issue or plan to use asio to manage client->server connections
在 2017年11月16日星期四 UTC+8下午3:27:59,wolfk...@gmail.com写道:Hi official guys.Currently, connections between client and mongos/mongod is in the model of one-thread-per-connection.We may have 40k connections connected to one mongos, and 40k threads, each serve a connection. it is unacceptable and hard to say if system trash is related to too many connections.Is there a plan, or an issue, tracking this problem ?thanks!
--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev...@googlegroups.com.
To post to this group, send email to mongo...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-dev.