HCP namespace access protocols are categorized as either cloud protocols or noncloud protocols. The cloud protocols are the HTTP, 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 and the management of multipart objects. Additionally, only cloud-optimized namespaces support erasure coding as their protection type.
To benefit most from optimization, you should increase system memory. Results are most apparent on systems with high object and directory counts. If you want to upgrade system memory, contact your HCP sales representative.
At the system level, the default configuration setting for new namespaces is optimize for all namespace access protocols. You can change this to optimize for cloud protocols only. You can also change all existing namespaces for which no noncloud protocols are enabled to be cloud-optimized.
![]() |
Note: You cannot make protocol optimization changes while an HCP system upgrade is in progress. |
© 2015, 2020 Hitachi Vantara LLC. All rights reserved.