<br><tt><font size=2>Toni Asensi Esteve <asmond@orange.es> wrote
on 18/05/2010 08:43:50:<br>
<br>
> Les Mikesell wrote:<br>
> <br>
> > It might help a bit to keep your screens as 'plain' as possible,<br>
> > removing images and background gradients where you can to make
it more<br>
> > likely to be able to compress large blocks and cache and reuse
them.<br>
> <br>
> OK!. I created a new page about it:<br>
> <br>
> </font></tt><a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-"><tt><font size=2>http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-</font></tt></a><tt><font size=2><br>
> _FAQ/Screen_Performance<br>
> </font></tt>
<br>
<br><tt><font size=2>Hi Toni</font></tt>
<br>
<br><tt><font size=2>Oh, so there is a FAQ !!</font></tt>
<br>
<br><tt><font size=2>I thought you were joking !!</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>It might be worth adding a couple more things if you
are maintaining a</font></tt>
<br><tt><font size=2>FAQ.</font></tt>
<br>
<br>
<br><tt><font size=2>For example, you can customize for quality at the
expense of speed (or</font></tt>
<br><tt><font size=2>visa versa) as far as the link is concerned</font></tt>
<br><tt><font size=2> or </font></tt>
<br><tt><font size=2>compress for slow links verses speed as far as loading
the CUP/memory is</font></tt>
<br><tt><font size=2>concerned </font></tt>
<br>
<br><tt><font size=2>You can disable caching etc on an old/under-rescourced
workstation if</font></tt>
<br><tt><font size=2>the link is quite quick which can save you having
to buy hardware.</font></tt>
<br>
<br><tt><font size=2>And</font></tt>
<br>
<br><tt><font size=2>There are the usual issues regarding multi user machines
which are often</font></tt>
<br><tt><font size=2>more significant to the performance of an NX machine
then NX its-self.</font></tt>
<br>
<br><tt><font size=2>eg.</font></tt>
<br>
<br><tt><font size=2>Image quality</font></tt>
<br>
<br><tt><font size=2>If you want screen quality then upping the "custom
jpeg quality", or</font></tt>
<br><tt><font size=2>going to RGB only is a good idea but quality will
of course hit the link.</font></tt>
<br>
<br><tt><font size=2>Don't forget the Server<->Internet link, not
just user's WAN links.</font></tt>
<br>
<br><tt><font size=2>Low quality will help the link, but there will be
a hit on the CPU if</font></tt>
<br><tt><font size=2>you do high compression.</font></tt>
<br>
<br>
<br><tt><font size=2>Response Time</font></tt>
<br>
<br><tt><font size=2>If you disable the shared memory extension in the
client, then</font></tt>
<br><tt><font size=2>nomachine say you may get a quicker response time
reaction </font></tt>
<br><tt><font size=2>to screen changes, ( I haven't bother trying it myself,
but if you</font></tt>
<br><tt><font size=2>use a fast LAN then it might be a good default )</font></tt>
<br><tt><font size=2>and</font></tt>
<br><tt><font size=2>disabling deferred screen updates on a fast WAN link
may give</font></tt>
<br><tt><font size=2>a less jerky response. It is a default LAN setting.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>Link Speed</font></tt>
<br>
<br><tt><font size=2>A slow link can run better with jpeg set to very low
quality, but I </font></tt>
<br><tt><font size=2>wouldn't advise that for ordinary users because you
can barely </font></tt>
<br><tt><font size=2>see what you are doing.</font></tt>
<br>
<br><tt><font size=2>I've seen even "power users" who, for example
have been told</font></tt>
<br><tt><font size=2>about this sort of setting to give them the option
of using it in a</font></tt>
<br><tt><font size=2>cafe, fail to re-set it and then complain about link
quality.</font></tt>
<br>
<br><tt><font size=2>Link latency and packet loss can cause time out issues
which no</font></tt>
<br><tt><font size=2>amount of tweaking will fix. A "slow"
link may just be a cafe</font></tt>
<br><tt><font size=2>with too many users reading email for a session based
application.</font></tt>
<br>
<br><tt><font size=2>Don't set up remote printing, shared drives unless
you need them.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>Server load</font></tt>
<br>
<br><tt><font size=2>Disabling compression and encryption will reduce server
load.</font></tt>
<br>
<br><tt><font size=2>If your WANers use a VPN client you only need to encrypt
if you</font></tt>
<br><tt><font size=2>don't trust your LAN ( don't laugh, I've seen wi-fi
used to monitor</font></tt>
<br><tt><font size=2>(larger) VLAN packets being broadcast over London,
Windoze</font></tt>
<br><tt><font size=2>passwords, the lot )</font></tt>
<br>
<br><tt><font size=2>and . . .</font></tt>
<br>
<br>
<br><tt><font size=2>Useful work only</font></tt>
<br>
<br><tt><font size=2>Running an application rootlessly, misses out the
rest of the </font></tt>
<br><tt><font size=2>desktop, which can stop users running games, screensavers,</font></tt>
<br><tt><font size=2>email, web browsers, apps they aren't using etc</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>Cost effective</font></tt>
<br>
<br><tt><font size=2>In my view, tweaking is all well and good, but for
a "reliable high</font></tt>
<br><tt><font size=2>quality user experience" it's cheaper and more
effective to keep</font></tt>
<br><tt><font size=2>reasonable defaults and :-</font></tt>
<br>
<br><tt><font size=2>1/ stop the users using things they don't need to
do</font></tt>
<br><tt><font size=2>2/ add £200 worth of memory</font></tt>
<br><tt><font size=2>2a/ get another CPU core ( Yup, can still be cheaper)</font></tt>
<br><tt><font size=2>3/ don't use slow links ( there's always another cafe.
take up thy</font></tt>
<br><tt><font size=2> st*rbucks
card and walk )</font></tt>
<br>
<br><tt><font size=2>. . . . rather than set up test-beds to compare RGB
to high Q jpeg</font></tt>
<br><tt><font size=2>over a variety of departmental tasks.</font></tt>
<br>
<br><tt><font size=2>If you like that sort of thing, and the alternative
is testing the</font></tt>
<br><tt><font size=2>backups well and good.</font></tt>
<br>
<br><tt><font size=2>Personally I find testing backups more rewarding.</font></tt>
<br>
<br>
<br><tt><font size=2>My tuppen'orth</font></tt>
<br>
<br><tt><font size=2>The most significant issue with performance is:-</font></tt>
<br>
<br><tt><font size=2>don't let the users know that there are setting which
can be</font></tt>
<br><tt><font size=2>changed, else you'll get just-in-case/live-in-hope
complaints</font></tt>
<br><tt><font size=2>on the off chance that you can speed things up.</font></tt>
<br>
<br><tt><font size=2>The more users fiddle, the more "witchcraft"
type of associations</font></tt>
<br><tt><font size=2>they make between cause and effect and the more thay
fiddle.</font></tt>
<br><tt><font size=2>It's not just restricted to 17th century Lancashire
or Salem.</font></tt>
<br>
<br><tt><font size=2>You can only tweak for one senario !!</font></tt>
<br>
<br>
<br><tt><font size=2>Ye bottom line</font></tt>
<br>
<br><tt><font size=2>Don't let your hardware let you down - you can only
get so much</font></tt>
<br><tt><font size=2>out of it.</font></tt>
<br><tt><font size=2>Tweak your user-base (& management) not your setting.</font></tt>
<br><tt><font size=2>Use tweak-time to do something more productive.</font></tt>
<br>
<br>
<br><tt><font size=2><br>
> So that new questions about this subject... can be redirected to that
page. I<br>
> also added those instructions that we use in our company; feel free
<br>
> to correct <br>
> me: <br>
> <br>
> - If, for example, you have a slow connection,
you use the NX client and<br>
> you are using programs in the server that have
a normal presentation <br>
> ( those which show text, numbers, lines, squares,
and so on in the<br>
> screen... but not photographs or gradients) it's
better to configure the<br>
> client to use RGB compression in the menu "Display
> Settings".</font></tt>
<br>
<br><tt><font size=2>RGB is lossless encoding, ie mostly don't compress</font></tt>
<br>
<br><tt><font size=2>Personally, I find it slower than a steamroller, unless
on a LAN link.</font></tt>
<br><tt><font size=2>jpeg is everywhere for a reason !!</font></tt>
<br>
<br>
<br><tt><font size=2><br>
> <br>
> Greetings:<br>
> Toni<br>
> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX
problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
> <br>
> </font></tt><a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ"><tt><font size=2>http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</font></tt></a><tt><font size=2><br>
> <br>
> Don't forget to check the NX Knowledge
Base:<br>
> </font></tt><a href=http://www.nomachine.com/kb/><tt><font size=2>http://www.nomachine.com/kb/</font></tt></a><tt><font size=2>
<br>
> <br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org<br>
> </font></tt><a href="https://mail.kde.org/mailman/listinfo/freenx-knx"><tt><font size=2>https://mail.kde.org/mailman/listinfo/freenx-knx</font></tt></a><tt><font size=2><br>
> ________________________________________________________________<br>
</font></tt>