Skip to content

Update rETL limit to be more descriptive #7781

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/engage/audiences/linked-audiences-limits.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ If you have a non-standard or high volume usage plan, you have unique Linked Aud

Name | Limit | Details
---- | ----- | --------
RETL row limit | 150 million | The audience compute fails if the total output exceeds the limit.
RETL row limit | 150 million | The audience compute fails if the total output exceeds the limit. This limit is approximately the sum of the total linked audience profile membership count and the total number of entity relationships for the profiles in the audience.
RETL column limit | 500 columns | The audience compute fails if the number of columns exceeds the limit.
Global concurrent audience runs | 5 total within any given space | New audience runs are queued once the limit is reached and will start execution once prior audience runs complete. If you need a higher global concurrent audience runs limit, contact [[email protected]](mailto:[email protected]){:target="_blank"}.
Event Size | 32 KB | Segment doesn’t emit messages for profiles whose total related entities and enrichments exceed the limit.
Expand All @@ -56,4 +56,4 @@ To improve performance and manage compute costs, follow these best practices:
- Run on a dedicated warehouse cluster if you're operating at enterprise scale.
- Stagger audience sync schedules to reduce concurrency and avoid bottlenecks.

Following this guidance will help you keep audience syncs running efficiently even as your scale grows.
Following this guidance will help you keep audience syncs running efficiently even as your scale grows.