HCP namespace access protocols are categorized as either cloud protocols or noncloud protocols. The cloud protocols are the REST, S3 compatible, and HSwift 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 multipart uploads. Additionally, only cloud-optimized namespaces can be configured to allow erasure coding.
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.