Improving packets/sec and data rate - v1.0.24

[Jared Ledvina]

Niklas - Thanks! Yeah, your Github issue was very useful for me to
understand what is probably causing our issue (the syscall chain done on
every UDP packet). Very interesting that you're able to see around 90%
of a Gig line on bare metal. Were you ever able to make any further
progress on adjusting Tinc based on the investigation in
https://github.com/gsliepen/tinc/issues/110 ?

Martin - Yeah, I was looking into Wireguard too. However, we're pretty
embeded with Tinc right now (as we've been running it for a few years
now) so, I'd love to be able to adjust our existing setup not get such a
perf hit. 

- Jared


On Wed, May 17, 2017, at 10:26 AM, Niklas Hambüchen wrote:
> I once filed this issue and did an investigation on high CPU load on
> cloud instances that might be relevant to this topic:
> 
> https://github.com/gsliepen/tinc/issues/110
> 
> If I remember correctly I found that AWS EC2 instances have this problem
> less than DigitalOcean instances.
> 
> On bare metal machines with tinc 1.0 and aes-128-cbc, I can get 90% of
> gigabit line speed over tinc.
> 
> On 17/05/17 19:17, Martin Eskdale Moen wrote:
> > Hi Jared,
> > I've seen the same while testing on digital ocean, I think it's the
> > context switching that happens when sending a packet.
> > I've done some testing with wireguard and that has a lot better
> > performance but it's still changing quite a lot and only does a subset
> > of what tinc does so probably not a stable solution.