# Thinlinc - TigerVNC performance optimisations **URL:** \ **Category:** Community Support\ **Tags:** linux, tlserver, thinlinc\ **Created:** [30 September 2026 01:13 UTC](https://community.thinlinc.com/t/thinlinc-tigervnc-performance-optimisations/2085 "2026-09-30T01:13:43Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)\ **Post date:** [30 September 2026 22:35 UTC](https://community.thinlinc.com/t/thinlinc-tigervnc-performance-optimisations/2085/4 "2026-09-30T22:35:09Z")
Hi @Harj, > [@Harj](#): > > KillDisconnected=false # Don’t kill sessions on disconnect > DisconnectedTimeLimit=0 # No timeout (infinite reconnect window) ThinLinc has similar settings, but by default sessions will not be killed when disconnected. So unless you’ve changed this default, it should be fine. > [@Harj](#): > > tcp\_send\_buffer\_bytes=4194304 # 4 MB > tcp\_recv\_buffer\_bytes=4194304 # 4 MB (often commented out by default!) ThinLinc doesn’t have an equivalent here, but that’s because we rely on system-level settings instead. So the `net.core.wmem_max` and `net.core.rmem_max` settings you mention below will have the same effect, as should the other system-level tweaks you mentioned. Whether this will actually solve the performance issues you’re seeing or not depends on where the bottleneck is. In general, for GPU workloads, the bottleneck is often the CPU, as this is necessarily involved in shuffling data back and forth between the GPU and the session itself (at least until [Wayland](https://community.thinlinc.com/t/bringing-headless-remote-desktop-to-wayland/2084) support arrives). If this is the case, then unfortunately there’s no simple tweak available to mitigate this. Hope that helps. --- _[View the full topic](https://community.thinlinc.com/t/thinlinc-tigervnc-performance-optimisations/2085)._