From 1f5c83b9fa7d6883ee7cea2d8cc01caddf96a74c Mon Sep 17 00:00:00 2001 From: dswd Date: Thu, 25 Aug 2016 09:38:51 +0200 Subject: [PATCH] Updated Frequently Asked Questions (markdown) --- Frequently-Asked-Questions.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Frequently-Asked-Questions.md b/Frequently-Asked-Questions.md index eb980e6..60a8d7a 100644 --- a/Frequently-Asked-Questions.md +++ b/Frequently-Asked-Questions.md @@ -18,6 +18,7 @@ Most likely this is because of a slightly too high (or missing) MTU setting on t #### What happens when I increase the MTU above 1400? Setting the MTU higher than the physical medium causes IP to fragment each inner packet into several outer packets and reassemble them at the receiving side. This has the advantage that VpnCloud has to process less packets and therefore uses less CPU (most of it will be memcpy) and has less context switches. It will also save some bytes on the wire as less bytes are used for VpnCloud headers and UDP headers and only a small additional IP fragmentation header is added. I think in total that is the 2% you are seeing. + The downside is that if one of the outer packets gets lost on the wire the whole inner packet is lost. If your MTU is is 40 times higher than normal, 40 outer packets will be sent for one inner packet. So your packet loss rate will be about 40 times higher than normal (e.g. 4.1% instead of 0.1%). It will also influence your delay distribution negatively. If the delay distribution and the loss ratio matters to you, this is a bad idea. If your line is pretty good and you just care about throughput, I think it makes sense to increase the MTU.