Skip to main content
NetApp Knowledge Base

How do Dynamic Home Directories improve performance?

Views:
2,137
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

  • ONTAP 9
  • Data ONTAP operating in 7-mode
  • CIFS Home Directories
  • User profiles can be in used in VDI (Hyper-V) or Citrix Home Profiles using folder redirection.

Answer

  1. Take as an example "\\filer\home\user18456". With a regular FlexVol or FlexGroup setup, the sequence goes as follows for all Windows clients:
    1. Negotiate Protocol Request and Response.
    2. Session Setup Request and Response.
    3. Tree Connect \\filer\home and response.
    4. Create requests and closes.
    5. A Find of \\filer\home for user18456 with pattern of *.
    6. Finally a Close and then a create call of user 18456:
      捕获.PNG
  2. Notice, the Find Request above with "Pattern: *", means this will return all 18456 entries. ONTAP has to process each single entry and transmit all that associate data to the Windows client.
  3. Dynamic Home Directories simplify this and ONTAP only returns the single user's folder. ONTAP still has to search all 18,456 folders, but it is only doing a simple find, not reading the entire contents of the folder to transmit to Windows. This is less CPU computationally intensive compared to a typical home directory, and this is how performance is improved with Dynamic Home Directories.
    捕获2.PNG

 

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.