Quota description
Three kinds of SDS quotas: Table quantity quota, tablespace quota, and table read/write quotas.
Table quantity quota
Table quantity quota is the limit of the number of tables a user can have. That is how many tables each user can have at the same time. The initial quota for the number of tables is 100.
Tablespace quota
Tablespace quota refers to the amount of data (in bytes) that can be stored in user's table. User is given a total tablespace quota, which can be allocated to each table according to needs. User's initial total tablespace quota is 1G.
Table read/write quotas
Quotas for table read/write are determined by calculation of the size of record data unit. Capacity unit is 1KB. The quotas are divided into the following types:
Default read/write quotas for primary cluster
Default read/write quotas of primary cluster are for user’s table in primary cluster. System guarantees the number of capacity unit records that can be read and written per second. Each user account has a quota pool, which can be used for quota allocation for tables by demand. User’s initial quota pool size is 200.
Default cluster read/write quotas
Function has the same amount of read/write quotas as default master cluster's. If no explicit specifications set at time of building table, by default, read/write quotas will be the same as master cluster’s.
Maximum excessive read/write quotas for primary cluster
If excessive quotas are set larger than the read/write quotas of default primary cluster, at times the system is idle, it allows read/write quotas to exceed that of default primary cluster, but the maximum read/write capacity per second will not go beyond this value. Note: Some systems cannot guarantee successful allocation when read/write quotas are set larger than that of default primary cluster. If no explicit specifications set at time of building table, by default, read/write quotas will be 1.5 times of master cluster’s.
Maximum excessive read/write quotas for standby cluster
Function has the same amount of maximum excessive read/write quotas as default master cluster's. If no explicit specifications set at time of building table, by default, read/write quotas will be 1.5 times of master cluster’s.
Example of table read/write quotas
The following examples are in the main cluster. Only write quotas are discussed. Read quotas are similar, and no indexes are examined.
Application needs to write 10 records per second to a table in SDS. Each record is less than 1 KB, and write quota from default master cluster of 10 is needed.
Application needs to write 10 records per second to a table in SDS. Each record is less than 2.5 KB, and write quota from default master cluster of 30 is needed.
A table needs only 100 of write quota most of the time. Burst traffic can rise and push it to 150. If system is idle and maximum excessive write quota for table of primary cluster is more than 150, then this burst of traffic can be supported. If system at the time is busy, the excess quota of 50 will not be guaranteed.
Write quota of default primary cluster for a table is 100, and the maximum excessive write quota of primary cluster is 150. If 200 capacity units are written per second, even if the system is idle, it can only support writing at most of 150 capacity units per second.
Additional read/write quota consumption for indexed table
When table is being read or written, and it has an index, then additional quota consumption will be generated.
Lazy index
Put operation: If put attribute contains the key attribute of index, each LAZY index will consume extra 1 capacity unit of write quota.
Remove operation: No expired index will be deleted when removing. Index does not consume additional quota.
Scan operation: Additional 1 write capacity unit and 1 read capacity unit are required for scan.
Lazy index
Put operation: If put attribute contains the key attribute or projection attribute of index, each EAGER index will consume extra 1 capacity unit of write quota. If it is a unique index, it will also consume extra 1 capacity unit of read quota.
Remove operation: If deleted attribute contains an indexed key attribute or projection attribute, each EAGER index will consume extra 1 capacity unit of write quota.
Scan operation: When scanning, if index’s key attribute and attributes other than projection attributes are needed to be read, each record will consume extra 1 capacity unit of read quota.
Immutable index
Put operation: If put attribute contains the key attribute of index, each LAZY index will consume extra 1 capacity unit of write quota.
Remove operation: If deleted attribute contains an indexed key attribute, each IMMUTABLE index will consume extra 1 capacity unit of write quota.
Scan operation: When scanning, if index’s key attribute and attributes other than projection attributes are needed to be read, each record will consume extra 1 capacity unit of read quota.
Additional read/write quota consumption from CAS
Put and delete operations: With conditions set, consume extra read quota worth 1 capacity unit
Increment operation: Consume a read quota of 1 capacity unit and a write quota of 1 capacity unit.
If more quota needed, you can contact us, so we can adjust it for you.