[FreeNX-kNX] NoMachine NX client compression
Darryl Palmer
dpalmerjr at gmail.com
Wed Nov 8 20:41:02 UTC 2006
On 11/8/06, fclewis at carolina.rr.com <fclewis at carolina.rr.com> wrote:
>
> Hi,
>
> I came as a surprise in the page:
>
> http://openfacts.berlios.de/index-en.phtml?title=NX_Components
>
> that my network connection type selection was controlling compression:
>
> "(Note: the "Modem" compression type [as shown in the NoMachine NX
> Client GUI] is the best compression, "LAN" setting does no compression
> at all. You can use "modem" compression in LANs for better efficiency.)"
>
> So if I'm on a WAN should I say Modem?
>
> Is caching also configured in this indirect way?
If the bottleneck is the transport then select the best compression, if it
is not, then do not. Selecting Modem connection type over a WAN will do 2
things. 1) Increase the load on the server and 2) make the interface less
"responsive" beacause you have to spend time compressing/uncompressing
messages.
Darryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20061108/69f60132/attachment.html>
More information about the FreeNX-kNX
mailing list