License usage and capacities
- View License Usage Dashboard
- This permission lets you view the capacity home.
- Manage Sandboxes
- This permission lets you edit your capacity allocations.
In ÃÛ¶¹ÊÓƵ Experience Platform, capacities let you know if your organization has exceeded any of your guardrails and gives you information on how to fix these issues.
For more information about guardrails in Experience Platform, please read the Real-Time CDP guardrails overview.
Capacity behavior behavior
Currently, Capacity supports the following services:
- Streaming segmentation
- Streaming ingestion
Within these services, the following guardrails are tracked:
- The maximum number of streaming audiences is 500
- Of these 500 streaming audiences, the maximum number of edge audiences is 150
- The maximum combined throughput for streaming segmentation is 1500 records per second (rps)
The audience capacity is at a sandbox level. This means that, for every sandbox you have in your organization, you can have 500 streaming audiences, of which 150 of those can be edge audiences.
The throughput capacity is at an organization level and can be distributed to your individual sandboxes. For example, with the 1500 rps for streaming segmentation throughput, you can set your production sandbox to be at 1350 rps and your development sandbox to be at 150 rps.
Experience Platform calculates the sandbox’s throughput in 15 minute rolling intervals. This throughput is measured in real-time, with the data refreshing every 60 seconds.
If your usage reaches 80% and 90% of your licensed capacity, Experience Platform will issue an alert, notifying that you are reaching the maximum of your specified capacity. You can modify the settings to customize the capacity percentage to receive the alert or remove the alert entirely.
If your usage goes to above 100% of your licensed capacity, you will be considered in breach of your capacity. At this point, you will experience performance latency, and your service level targets (SLTs) will not be guaranteed.
Access access
To access the Capacity overview, select License usage followed by Capacity.
The Capacity overview page is displayed, showing information including a history of alerts as well as details of your organization’s capacities.
Alert history alert-history
The Alert history section displays a list of the most recent capacity breaches within your organization.
To view a full history of the alerts for your organization, select the
Capacity details capacity-details
The Capacity details section outlines information about your organization’s capacities. In this section, you can filter per sandbox and change the lookback period.
Currently, this displays capacity information about streaming throughput, streaming audiences, and edge audiences.
Streaming throughput streaming-throughput
The streaming throughput section displays information about the streaming throughput throughout your organization’s sandboxes. The streaming throughput value measures the combined peak inbound events per second for streaming ingestion into Profile service.
You can select the individual sandbox to see a more detailed view of the sandbox’s streaming throughput.
The Streaming throughput details page is displayed. You can see a graph that displays the request throughput compared to the capacity limit, a list of the sandboxes and their throughputs, as well as a button to allocate your organization’s capacities.
To update the organization’s streaming throughput capacities, select Allocate capacities.
The allocation page appears. On this page, you can set your capacities for your different sandboxes. The sum of all the capacities must equal to the organization’s capacity total.
After updating the capacity allocations, select Save to finish the updates. Please note, it may take up to 10 minutes for the changes to be reflected on your organization.
Audience count audience-count
The Streaming audience count and Edge audience count sections display the number of streaming and edge audiences within the sandbox as well as the maximum number of streaming and edge audiences allowed within the sandbox.
Streaming throughput best practices suggestions
You can resolve your streaming throughput violations by adopting one of the following recommendations:
- Increase the allocated capacity for the sandbox.
- Identify high throughput dataflows in the monitoring dashboard and apply throttling or filtering against these dataflows if needed.
- Optimize your ingestion by using batch ingestion for lower latency use cases.
Additionally, you can look at your dataflows and see if you can optimize your data strategy.
Ingest only data that is required for your use cases. Ensure that you filter out unnecessary data.
- ÃÛ¶¹ÊÓƵ Analytics: Use row-level filtering to optimize your data intake.
- Sources: Use the Flow Service API to filter row-level data for supported sources like Snowflake and Google BigQuery. Edge datastream : Configure dynamic datastreams to perform row-level filtering of traffic coming in from WebSDK.
Frequently asked questions faq
The following section outlines frequently asked questions about the capabilities of Capacity.
Can I have a maximum combined throughput limit that sums up to less than my target maximum?
What happens if I exceed my maximum capacities?
This depends on which capacity is exceeded.
Currently, if you exceed the maximum number of allowed audiences, your excessive audiences will not be affected. However, the ability to create new audiences may be restricted in the future.
If you exceed your streaming throughput, you will experience performance latency in your ingestion and segmentation.
Why should I adhere to my maximum capacities?
Working within your maximum capacities ensures your data remains consistent and keeps your data integrity intact.
You ensure consistent performance during peak events, avoiding technical issues that could adversely affect system performance and impact your downstream customer experiences, ultimately improving your data hygiene and overall system performance.
What are best practices to manage streaming segmentation throughput?
To best manage your streaming segmentation throughput, you should evaluate your datasets to ensure they are prioritizing data necessary for personalization.
If real-time processing is not required, you should use batch ingestion instead of streaming ingestion.