User guides and documentation for Native Object Storage (NOS) is available at https://docs.teradata.com/. These documents, such as the Native Object Store Getting Started Guide, contain practical guides and recommendations for working with data sets in object stores using NOS.
In addition to this guidance, the following table provides specific recommendations to be considered when using NOS with the Dell ECS Object Storage solution on Vantage on VMware (VoV) platforms.
NOS Component | Description | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOS Adapter | Configure the NOS adapters on the VoV VMs with customer supplied IPs and associated subnet that enables connectivity to Dell ECS Object Storage load balancers and nodes. | ||||||||||||||||||
NOS Network | Configure the NOS network as routable to ensure NOS traffic from the VoV VMs can be successfully transmitted to the Dell ECS Object Storage. | ||||||||||||||||||
DBS Control Settings | Configure the following NOS settings:
|
||||||||||||||||||
NOS File Format | While CSV, JSON, and Parquet are all completely supported external file formats, Teradata recommends using Parquet (with SNAPPY), where possible, to achieve the best possible NOS throughput. | ||||||||||||||||||
Object Size | NOS supports up to 16 MiB objects. Optimal performance with Dell ECS Object Storage can be achieved by leveraging objects at least 8 MiB in size. | ||||||||||||||||||
NOS Sessions | As NOS workloads can be CPU intensive (particularly on READ operations), keep the number of NOS sessions to 2 or less to avoid impacts to the database (for non-NOS workloads). | ||||||||||||||||||
NOS Performance Scaling | NOS performance to Dell ECS Object Storage scales as a function of the number of TPA nodes (running NOS), until the network or object storage solution itself becomes fully saturated. | ||||||||||||||||||
NOS S3 Connections | Each NOS session creates client connections equivalent to the total number of AMPs. The number of active connections should always stay under cluster size rate limit. |