<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 10/25/13, 11:18 AM, Thomas Stokkeland wrote:<br>
<blockquote
cite="mid:462C92ED3567DF4993202FBEB4B3A6340EB9C61F@MAIL43.thoughtbus.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;">If you are not doing SAN stuff, or
very large file transfers within the collision domain - enabling
Jumbo is likely to cause a crappier performance than leaving it
at the standard 1500MTU - because, the router or receiving
device will tell the sender to fragment, your packet will be
split in half, this retransmit attempt will happen several times
till the MTU is met - then as the "knowledge" of this expires
your device will have to do that over and over.. causing a ton
of extra traffic on your network.. so, if you don't have a
requirement to use large MTU, then turn it off - i suspect there
are mechanisms in the vpn software that either ignores large
packets (because they are not to be routed) or just can't handle
fragmentation at that level<br>
</div>
</blockquote>
That makes sense - thanks for the explanation. I suffer the "If an
optional value is bigger, it must therefore be better/faster/more,
so I need to use it" syndrome.<br>
<br>
<pre class="moz-signature" cols="72">--
Paul Theodoropoulos
<a class="moz-txt-link-abbreviated" href="http://www.anastrophe.com">www.anastrophe.com</a></pre>
</body>
</html>