Xpra: Ticket #2382: memscroller stresses the html5 client

Split from #2231, see ticket:2231#comment:9.

Damage latency goes up to 7 seconds with chrome! Average is also too high: memscroller latency



Sun, 11 Aug 2019 06:21:06 GMT - Antoine Martin: attachment set

memscroller latency


Sun, 11 Aug 2019 06:21:48 GMT - Antoine Martin: status, description changed


Wed, 14 Aug 2019 06:34:16 GMT - Antoine Martin:

More test data showing the memscroller outlier problem in ticket:2231#comment:12.


Thu, 15 Aug 2019 11:47:09 GMT - Antoine Martin:

As per ticket:619#comment:29, the problem occurs only with NODELAY=0. My guess is that this buffers too many packets in the kernel's socket output buffer, allowing things to spiral out of control.


Mon, 19 Aug 2019 16:32:09 GMT - Antoine Martin: attachment set

memscroller also uses too much memory


Mon, 19 Aug 2019 16:32:36 GMT - Antoine Martin:

memscroller also uses too much memory: memscroller also uses too much memory


Thu, 05 Sep 2019 11:45:00 GMT - Antoine Martin: milestone changed

As per comment:3 and ticket:2231#comment:12, the default configuration handles this well enough that this can wait for the next release.


Thu, 05 Mar 2020 10:32:53 GMT - Antoine Martin: milestone changed


Sun, 04 Oct 2020 13:05:44 GMT - Antoine Martin: milestone changed


Sat, 23 Jan 2021 05:49:48 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2382