Skip to content

Commit d310467

Browse files
pwsegstayseesong
andauthored
Update src/engage/audiences/linked-audiences-limits.md
Co-authored-by: stayseesong <[email protected]>
1 parent a1f985e commit d310467

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/engage/audiences/linked-audiences-limits.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ To get the best performance from Linked Audiences at scale, Segment recommends s
4646

4747
Most workloads running on a dedicated cluster should complete within 60 minutes per sync cycle. Staying under this threshold helps keep audiences fresh and aligned with downstream activation schedules.
4848

49-
Segment has tested Linked Audiences at enterprise scale with over 30 audiences running concurrently, each targeting millions of entities. However, actual performance and cost will vary based on how your Data Graph is structured, how many audiences you run at once, and how frequently they sync. Complex joins, deep relationships, and high concurrency can all increase query time and warehouse usage.
49+
Segment has tested Linked Audiences at enterprise scale with over 30 audiences running concurrently, each targeting millions of entities. However, actual performance and cost varies based on how your Data Graph is structured, how many audiences you run at once, and how frequently they sync. Complex joins, deep relationships, and high concurrency can all increase query time and warehouse usage.
5050

5151
To improve performance and manage compute costs, follow these best practices:
5252

0 commit comments

Comments
 (0)