Azure Cosmos DB for MongoDB account (RU)の最大同時接続可能数の確認方法について

こんにちは @梅原香オル子さん

Microsoft QAにご連絡いただきありがとうございます。ご懸念を検討し、解決策をご提案いたします。

Hello @Umehara Kaoruko

It sounds like you're trying to figure out how to check the maximum number of simultaneous connections supported by your Azure Cosmos DB for MongoDB account (RU).

Currently, Azure Cosmos DB doesn't explicitly provide a straightforward way to retrieve the maximum simultaneous connection limits through the Azure portal or any direct API calls. However, the connection limits can be influenced by several factors including the provisioned Request Units (RUs) for your database and the configuration of your application itself.

Here are some steps you can take:

Connection Pooling: Ensure that your application is using proper connection pooling settings, as this can directly influence how many concurrent connections can be handled efficiently. Review your MongoDB driver or library documentation for best practices on configuring connection pools.

Request Units (RUs): Monitor your provisioned throughput. The RU consumption for each operation can affect how many connections can be sustained. You might want to increase your RUs temporarily to test how this affects allowed simultaneous connections. This can help you determine the maximum effective load your account can sustain.

Monitor Connections: Enable Diagnostic settings in Azure. This allows you to collect and analyze metrics and logs related to your connections and throughput:

• Navigate to your Cosmos DB account in Azure portal.
  • Go to Diagnostic settings and enable logs and metrics.
    • Use Azure Monitor to track metrics like Total Requests, Throttled Requests, and other relevant statistics which indicate how close you are to your connection limits.
    Testing: You could run a test to gradually increase the number of parallel connections from your application to find the point at which you start seeing throttling (Error 16500 - TooManyRequests).

To get statistics about your current connections or see how many connections you've used historically:

• You can utilize the getLastRequestStatistics command from your MongoDB shell or any client tool (like MongoDB Compass, Robo 3T) you've used to connect.

1. Documentation: You might find it useful to reference the following documentation to get insights on performance optimization and diagnostic settings:
   • Monitor Azure Cosmos DB data by using diagnostic settings
     • Connection and Client Tools
       • Find the request unit charge for operations executed in Azure Cosmos DB for MongoDB

Hope this helps your application’s performance and parallel processing needs! If you have any follow-up questions or need further clarification, feel free to ask!