-
Notifications
You must be signed in to change notification settings - Fork 380
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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. | ||
|
@@ -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. | ||
stayseesong marked this conversation as resolved.
Show resolved
Hide resolved
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.