Table of ContentsView in Frames

Performance FAQs

What factors does the performance of an FPolicy depend on?

The following are some of the factors that the performance of FPolicy depends on:
  • Number of Operations (like read, open, close, and so on) being monitored
  • Number of registered FPolicy servers (load sharing)
  • Number of Policies screening the same operation
  • Network bandwidth between storage system and FPolicy server (round-trip time of the screen request)
  • Response time of the FPolicy server

How can we measure how FPolicy traffic is divided between CIFS and NFS traffic?

The output of the FPolicy command run at the storage system contains a counter for the total number of request screened by that particular file policy. However, currently there is no way to understand the division between CIFS and NFS traffic.

Every client request that goes through FPolicy screening generates some extra CIFS requests for internal FPolicy communication. This is true for both CIFS and NFS clients requests. Currently there is no way to measure this extra traffic.

If you switch on FPolicy before doing recalls, does that have an impact on performance?

Yes, switching on FPolicy before doing any recalls has an impact on the performance. The impact of the performance depends primarily on how FPolicy is configured. It is therefore recommended that you do not turn on FPolicy before doing any recalls.

When there are two FPolicy servers registered to a storage system with different performance levels, does the performance of the slower server affect the performance of the fast server?

Yes, the performance of the slower server does affect the performance of the faster server. It is therefore recommended that servers with same capabilities are used while connecting to a storage system.

Do we have a metric to determine the additional load on the CPU when FPolicy is enabled?

No, such data is not currently available for FPolicy.