<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20689">
<style type="text/css"><!--html { font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; }--></style><style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"><div>I confirmed it by looking at the network trace. I had another server where I could see it was using SMB2. There are registry settings to disable SMB 2 and 3, but in this case I didn’t touch those.</div><div><br></div><div>Mark<br></div><div data-signatureblock="true"><br></div><div style="padding-top: 5px; border-top-color: rgb(229, 229, 229); border-top-width: 1px; border-top-style: solid;"><div><font face=" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style='line-height: 15pt; letter-spacing: 0.02em; font-family: "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; font-size: 12pt;'><b>From:</b> <a href="mailto:moder@abv.bg" target="_parent">M. D.</a><br><b>Sent:</b> Thursday, December 11, 2014 6:32 AM<br><b>To:</b> <a href="mailto:mark@markfalk.com" target="_parent">Mark Falk</a><br><b>Cc:</b> <a href="mailto:jcifs@lists.samba.org" target="_parent">jcifs@lists.samba.org</a></font></div></div><div><br></div><div dir=""><div id="readingPaneBodyContent"> Hello Mark,<br><br>We too are experiencing performance issues with NetApp Filer. <br><br>We were thinking that it's because NetApp Filer has a crappy SMB 1 support and also because SMB 1 is slower by design but we might be wrong.<br><br>Can you please tell me how do you know that your windows client is using SMB1? Did you disable SMB 2 and 3? Did you restart after that?<br><br>Best regards,<br>M.D<br><br><br> >-------- Оригинално писмо --------<br> >От: Mark Falk <br> >Относно: [jcifs] JCIFS WAN performance vs. Windows<br> >До: jcifs@lists.samba.org<br> >Изпратено на: Четвъртък, 2014, Декември 11 03:00:54 EET<br> ><br> ><br> >I'm working on a project which is using JCIFS to copy a single 40 MB file <br> >across a WAN with 70ms latency. The server is a NetApp Filer. I've tweaked <br> >about every parameter I can, but I can't get above 4 Mbps on Linux, <br> >whereas using a simple copy command on a Windows 2008R2 client I'm seeing <br> >30 Mbps. Both are using SMB 1.0. I've upped the MPX count and snd_buf_size <br> >to match Windows.<br> ><br> >Linux command line:<br> >/usr/local/java/jdk_8u5_x64/bin/java -classpath ./jcifs_1.3.17/jcifs-<br> >1.3.17.jar:. -Djcifs.smb.client.snd_buf_size=33028 -<br> >Djcifs.smb.client.maxMpxCount=50 -Djcifs.util.loglevel=3 -<br> >Djcifs.resolveOrder=DNS -Djcifs.smb.client.dfs.disabled=true TestJavaCopy <br> ><br> >Graphs:<br> >JCIFS:<br> >http://i.imgur.com/Zl386qK.png<br> ><br> >Native 2008R2 client using "copy \\UNCPATH :":<br> >http://i.imgur.com/MIFcr39.png<br> ><br> >Any thoughts? Packet details available upon request.<br> ><br> >Thanks,<br> >Mark<br> ><br> ><br></div></div></div>
</body>
</html>