Quotas and limits
This page provides details on the limits that apply to using Cloud Profiler.
Profiler API quotas and limits
The Profiler API quotas place limits on the number of API requests that the Profiler backend can support for a specific Google Cloud project. The quotas include limits on the following:
- Number of new profiler-agent deployments per day.
Number of update requests per minute.
An update request is issued each time a deployment collects a profile type. Deployments that collect two profile types issue twice as many update requests as deployments that collect one profile type.
Number of update requests per day.
Number of list-profiles requests per day.
A list-profiles request can be issued to retrieve the profiles for your existing deployments.
If you exceed a quota, the Profiler backend rejects the API request. For example, assume that the quota for the number of new deployments per day is 75. If 80 new deployments are created in one day, then no profiling data is collected for 5 of the deployments.
As a second example, assume that you have 10 deployments for a service that collects Heap and Wall time profiling. In this case, the quota for the number of update requests per minute must be at least 20:
10 deployments x 2 profile types per deployment x 1 update request per profile type per minute = 20 update requests per minute (on average)
If this quota is less than 20, then some profiles aren't transmitted successfully to the Profiler backend.
Managing your quota
You can view, decrease, and increase your Profiler API quota. For more information about quotas, see Working with quotas:
To view your Profiler API quota and current usage, from the Google Cloud console, go to Quotas:
To limit your view to the Profiler API usage, set the Service menu to select only the Profiler API.
To decrease your Profiler API quota, see Capping usage.
To request an increase in your Profiler API quota, see Request a quota adjustment.
Data retention periods
Data collected by Cloud Profiler is retained for 30 days.