Stream Management instance limits
- Last UpdatedSep 10, 2026
- 2 minute read
This topic describes the enforced limits on resources and operations for a single instance of Stream Management.
Instance limits
The following limits apply to the total number of resources that can exist within a single Stream Management instance.
|
Resource |
Description |
Limit |
|---|---|---|
|
Streams per instance |
The total number of streams that can exist in a single Stream Management instance. |
320,000 |
|
Stream types per instance |
The total number of stream types that can be defined in a single Stream Management instance. |
500 |
|
Stream views per instance |
The total number of stream views that can be defined in a single Stream Management instance. |
No enforced limit |
|
Data points per instance |
The total number of data points that can be stored across all streams in the instance. |
No enforced limit |
Request limits
The following limits apply to individual API requests. Requests that exceed these limits return an HTTP error.
|
Operation |
Description |
Limit |
HTTP error when exceeded |
|---|---|---|---|
|
Bulk delete streams |
The number of streams that can be permanently deleted in a single request. |
1 stream per request |
413 Request Entity Too Large |
|
Bulk read streams |
The number of stream definitions that can be read in a single request. |
1,000 streams per request |
413 Request Entity Too Large |
|
Data points returned per read request |
The maximum number of data points that can be returned across all streams in a single read request. |
2,500,000 |
400 Bad Request |
|
Summary intervals per summaries request |
The maximum number of summary intervals that can be calculated in a single summaries request. |
100,000 intervals |
400 Bad Request |
|
Bulk security tag update |
The number of streams whose security tags can be updated in a single request. |
500 streams per request |
413 Request Entity Too Large |
|
Concurrent requests |
The maximum number of requests that can be processed simultaneously. |
200 requests |
429 Too Many Requests |
Resource definition limits
The following limits apply to the character length of individual property values when creating or updating Stream Management objects.
|
Property |
Description |
Limit |
|---|---|---|
|
id (stream, stream type, stream view) |
The unique identifier for the object. |
250 characters |
|
name |
The display name for the object. |
250 characters |
|
description |
A human-readable description of the object. |
2,000 characters |
|
Tags per stream |
The number of tags that can be associated with a stream. |
No enforced limit |
|
Metadata payload per stream |
The total size of all metadata key-value pairs associated with a stream. |
256 KB |
|
Compressed record size |
The maximum size of an individual compressed data record. |
300,000,000 bytes (โ286 MB) |
|
Type property nesting depth |
The maximum depth of nested properties in an SDS type. Third-level properties must use primitive types. |
3 layers |
1: For id and name, both the character limit and the UTF-8 byte limit are enforced concurrently; whichever limit is reached first constrains the value. This distinction matters for non-ASCII text: characters outside the ASCII range (including accented Latin characters, non-Latin scripts, and emojis) can each consume 2โ4 bytes in UTF-8, so a value can hit the byte limit well before reaching 250 characters.
Account-specific limits
To learn about the specific limits that apply to your account, contact AVEVA Support.