HCP namespace access protocols are categorized as either cloud protocols or noncloud protocols. The cloud protocols are the REST and S3 compatible APIs. The noncloud protocols are WebDAV, CIFS, NFS, and SMTP.
Protocol optimization improves namespace ingest performance. You can optimize namespaces for all protocols, which provides balanced performance across both cloud protocols and noncloud protocols. Alternatively, you can optimize namespaces for cloud protocols only. Cloud-only optimization improves the ingest rate of namespaces using cloud protocols. Cloud protocols, themselves, are further optimized for improved ingest performance.
A namespace that is optimized only for cloud protocols is said to be cloud optimized. Clients can use only cloud protocols to access cloud-optimized namespaces. For clients to use noncloud protocols to access a namespace, the namespace must be optimized for all protocols.
Only cloud-optimized namespaces support the following features.
- Multipart uploads
- Management of multipart objects
- Erasure coding as protection type
- Unbalanced directory usage
You can change the protocol optimization setting for a namespace from optimized only for cloud protocols to optimized for all protocols only if the namespace does not contain any objects. You can change the setting from optimized for all protocols to optimized only for cloud protocols only if no noncloud protocols are enabled for the namespace.
The default protocol optimization setting for new namespaces is set by the HCP system administrator.
Directory usage defines how the objects are stored within the HCP and it allows the user to choose an approach that best matches their data use patterns.
HCP namespaces can use either balanced or unbalanced directory usage. You can configure this setting at the time of creating a namespace and cannot modify later. Balanced directory usage is selected by default. This type of directory usage requires a well distributed directory structure to avoid hot spotting and to ensure maximized performance. This setting can be applied to namespaces optimized for cloud protocols as well as for those optimized for all protocols.
With unbalanced directory usage, you do not need to know how the applications ingest data or ensure that the objects are distributed across a diverse directory structure. Unbalanced directory usage setting can only be applied to namespaces that are optimized only for cloud protocols.