Skip to main content
NetApp Stage KB

Global File Cache: Why are users reporting slowness after changing DFS path from pointing to Backend File server to GFC Edge

  1. Last updated
  2. Save as PDF
Views:
1
Visibility:
Public
Votes:
0
Category:
global-file-cache
Specialty:
CLOUD
Last Updated:

 

 

Applies to

  • Global FIle Cache (GFC)
  • Edge
  • Backend File Server
  • DFS

Answer

  • Typically users are not aware of the path that their mapped drives are actually taking them. If the DFS path was pointing directly to the backend file server, then changed to point to a GFC Edge, those files worked on/created on the backend file server would be shown cold on the Edge.
  • The first open of the file will "fetch" the entire file and warm it up on the edge. The second open would be faster as the data already exists now on the edge. 
  • There is a constant overhead while working through GFC. Every file open will induce a check to see that the most up to date data is on the edge. 
  • The behavior reported is normal and to be expected. 
  • Expectations need to be set with the end users as an asynchronous cache can not be compared to a local file server.

Additional Information

additionalInformation_text

 

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.