<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: cifs.tcp_window_size in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/cifs-tcp-window-size/m-p/66668#M6098</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have always made it a practice to increase this option from the default of 17520 to the recommend&lt;SPAN style="background-color: #f8fafd;"&gt;ed (per kb article and other documentation) to 64240.&amp;nbsp;&amp;nbsp;&amp;nbsp; This can improve large write transfers.&amp;nbsp;&amp;nbsp; In any case, windows can "slide" to the appropriate value.&amp;nbsp;&amp;nbsp; If you leave it at default, it can never be larger than 17520.&amp;nbsp; But at 64240, it can "slide" down.&amp;nbsp;&amp;nbsp; I've never heard or experienced any adverse effect from setting this option to 64240.&amp;nbsp;&amp;nbsp; And years ago, I had a copy of&amp;nbsp; Network General Sniffer report that graphed the positive improvement of this setting at 64240 as compared to the default 17520.&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;This option change will requre a cifs terminate/restart or reboot in order to take effect immediately. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Feb 2010 17:44:48 GMT</pubDate>
    <dc:creator>rtriana</dc:creator>
    <dc:date>2010-02-17T17:44:48Z</dc:date>
    <item>
      <title>cifs.tcp_window_size</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/cifs-tcp-window-size/m-p/66663#M6095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have read what is on wiki and also on kb.&amp;nbsp; Along those lines I have also discussed with support changing this setting from 17520 (default setting) to 64240 to improve performance.&amp;nbsp; I need to know if anyone has run into problems due to changing this or if you have had great success with making this change. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:18:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/cifs-tcp-window-size/m-p/66663#M6095</guid>
      <dc:creator>jmckenna</dc:creator>
      <dc:date>2025-06-05T07:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: cifs.tcp_window_size</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/cifs-tcp-window-size/m-p/66668#M6098</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have always made it a practice to increase this option from the default of 17520 to the recommend&lt;SPAN style="background-color: #f8fafd;"&gt;ed (per kb article and other documentation) to 64240.&amp;nbsp;&amp;nbsp;&amp;nbsp; This can improve large write transfers.&amp;nbsp;&amp;nbsp; In any case, windows can "slide" to the appropriate value.&amp;nbsp;&amp;nbsp; If you leave it at default, it can never be larger than 17520.&amp;nbsp; But at 64240, it can "slide" down.&amp;nbsp;&amp;nbsp; I've never heard or experienced any adverse effect from setting this option to 64240.&amp;nbsp;&amp;nbsp; And years ago, I had a copy of&amp;nbsp; Network General Sniffer report that graphed the positive improvement of this setting at 64240 as compared to the default 17520.&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;This option change will requre a cifs terminate/restart or reboot in order to take effect immediately. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Feb 2010 17:44:48 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/cifs-tcp-window-size/m-p/66668#M6098</guid>
      <dc:creator>rtriana</dc:creator>
      <dc:date>2010-02-17T17:44:48Z</dc:date>
    </item>
    <item>
      <title>Re: cifs.tcp_window_size</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/cifs-tcp-window-size/m-p/66675#M6102</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you.  That helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Feb 2010 18:28:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/cifs-tcp-window-size/m-p/66675#M6102</guid>
      <dc:creator>jmckenna</dc:creator>
      <dc:date>2010-02-17T18:28:40Z</dc:date>
    </item>
  </channel>
</rss>

