Skip to main content
NetApp Knowledge Base

Storage aggregate object-store profiler displays 256KB GET failures

  1. Last updated
  2. Save as PDF
Views:
330
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • FabricPool
  • ONTAP S3
  • Quality of Service (QoS)

Issue

After testing the performance with the storage aggregate object-store profiler start command, 256KB GET failures are seen:
 
Cluster-01::> storage aggregate object-store profiler show
Object store config name: ontap_s3_netapp5_local
Node name: Node-01
Status: Done. Failed to delete all objects of bin-UUID:00000000-0000-0000-0000-000000000000
Start time: 2/15/2022 14:49:14
 
 
Op Size Total Failed Latency(ms) Throughput
min max avg
-------------------------------------------------------------------------------
PUT 4MB 2500 0 41 3987 418 475.3MB
GET 4KB 341982 0 7 4954 107 29.62MB
GET 8KB 341967 0 2 6250 130 59.24MB
GET 32KB 341972 0 1 9048 127 237.0MB
GET 256KB 85228 83 1 10018 222 471.8MB
5 entries were displayed.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.