Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 2 results
    • Heavy SMB signing pressure causes high SMB3 latency from Network CPU domain
      https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/Heavy_SMB_signing_pressure_causes_high_SMB3_latency_from_Network_CPU_domain
      In the latency breakdown section, the bulk of the latency is from Network or CPU N-blade, depending on the tools that are used to monitor performance cluster1::> set -c off advanced cluster1::*> stati...In the latency breakdown section, the bulk of the latency is from Network or CPU N-blade, depending on the tools that are used to monitor performance cluster1::> set -c off advanced cluster1::*> statistics start -node node1 -object cifs -counter total_smb3_1_connections_count|total_smb3_connections_count cluster1::*> statistics show -sample-id sample_1 As they have to complete for the same network threads with SMB signing workload
    • Extreme Client latency and/or hang due to shortage of long-term, replay cache buckets
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Extreme_Client_latency_and_or_hang_due_to_shortage_of_long_term_replay_cache_buckets
      Based on ONTAP statistics, high latency could be observed from OPM, Grafana, Perfstat/PerfArchive in the latency breakdown section. Depending on the tools that are used to monitor performance, the bu...Based on ONTAP statistics, high latency could be observed from OPM, Grafana, Perfstat/PerfArchive in the latency breakdown section. Depending on the tools that are used to monitor performance, the bulk of the latency is from 'CPU_NETWORK' or 'CLUSTER_INTERCONNECT'.