From c92c4690c65cb9f313a170d3882f563822cd69a7 Mon Sep 17 00:00:00 2001 From: Elio Damaggio Date: Fri, 18 Mar 2016 10:16:22 -0700 Subject: [PATCH 1/2] IoT Hub - clarify device connection throttle #sign-off --- articles/iot-hub/iot-hub-devguide.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/articles/iot-hub/iot-hub-devguide.md b/articles/iot-hub/iot-hub-devguide.md index bdea866b969..597ce0b0628 100644 --- a/articles/iot-hub/iot-hub-devguide.md +++ b/articles/iot-hub/iot-hub-devguide.md @@ -576,6 +576,11 @@ The following is the list of enforced throttles. Values refer to an individual h | Cloud-to-device sends | 100/min/unit | | Cloud-to-device receives | 1000/min/unit | +It is important to clarify that the *device connections* throttle governs the rate at which new device connections can be established with an IoT hub, and not the maximum number of simultaneously connected devices. The throttle is dependent on the number of units that are provisioned for the hub. + +For instance, if you buy a single S1 unit, you get a throttle of 100 connections per sec. This means that in order to connect 100.000 devices it would take at least 1000 secs ~ 16mins. You can, however, have as many simultaneously connected devices as you have in your device identity registry. + + **Note**. At any given time, it is possible to increase quotas or throttle limits by increasing the number of provisioned units in an IoT hub. **Important**: Identity registry operations are intended for run-time use in device management and provisioning scenarios. Reading or updating large number of device identities is supported through [import/export jobs](#importexport). From e6776b07ddb7bd6b0d7fac9f640daad524877d0a Mon Sep 17 00:00:00 2001 From: Elio Damaggio Date: Tue, 22 Mar 2016 10:00:32 -0700 Subject: [PATCH 2/2] Update iot-hub-devguide.md --- articles/iot-hub/iot-hub-devguide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/iot-hub/iot-hub-devguide.md b/articles/iot-hub/iot-hub-devguide.md index 597ce0b0628..963baaf5c63 100644 --- a/articles/iot-hub/iot-hub-devguide.md +++ b/articles/iot-hub/iot-hub-devguide.md @@ -578,7 +578,7 @@ The following is the list of enforced throttles. Values refer to an individual h It is important to clarify that the *device connections* throttle governs the rate at which new device connections can be established with an IoT hub, and not the maximum number of simultaneously connected devices. The throttle is dependent on the number of units that are provisioned for the hub. -For instance, if you buy a single S1 unit, you get a throttle of 100 connections per sec. This means that in order to connect 100.000 devices it would take at least 1000 secs ~ 16mins. You can, however, have as many simultaneously connected devices as you have in your device identity registry. +For example, if you buy a single S1 unit you get a throttle of 100 connections per second. This means that to connect 100,000 devices it takes at least 1000 seconds (approximately 16 minutes). However, you can have as many simultaneously connected devices as you have devices registered in your device identity registry. **Note**. At any given time, it is possible to increase quotas or throttle limits by increasing the number of provisioned units in an IoT hub.