nerdexam
Network_Appliance

NS0-157 · Question #392

A customer has a 4-node cluster. Two nodes have FlashCache and the other two nodes have Flash Pools. The customer is interested in deploying and OLTP application with a workload that consists of an…

The correct answer is A. Place all volumes for the application on the nodes with Flash Pools. For OLTP workloads with extreme small random writes, Flash Pool nodes are the correct choice because Flash Pool SSDs provide a write cache tier, while FlashCache is primarily a read cache.

Performance, Troubleshooting, and Security

Question

A customer has a 4-node cluster. Two nodes have FlashCache and the other two nodes have Flash Pools. The customer is interested in deploying and OLTP application with a workload that consists of an extreme number of small random writes on four LUNs spread across four volumes. What should the customer do to improve performance for the OLTP application?

Options

  • APlace all volumes for the application on the nodes with Flash Pools.
  • BDeploy all volumes for the application on the two nodes with the FlashCache installed.
  • CSplit the volumes between the two nodes with FlashCache and two of the nodes with Flash Pools.
  • DPlace the volume with the highest read load on the Flash Pool nodes and place the other volumes

How the community answered

(26 responses)
  • A
    58% (15)
  • B
    15% (4)
  • C
    19% (5)
  • D
    8% (2)

Why each option

For OLTP workloads with extreme small random writes, Flash Pool nodes are the correct choice because Flash Pool SSDs provide a write cache tier, while FlashCache is primarily a read cache.

APlace all volumes for the application on the nodes with Flash Pools.Correct

Flash Pool hybrid aggregates use SSDs as both a read and write cache tier, meaning small random writes are absorbed by the SSD layer and destaged to spinning disk asynchronously, dramatically reducing write latency for OLTP workloads. FlashCache cards, by contrast, function as an intelligent read cache only and do not accelerate random write operations, making Flash Pool the correct placement for all four write-intensive volumes.

BDeploy all volumes for the application on the two nodes with the FlashCache installed.

FlashCache (Performance Acceleration Module) is a read cache that caches frequently accessed blocks in flash memory on the controller - it does not provide a write caching tier, so it offers no benefit for write-intensive OLTP workloads.

CSplit the volumes between the two nodes with FlashCache and two of the nodes with Flash Pools.

Splitting volumes between FlashCache and Flash Pool nodes gives only half the volumes the benefit of SSD write caching, unnecessarily leaving the FlashCache-hosted volumes without write acceleration.

DPlace the volume with the highest read load on the Flash Pool nodes and place the other volumes

Routing only the highest read-load volume to Flash Pool nodes ignores the stated workload characteristic of extreme random writes across all four volumes, leaving most of the write workload without SSD-backed write caching.

Concept tested: Flash Pool write caching vs FlashCache read caching for OLTP

Source: https://docs.netapp.com/us-en/ontap/concepts/flash-pool-aggregates-concept.html

Topics

#FlashCache#Flash Pool#OLTP#random write performance

Community Discussion

No community discussion yet for this question.

Full NS0-157 Practice