vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQs for limits and maximum values 

Have a question about CDN and limits or maximum? Review these frequently asked questions, which provide answers to common inquiries.



 Is there a maximum value for Time To Live? A minimum? 

The maximum value for Time To Live is 2,147,483,647 seconds, which equates to roughly 68 years! The minimum value is 0 seconds.





 Is there a limit on the number of origin and TTL entries? 

Yes, the combined limit is 75 entries per CDN.





 What is the largest file size that can be delivered through Akamai CDN? 

Attempts to retrieve or deliver files larger than 1.8 GB receive a 403 Access Forbidden response for the default performance configuration. If Large File Optimization is enabled, file downloads up to 320 GB are possible.





 How long do configuration changes take before they become active on the Akamai side? 

You can expect changes to become active on Akamai in 10 minutes.





 What's the rate limit for a multiple file purge? 

For a multiple file purge, there is a limit on the number of files that can be purged at a given time. The limiting algorithm that is used for the sustained rate and burstiness follows the Token Bucket model, where there is one fixed-capacity bucket that is applied for all the purge paths in your account. The total number of tokens in the bucket represents the number of paths that can be purged in a burst.

In the following table, X-RateLimit-Purge-Paths-Limit-Burst represents the number of tokens that the bucket can hold. The initial token bucket is full. Tokens are constantly added to this bucket based on the sustained rate (X-RateLimit-Purge-Paths-Limit-Per-Second). However, if the bucket is full, no more tokens can be added.

When a multiple file purge request is made, the remaining number of tokens is checked against the number of file paths. The paths bucket must contain enough tokens to satisfy all of the paths in the request. If there are enough tokens in the purge bucket, the tokens are removed from the bucket and the request is accepted.
ibmcloud project delete --id ID
<-- <section "id="section-project-delete-cli-options" "> --> Command options --id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! ! +$/.
<-- </section "id="section-project-delete-cli-options" "> --><-- <section "id="section-project-delete-examples" "> --> Example ibmcloud project delete --id=exampleString
<-- </section "id="section-project-delete-examples" "> --><-- </section "id="section-project-cli-delete-command" "> --><-- <section "id="section-project-cli-config-create-command" "> --> ibmcloud project config-create Add a new configuration to a project. ibmcloud project config-create --project-id PROJECT-ID --name NAME --locator-id LOCATOR-ID --labels LABELS] --description DESCRIPTION] --authorizations AUTHORIZATIONS] --compliance-profile COMPLIANCE-PROFILE] --input INPUT] --setting SETTING] !
<-- <section "id="section-project-config-create-cli-options" "> --> Command options --project-id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] +$/.
--name (string): The name of the configuration. Required.
The maximum length is 64 characters. The minimum length is 1 character. The value must match regular expression /^a-zA-Z0-9]a-zA-Z0-9-_ ] !!$/.
"updated_at" : "2023-02-22T19:51:23.253Z",
"href" : "/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd"
} ] ! ! ! !
}
<-- </section "id="section-project-configs-cli-output" "> --><-- </section "id="section-project-cli-configs-command" "> --><-- <section "id="section-project-cli-config-get-command" "> --> ibmcloud project config-get Returns the specified project configuration in a specific project. ibmcloud project config-get --project-id PROJECT-ID --id ID
<-- <section "id="section-project-config-get-cli-options" "> --> Command options --project-id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] +$/.
--id (string): The unique config ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! +$/.
<-- </section "id="section-project-config-get-cli-options" "> --><-- <section "id="section-project-config-get-examples" "> --> Example ibmcloud project config-get --project-id=exampleString --id=exampleString
Options: id, name, created, size_bytes
-h, --help Show this message and exit.

Notifications are sent when you reach three different space thresholds – 75 percent, 90 percent, and 95 percent.



* At 75 percent capacity, a warning is sent that snapshot space usage exceeded 75 percent. To remediate, you can manually add space, or delete retained unnecessary snapshots. You can reduce the number of retained snapshots in the schedule. If you reduce the snapshot data or increase the space, the warning system is reset, and no autodeletion occurs.
* At 90 percent capacity, a second warning is sent when snapshot space usage exceeded 90 percent. Like with reaching 75 percent capacity, if you take the necessary actions to decrease the snapshot data or increase the space, the warning system is reset and no autodeletion occurs.
* At 95 percent capacity, a final warning is sent. If no action is taken to bring your space usage under the threshold, automatic deletion starts so that future snapshots can be created. Scheduled snapshots are deleted, starting with the oldest, until usage drops under 95 percent. Snapshots continue to be deleted each time usage exceeds 95 percent until it drops under the threshold. If the space is manually increased or snapshots are manually deleted, the warning is reset, and reissued if the threshold is exceeded again. If no actions are taken, this notification is the only warning that you receive.



If snapshot space usage increases too rapidly, then you might receive one notification before autodeletion of the oldest scheduled snapshot occurs. For example, if usage jumps from 76% to 96% within 15 minutes, you receive one notification about exceeding 75% and one notification about exceeding 95%. The system skips the 90%-exceeded warning.

By default, snapshot warning notifications are enabled for every customer. However, you can choose to disable them. When this feature is disabled, all ticket generation and notifications are stopped. You can disable and enable notifications for the volume at any time.

To check whether the notifications are enabled for the storage volume, use the following command.

 slcli file snapshot-get-notification-status
By using the dp2 profile, you can specify the total IOPS for the file share within the range for a specific file share size, 10 GB (default minimum) to 32,000 GB. You can provision shares with IOPS performance from 100 IOPS (default minimum) to 96,000 IOPS, based on share size. The dp2 profile is based on a block size of 256 KB. Maximum throughput is 1024 MB/s. This profile is backed by solid-state drives (SSDs).

Table 2 shows the available IOPS ranges, based on share size.



Table 2. dp2 file share profile IOPS and capacity ranges

 Share size (GB) IOPS range (IOPS) 

 10-39 100-1,000 
 40-79 100-2,000 
 80-99 100-4,000 
 100-499 100-6,000 
 500-999 100-10,000 
 1,000-1,999 100-20,000 
 2,000-3,999 200-40,000 
 4,000-7,999 300-40,000 
 8,000-15,999 500-64,000 
 16,000-32,000 2,000-96,000 







 Previous version file storage profiles 



 IOPS tiers 

Existing file shares can be based on IOPS tiers that you selected when you created the file share. Table 3 describes the IOPS performance for the IOPS tier profile.



Table 3. IOPS tier profiles and performance levels for each tier

 IOPS Tier Workload Share size (GB) Max IOPS (IOPS) 

 3 IOPS/GB General-purpose workloads 10-32,000 96,000 
 5 IOPS/GB High I/O intensity workloads 10-9,600 48,000 
 10 IOPS/GB Demanding storage workloads 10-4,800 48,000 



The total maximum IOPS is rounded up to the next multiple of 10 when the IOPS calculation results in IOPS less than or equal to 48,000 IOPS.
physpages system Total number of RAM pages used by processes 
 numfile system Number of open files 
 numflock system Number of file locks 
 numpty system Number of pseudo-terminals 
 numsiginfo system Number of siginfo structures 
 dcachesize system Total size of dentry and inode structures locked in memory 
 numiptent system Number of NETFILTER (IP packet filtering) entries 
 cpulimit cpu Limit on CPU consumption 
 diskinodes disk Disk inode (filesystem object) quota 
 quotatime disk Amount of time, in seconds that the disk can exceed it's quota limits. 
 quotaugidlimit disk Limit on the number of uid and gid accounting entries 



Table 1. SLM parameter descriptions

You can access VzLinuxUBCMgmt.pdf or view it in HTML, within PIM on your server by going to: Management > Support > Downloads > Management of UBC Resources Administrator's Guide

For more information about UBC, see, [OpenVZ Virtuozzo Containers, Category: UBC ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://wiki.openvz.org/Category:UBC). Note: Not everything in OpenVZ is the same as Virtuozzo.
"name": "type"
}
}
}
<-- </ol> --><-- </section "id="section-migrating_endpoint" "> --><-- <section "id="section-rest_producer_limitations" "> --> Limitations When you use the REST producer API, a limitation exists on the maximum size of the message that is passed as request payload. The maximum size of the payload is limited to 64 K.<-- </section "id="section-rest_producer_limitations" "> --><-- <section "id="section-rest_api_reference" "> --> API reference <-- <ul> --> * For more information about the API reference of v2 endpoint, see the Event Streams REST Producer v2 API reference]] . * For more information about the API reference of existing endpoint, see the Event Streams REST Producer API reference]Event Streams REST Producer API reference 1] ! ! ! ! !
-c, --new-size INTEGER New Size of file volume in GB. If no size
is given, the original size of volume is
used.
Potential Sizes: [20, 40, 80, 100,
250, 500, 1000, 2000, 4000, 8000, 12000]
Minimum: [the original size of the volume]
-i, --new-iops INTEGER Performance Storage IOPS, between 100 and 6000
in multiples of 100 [only for performance
volumes] If no IOPS value is specified, the
original IOPS value of the volume will be
used.
Requirements: [If original IOPS/GB
for the volume is less than 0.3, new IOPS/GB
must also be less than 0.3. If original
IOPS/GB for the volume is greater than or
equal to 0.3, new IOPS/GB for the volume must
also be greater than or equal to 0.3.]
-t, --new-tier [0.25|2|4|10] Endurance Storage Tier (IOPS per GB) [only for
endurance volumes] If no tier is specified,
the original tier of the volume will be
used.
Requirements: [If original IOPS/GB
for the volume is 0.25, new IOPS/GB for the
volume must also be 0.25. If original IOPS/GB
for the volume is greater than 0.25, new
IOPS/GB for the volume must also be greater
than 0.25.]
-h, --help Show this message and exit.

Unmount, then mount the modified volume, so the OS can recognize the extra storage space.





 Resizing storage with the API 

You can increase your storage capacity by using an API call to the SOAP web service. The following sample API calls can be called from the scripting language of your choice.

For more information about the SLAPI, see the [SLDN](http://sldn.softlayer.com/reference/softlayerapi).



* Increase capacity on a Performance storage volume.
X-Clv-Request-Id: c8be10e7-94c4-4c03-9960-6f242b42424d
Accept-Ranges: bytes
Server: Cleversafe/3.9.1.114
X-Clv-S3-Version: 2.5
ETag: "765ba3df36cf24e49f67fc6f689dfc6e-2"
Content-Type: application/xml
Content-Length: 364

<CompleteMultipartUploadResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Location>http://s3.us.cloud-object-storage.appdomain.cloud/zopse/multipart-object-123</Location>
<Bucket>some-bucket</Bucket>
<Key>multipart-object-123</Key>
<ETag>"765ba3df36cf24e49f67fc6f689dfc6e-2"</ETag>
</CompleteMultipartUploadResult>

--------------------





 Abort incomplete multipart uploads 

A DELETE request issued to an object with query parameter uploadId deletes all unfinished parts of a multipart upload.

Not all operations are supported in Satellite environments. For details, see [supported Satellite APIs](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-apis-cos-satellite)

Syntax

DELETE https://{endpoint}/{bucket-name}/{object-name}?uploadId={uploadId}= path style
DELETE https://{bucket-name}.{endpoint}/{object-name}?uploadId={uploadId}= virtual host style

Example request
Required.

The maximum length is 36 characters. The minimum length is 7 characters. The value must match regular expression /^([0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}|default)$/.





 Example 

ibmcloud secrets-manager secret-group --id=d898bb90-82f6-4d61-b5cc-b079b66cfa76





 Example output 

Example of SecretGroup response

{
"created_at" : "2020-10-05T21:33:11Z",
"description" : "Extended description for this group.",
"id" : "d898bb90-82f6-4d61-b5cc-b079b66cfa76",
"name" : "my-secret-group",
"updated_at" : "2020-11-25T22:13:10Z",
"created_by" : "iam-ServiceId-e4a2f0a4-3c76-4bef-b1f2-fbeae11c0f21"
}







 ibmcloud secrets-manager secret-group-update 

Update the properties of an existing secret group, such as its name or description.

ibmcloud secrets-manager secret-group-update --id ID [--name NAME] [--description DESCRIPTION]



 Command options 

--id (string)
: The ID of the secret group. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/.

--secret-group-patch (generic map)
This can help prevent the service calls from timing out.



* Flag: --page-size SIZE



* Optional: The total NUMBER of items to return in the command's output.



* Flag: --max-items NUMBER



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT













 List in-progress multipart uploads 



* Action: Lists in-progress multipart uploads.
* Usage:ibmcloud cos multipart-uploads --bucket BUCKET_NAME [--delimiter DELIMITER] [--encoding-type METHOD] [--prefix PREFIX] [--key-marker value] [--upload-id-marker value] [--page-size SIZE] [--max-items NUMBER] [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME



* Optional: A DELIMITER is a character that you use to group keys.



* Flag: --delimiter DELIMITER



* Optional: Requests to encode the object keys in the response and specifies the encoding METHOD to use.



* Flag: --encoding-type METHOD



* Optional: Limits the response to keys that begin with the specified PREFIX.



* Flag: --prefix PREFIX



* Optional: Together with upload-id-marker, this parameter specifies the multipart upload after which listing should begin.



* Flag: --key-marker value



* Optional: Together with key-marker, specifies the multipart upload after which listing should begin. If key-marker is not specified, the upload-id-marker parameter is ignored.



* Flag: --upload-id-marker value



* Optional: The SIZE of each page to get in the service call. This does not affect the number of items returned in the command's output. Setting a smaller page size results in more calls to the service, retrieving fewer items in each call. This can help prevent the service calls from timing out. (default: 1000).



* Flag: --page-size SIZE
The number of files a volume can contain is determined by how many inodes it has. An inode is a data structure that contains information about files. Volumes have both private and public inodes. Public inodes are used for files that are visible to the customer and private inodes are used for files that are used internally by the storage system. The maximum number of files setting is 2 billion. However, this maximum value can be configured only with volumes of 7.8 TB or larger. The maximum number of inodes that can be configured on a volume is calculated by taking the total allocated volume size in KB and dividing it by 4. Any volume of 7.8 TB or larger reaches the maximum limit at 2,040,109,451 inodes.



Table comparison
Table 1 shows the maximum number of inodes that are allowed based on the volume size. Volume sizes are in the left column. The numbers of inodes (files and directories) are on the right.

 Volume Size Inodes 

 20 GB 5,242,880 
 40 GB 10,485,760 
 80 GB 20,971,520 
 100 GB 26,214,400 
 500 GB 131,072,000 
 1 TB 268,435,456 
 4 TB 1,073,741,824 
 8 TB 2,040,109,451 
 12 TB 2,040,109,451 







 I ordered a File Storage for Classic volume in the wrong data center. Is it possible to move or migrate it to another data center? 

You need to order new File Storage for Classic in the right data center, and then cancel the File Storage for Classic device that you ordered in the incorrect location. When the volume is canceled, the request is followed by a 24-hour reclaim wait period. You can still see the volume in the console during those 24 hours. Billing for the volume stops immediately. When the reclaim period expires, the data is destroyed and the volume is removed from the console, too.





 Measuring IOPS 

IOPS is measured based on a load profile of 16-KB blocks with random 50 percent reads and 50 percent writes. Workloads that differ from this profile might experience poor performance.
The maximum length is 255 characters. The minimum length is 0 characters. The value must match regular expression /[!a-zA-Z 0-9-_/.?:'";,+=@$%^&()]/.

[--instance-id INSTANCE-ID] (string)
: Unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

[--sources SOURCES] ([TopicCreateSourcesItem[]](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-cli-plugin-event-notifications-clien-cli-topic-example-schema))
: The list of sources.
* Example:



* The following example shows the format of the TopicCreateSourcesItem[] object.

[
{
"id" : "exampleString",
"rules" :
{
"enabled" : true,
"event_type_filter" : "$.",
"notification_filter" : "exampleString"
}
]
}
]
* The following example shows the format of the TopicUpdateSourcesItem[] object.

[
{
"id" : "exampleString",
"rules" :
{
"enabled" : true,
"event_type_filter" : "exampleString",
"notification_filter" : "exampleString",
"rule_id" : "exampleString"
}
]
}
]









 ibmcloud event-notifications topic list 



* Action: List all Topic.
As described in the [Beta VPC API](https://cloud.ibm.com/apidocs/vpc-beta) reference [versioning](https://cloud.ibm.com/apidocs/vpc-betaapi-versioning-beta) policy, support for older versions of the beta API is limited to 45 days. Therefore, beta API requests must specify a version query parameter date value within the last 45 days. You must also provide generation parameter and specify generation=2. For more information, see Generation in the [Virtual Private Cloud API reference](https://cloud.ibm.com/apidocs/vpcapi-generation-parameter).

Make a PATCH /shares/{id} request and specify the ID of the file share for which you want to increase the size.

This request example expands a file share with a capacity of 50 GB to 2500 GB for a 5 IOPS/GB profile.

curl -X PATCH "$vpc_api_endpoint/v1/shares/$share_id?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: $iam_token" -d '{
"size": 2500
}'

The file share status shows updating while the capacity is increased. The current capacity is shown while it's updating.

{
"created_at": "2023-07-11T23:31:59Z",
"crn": "crn:[...]",
"encryption": "provider_managed",
"href": "$vpc_api_endpoint/v1/shares/199d78ec-b971-4a5c-a904-8f37ae710c63",
"id": "199d78ec-b971-4a5c-a904-8f37ae710c63",
"iops": 12500,
"lifecycle_state": "updating",
"name": "share-name1",
.
.
"size": 2500,
.
"href": "$vpc_api_endpoint/v1/share/profiles/tier-5iops",
"name": "tier-5iops",
"resource_type": "share_profile"
}
]
}
Show more





 How block size affects file share performance 

IOPS is based on a 16 KB block size for all profiles, with a 50-50 read/write random workload. Each 16 KB of data that is read or written counts as one read/write operation. A single write of less than 16 KB counts as a single write operation.

Baseline throughput is determined by the amount of IOPS multiplied by the 16 KB block size. The higher the IOPS you specify, the higher the throughput. Maximum throughput is 1536 MBps.

The block size that you choose for I/O from your application directly impacts storage performance. If the block size is smaller than the block size used by the profile to calculate the share’s bandwidth limit, the IOPS limit is reached before the throughput limit. Conversely, if the block size is larger, the throughput limit is reached before the IOPS limit.

Table 5 provides some examples of how block size and IOPS affect the throughput, calculated average I/O block size x IOPS = Throughput in MBps.



Table 5. How block size and IOPS affect throughput

 Block Size (KB) IOPS Throughput (MBps) 

 4 1000 4¹ 
 8 1000 8¹ 
 16 1000 16 
 32 500 16 
 64 250 16 
 128 128 16 
 512 32 16 
 1024 16 16 



¹If your cap is 1000 IOPS or 16 KB block size, the throughput caps at whatever limit is reached first.

Maximum IOPS can still be obtained when you use smaller block sizes, but throughput is less. The following example shows how throughput decreases for smaller block sizes, when max IOPS is maintained.



* 16 KB * 6000 IOPS == 94 MBps
* 8 KB * 6000 IOPS == 47 MBps
* 4 KB * 6000 IOPS == 23 MBps







 Next steps
--configs (ProjectConfigPrototype]]ProjectConfigPrototype] ! ! ): The project configurations. If configurations are not included, the project resource is persisted without this property.
The maximum length is 10000 items. The minimum length is 0 items.

Provide a JSON string option or specify a JSON file to read from by providing a filepath option that begins with a @, e.g. --configs=@path/to/file.json.
<-- </section "id="section-project-create-cli-options" "> --><-- <section "id="section-project-create-examples" "> --> Example ibmcloud project create --resource-group=Default --location=us-south --name=acme-microservice --description='A microservice to deploy on top of ACME infrastructure.'
Size range in gigabytes
: 20-4000 Gi

Hard disk
: SSD

Reclaim policy
: ibmc-block-gold: Delete
: ibmc-block-retain-gold: Retain





 Custom 

Name
: ibmc-block-custom
: ibmc-block-retain-custom

Type
: Performance File system
: ext4

IOPS and size
: Size range in gigabytes / IOPS range in multiples of 100



* 20-39 Gi / 100-1000 IOPS
* 40-79 Gi / 100-2000 IOPS
* 80-99 Gi / 100-4000 IOPS
* 100-499 Gi / 100-6000 IOPS
* 500-999 Gi / 100-10000 IOPS
* 1000-1999 Gi / 100-20000 IOPS
* 2000-2999 Gi / 200-40000 IOPS
* 3000-3999 Gi / 200-48000 IOPS
* 4000-7999 Gi / 300-48000 IOPS
* 8000-9999 Gi / 500-48000 IOPS
* 10000-12000 Gi / 1000-48000 IOPS



Hard disk
: The IOPS to gigabyte ratio determines the type of hard disk that is provisioned. To determine your IOPS to gigabyte ratio, you divide the IOPS by the size of your storage.
: Example: You chose 500Gi of storage with 100 IOPS. Your ratio is 0.2 (100 IOPS/500Gi).
: Overview of hard disk types per ratio:



* Less than or equal to 0.3: SATA
* Greater than 0.3: SSD



Reclaim policy
: ibmc-block-custom: Delete
: ibmc-block-retain-custom: Retain







 Sample customized storage classes 

You can create a customized storage class and use the storage class in your PVC.

IBM Cloud Kubernetes Service provides [pre-defined storage classes](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_storageclass_reference) to provision block storage with a particular tier and configuration.