Sun Storage 7000 Unified Storage System: Vertical Outlier Elimination for Analytics broken down by latency shows less operations when set to 0% (Doc ID 1553160.1)

Last updated on SEPTEMBER 11, 2015

Applies to:

Sun ZFS Storage 7120 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Sun Storage 7210 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7110 Unified Storage System - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Disk Storage ZFS Storage Appliance

Analytics, when configured with vertical outlier elimination, shows incorrect data. If no elimination is set, there are less operations and no latency is shown. If elimination is set to 1% or 5%, there are many operations with latency.

Normally, the 0% elimination should include all the peaks, and all the latencies. The problem here is that there are shown more operations with latency when setting the elimination, when in fact the elimination should exclude some of the operations.

Thus, there should always be more operations when the elimination is set to 0 rather than when it is set to 1% or 5%

Object: Problem has been noticed on the following analytics:
  -> Protocol: NFSv4 operations per second broken down by latency
  -> Protocol: SMB operations per second broken down by latency

System: Sun Storage Unified Systems

AK version: 2011.1.4.2

 

In BUI, the following outputs have been observed for the analytics "NFSv4 operations per second broken down by latency".

It can be seen that using 0% elimination, there are less iops. More precise information is provided when using 1% or 5% elimination.

- with 0% elimination (all the iops) there are:
             -> 2 ops with 26.1 ms latency
             -> 6 ops with 13.0 ms latency
             -> 1859 with 0 us latency

- with 0.1% elimination there are:
             -> 2 ops with 28.9 ms latency
             -> 1 ops with 16.7 ms latency
             -> 1 ops with 15.2 ms latency
             -> 4 ops with 13.7 ms latency
             -> 2 ops with 12.2 ms latency
             -> 2 ops with 10.7 ms latency
             -> 4 ops with 9.13 ms latency
             -> 1 ops with 7.61 ms latency
             -> 3 ops with 6.09 ms latency
             -> 1 ops with 4.57 ms latency
             -> 8 ops with 1.52 ms latency
             -> 1838 ops with 0 us latency

- with 1% elimination there are:
             -> 1 ops with 2.96 ms latency
             -> 1 ops with 2.61 ms latency
             -> 1 ops with 2.44 ms latency
             -> 1 ops with 2.26 ms latency
             -> 1 ops with 2.09 ms latency
             -> 1 ops with 1.91 ms latency
             -> 1 ops with 1.74 ms latency
             -> 1 ops with 1.57 ms latency
             -> 2 ops with 1.39 ms latency
             -> 2 ops with 1.22 ms latency
             -> 5 ops with 1.04 ms latency
             -> 6 ops with 870 us latency
             -> 27 ops with 696 us latency
             -> 97 ops with 522 us latency
             -> 552 ops with 348 us latency
             -> 23 ops with 174 us latency
             -> 1124 with 0 us latency

- with 5% elimination there are:
             -> 2 ops with 957 us latency
             -> 1 ops with 914 us latency
             -> 2 ops with 870 us latency
             -> 5 ops with 827 us latency
             -> 5 ops with 783 us latency
             -> 9 ops with 740 us latency
             -> 8 ops with 696 us latency
             -> 9 ops with 653 us latency
             -> 24 ops with 690 us latency
             -> 25 ops with 566 us latency
             -> 39 ops with 522 us latency
             -> 104 ops with 479 us latency
             -> 202 ops with 435 us latency
             -> 211 ops with 392 us latency
             -> 35 ops with 348 us latency
             -> 3 ops with 305 us latency
             -> 6 ops with 261 us latency
             -> 4 ops with 218 us latency
             -> 10 ops with 174 us latency
             -> 14 ops with 131 us latency
             -> 182 ops with 87 us latency
             -> 269 ops with 44 us latency
             -> 659 ops with 0 us latency

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms