Bug 7958 - Web content isn't compressed
Summary: Web content isn't compressed
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Misc (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
Depends on:
Blocks: performance
  Show dependency treegraph
Reported: 2022-07-01 15:29 CEST by Pierre Ossman
Modified: 2022-11-24 10:42 CET (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2022-07-01 15:29:21 CEST
Right now, we send web content as-is from our web services (tlwebadm and tlwebaccess). Generally this works fine, but we could reduce the bandwidth used by actively compressing the data as it is transported. Most of the data we send is also stuff that would compress well.

Python has zlib support, so that part of the puzzle is already available. Fancier algorithms, such as brotli, are probably difficult to support though.

The counter-point is that currently the data sent is not very large. Especially compared to the VNC data sent later. But that could change as we use more JavaScript and SVG images.
Comment 1 Pierre Ossman cendio 2022-07-01 15:30:43 CEST
Also note that .svgz seems to be a mess and should probably be avoided:

Comment 2 Pierre Ossman cendio 2022-11-24 10:41:42 CET
A quick test with a prototype confirms that compressing data gives very little improvement in page load time, as we have very little data to load. The data does compress well, though, getting at least 50% reduction for most files.

It might be more beneficial under extreme circumstances, but are those circumstances too extreme to be useful anyway?

The currently dominating time is TLS setup. Which means that bug 6003 is probably the best way to improve load times.

Note You need to log in before you can comment on or make changes to this bug.