Skip to content

Commit 3d00148

Browse files
vladfalonGitHub Enterprise
authored andcommitted
Merge branch 'main' into PLAT-255819-Update-dataset-export-section-about-schedules
2 parents 0a6c023 + 66e0c76 commit 3d00148

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

help/segmentation/methods/edge-segmentation.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,9 @@ Edge segmentation is the ability to evaluate segment definitions in Adobe Experi
1111
>
1212
> The edge data will be stored in an edge server location closest to where it was collected. This data may also be stored in a location other than the one designated as the hub (or principal) Adobe Experience Platform data center.
1313
>
14-
> Additionally, the edge segmentation engine will only honor requests on the edge where there is **one** primary marked identity, which is consistent with non-edge-based primary identities.
14+
> The edge segmentation engine will only honor requests on the edge where there is **one** primary marked identity, which is consistent with non-edge-based primary identities.
15+
>
16+
> Additionally, since edge segmentation is designed to process requests at scale, edge servers dynamically load the metadata required. As a result, the very first calls may experience "cold-start" latency regardless of the sandbox type. During this window, the first few evaluation calls may result in a timeout. A brief pre-warm burst or realistic load helps eliminate false-positive test failures.
1517
1618
## Edge segmentation query types {#query-types}
1719

0 commit comments

Comments
 (0)