Skip to content

Commit 57fecfc

Browse files
authored
Merge pull request #95682 from felipepessoto/patch-1
Document event count limit
2 parents 1a280d9 + f1559a8 commit 57fecfc

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/time-series-insights/concepts-streaming-ingress-throughput-limits.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,8 @@ In general, ingress rates are viewed as the factor of the number of devices that
2929

3030
* **Number of devices** × **Event emission frequency** × **Size of each event**.
3131

32-
By default, Azure Time Series Insights Gen2 can ingest incoming data at a rate of **up to 1 megabyte per second (MBps) per Azure Time Series Insights Gen2 environment**. There are additional limitations [per hub partition](./concepts-streaming-ingress-throughput-limits.md#hub-partitions-and-per-partition-limits).
32+
By default, Azure Time Series Insights Gen2 can ingest incoming data at a rate of **up to 1 megabyte per second (MBps) or 1000 events stored per second per Azure Time Series Insights Gen2 environment**. There are additional limitations [per hub partition](./concepts-streaming-ingress-throughput-limits.md#hub-partitions-and-per-partition-limits). Depending on how you've modeled your data, arrays of objects can be split into multiple events stored: [How to know if my array of objects will produce multiple events
33+
](./concepts-json-flattening-escaping-rules#how-to-know-if-my-array-of-objects-will-produce-multiple-events).
3334

3435
> [!TIP]
3536
>
@@ -65,7 +66,8 @@ For Event Hubs partitioning best practices, review [How many partitions do I nee
6566
6667
Whether you're creating a new hub for your Azure Time Series Insights Gen2 environment or using an existing one, you'll need to calculate your per partition ingestion rate to determine if it's within the limits.
6768

68-
Azure Time Series Insights Gen2 currently has a general **per partition limit of 0.5 MBps**.
69+
Azure Time Series Insights Gen2 currently has a general **per partition limit of 0.5 MBps or 500 events stored per second**. Depending on how you've modeled your data, arrays of objects can be split into multiple events stored: [How to know if my array of objects will produce multiple events
70+
](./concepts-json-flattening-escaping-rules#how-to-know-if-my-array-of-objects-will-produce-multiple-events).
6971

7072
### IoT Hub-specific considerations
7173

0 commit comments

Comments
 (0)