Skip to content

Commit 817b267

Browse files
authored
Merge pull request #110642 from lyrana/update-throttling-info
Update throttling info
2 parents c4c1e50 + e750e87 commit 817b267

File tree

3 files changed

+10
-12
lines changed

3 files changed

+10
-12
lines changed

articles/time-series-insights/time-series-insights-environment-mitigate-latency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ You are most likely to experience latency and throttling when you:
2525
- Add an event source that contains old data that may exceed your allotted ingress rate (Time Series Insights will need to catch up).
2626
- Add more event sources to an environment, resulting in a spike from additional events (which could exceed your environment’s capacity).
2727
- Push large amounts of historical events to an event source, resulting in a lag (Time Series Insights will need to catch up).
28-
- Join reference data with telemetry, resulting in larger event size. From a throttling perspective, an ingressed data packet with a packet size of 32 KB is treated as 32 events, each sized 1 KB. The maximum allowed event size is 32 KB; data packets larger than 32 KB are truncated.
28+
- Join reference data with telemetry, resulting in larger event size. The maximum allowed packet size is 32 KB; data packets larger than 32 KB are truncated.
2929

3030
## Video
3131

articles/time-series-insights/time-series-insights-environment-planning.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -74,9 +74,7 @@ You can adjust retention and toggle between the two modes on the environment’s
7474

7575
### Environment planning
7676

77-
The second area to focus on for planning your Time Series Insights environment is ingress capacity. Ingress capacity is a derivative of the per-minute allocation.
78-
79-
From a throttling perspective, an ingressed data packet that has a packet size of 32 KB is treated as 32 events, each 1 KB in size. The maximum allowed event size is 32 KB. Data packets larger than 32 KB are truncated.
77+
The second area to focus on for planning your Time Series Insights environment is ingress capacity. The daily ingress storage and event capacity is measured per minute, in 1-KB blocks. The maximum allowed packet size is 32 KB. Data packets larger than 32 KB are truncated.
8078

8179
You can increase the capacity of an S1 or S2 SKU to 10 units in a single environment. You can't migrate from an S1 environment to an S2. You can't migrate from an S2 environment to an S1.
8280

includes/time-series-insights-ga-limits.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,27 +15,27 @@ The following summarizes key limits in General Availability.
1515

1616
### SKU ingress rates and capacities
1717

18-
S1 and S2 SKU ingress rates and capacities provide flexibility when configuring a new Time Series Insights environment.
18+
S1 and S2 SKU ingress rates and capacities provide flexibility when configuring a new Time Series Insights environment. Your SKU capacity indicates your daily ingress rate based on number of events or bytes stored, whichever comes first. Note that ingress is measured *per minute*, and **throttling** is applied using the token bucket algorithm. Ingress is measured in 1-KB blocks. For example a 0.8-KB actual event would be measured as one event, and a 2.6-KB event is counted as three events.
1919

2020
| S1 SKU capacity | Ingress rate | Maximum storage capacity
2121
| --- | --- | --- |
22-
| 1 | 1 GB (1 million events) | 30 GB (30 million events) per month |
23-
| 10 | 10 GB (10 million events) | 300 GB (300 million events) per month |
22+
| 1 | 1 GB (1 million events) per day | 30 GB (30 million events) per month |
23+
| 10 | 10 GB (10 million events) per day | 300 GB (300 million events) per month |
2424

2525
| S2 SKU capacity | Ingress rate | Maximum storage capacity
2626
| --- | --- | --- |
27-
| 1 | 10 GB (10 million events) | 300 GB (300 million events) per month |
28-
| 10 | 100 GB (100 million events) | 3 TB (3 billion events) per month |
27+
| 1 | 10 GB (10 million events) per day | 300 GB (300 million events) per month |
28+
| 10 | 100 GB (100 million events) per day | 3 TB (3 billion events) per month |
2929

3030
> [!NOTE]
3131
> Capacities scale linearly, so an S1 SKU with capacity 2 supports 2 GB (2 million) events per day ingress rate and 60 GB (60 million events) per month.
3232
3333
S2 SKU environments support substantially more events per month and have a significantly higher ingress capacity.
3434

35-
| SKU | Event count per month | Event size per month | Event count per minute | Event size per minute |
35+
| SKU | Event count per month | Event count per minute | Event size per minute |
3636
|---------|---------|---------|---------|---------|
37-
| S1 | 30 million | 30 GB | 720 | 720 KB |
38-
|S2 | 300 million | 300 GB | 7,200 | 7,200 KB |
37+
| S1 | 30 million | 720 | 720 KB |
38+
|S2 | 300 million | 7,200 | 7,200 KB |
3939

4040
### Property limits
4141

0 commit comments

Comments
 (0)