Improving packets/sec and data rate - v1.0.24

Naemr . naemrr at gmail.com
Thu May 18 04:13:53 CEST 2017


I noticed a large performance boost both on bare metal and in vps instances
by turning on kernel routing in the tinc config, and using full host
declerations for routs rather than dumping things to the tun interface
ambiguously.

"Forwarding = kernel"

ip route add 1.2.3.4 via 4.3.2.1 dev tun
-instead of-
ip route add 1.2.3.4 dev tun

On May 17, 2017 3:10 PM, "Niklas Hambüchen" <mail at nh2.me> wrote:

> On 17/05/17 21:50, Jared Ledvina wrote:
> > Were you ever able to make any further
> > progress on adjusting Tinc based on the investigation in
> > https://github.com/gsliepen/tinc/issues/110 ?
>
> Hi Jared,
>
> No, not yet.
>
> I list a few ways for potential improvements in the ticket, but the one
> that I suspect would do most on the type of virtualisation that
> DigitalOcean does is to add a feature to the Linux kernel to sending the
> data for multiple UDP packets in one syscall, as mentioned in comment
> https://github.com/gsliepen/tinc/issues/110#issuecomment-201949838.
>
> In the last message of that Kernel code review, Alex Gartrell says
> "Sounds good to me. I'll get a patch turned around soon.". I don't know
> if they ever got around to it. It might be worth shooting an email to ask!
> It would be great to have that feature.
>
> For me personally the issue became less important, when I realised that
> the syscall overhead is more specific to the DigitalOcean virtualisation
> and less prominent with the virtualisation that AWS uses.
> I also currently use mainly bare metal so that this issue affects me
> even less. I would still love to see it fixed or if it myself (if I need
> it, or I have some free time, or if I find somebody who wants me to do
> it for them).
>
> Niklas
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20170517/a4279684/attachment-0001.html>


More information about the tinc mailing list