This page lists the quotas that apply to Pub/Sub Lite.
Pub/Sub Lite enforces a limit of 1,000 Lite subscriptions per Lite topic. You cannot request an increase for the number of Lite subscriptions.
The following quotas apply to each project and location:
|Publishing throughput per zone||64 MiB/s|
|Subscribing throughput per zone||128 MiB/s|
|Storage per zone||10 TiB|
|Reservation throughput per region||128 units|
Requests to increase these quotas up to 5 times will be quickly approved. Order of magnitude increases will usually take a few business days, depending on the request size.
Lite topics store messages in partitions, and each message uses 256 bytes-3.5 MiB of storage. If the message is larger than 256 bytes, then the size of the message is the sum of the following:
- The number of bytes in the encoded message body string
- The number of bytes in the key and value of each attribute
- The number of bytes in the ordering key
- 12 bytes for the event timestamp
For more information about the message format, see the message resource in the Pub/Sub Lite API reference.
The following quotas apply to Pub/Sub Lite requests in each region:
|Administrative read requests per min||600||Getting and listing Lite topics and Lite subscriptions|
|Administrative write requests per min||600||Creating, updating, and deleting Lite topics and Lite subscriptions, or manually changing the offset of a committed cursor.|
|Message stats computation requests per min||600||Computing backlog statistics|
|Head cursor computation requests per min||600||Computing the current head cursor|
These quotas apply to each Google Cloud Console project and are shared across all applications and IP addresses using that project. Increases to these quotas will be approved if the requesting project is using a significant amount of partitions.
If you want to increase any of your quotas for Pub/Sub Lite, you can use the Google Cloud Console to request a quota increase. For details, see Requesting higher quota.