Skip to main content
NetApp Knowledgebase

Hitting QOS IOPS Limit without CIFS Oplocks Enabled

Views:
77
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

Applies to

All FAS systems with CIFS SMB.

Issue

Two CIFS shares were being tested by the same Application on the same Windows Server.

• Both volumes were hosted on same Node ,on same Aggregate and part of same Vserver.
• Both shares consisted of exactly the same files of same count.

However we could see a huge no. of IOPS(~13K) coming through to one volume as compared to the other (~1K Ops) ,when tested through the same Application.

As a result , the volume receiving high no. of IOPS suffered a latency due to QOS IOPS limit being reached.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support