-menu was responding slow when using it for the first time, was due to
-the way KDE find application icons. I discovered that showing the
-Multimedia menu would cause more than 20 000 IP packages to be passed
-between the LTSP client and the NFS server. Most of these were NFS
-LOOKUP calls, resulting in a NFS3ERR_NOENT response. Looking at the
-strace of kicker in Lenny (or plasma-desktop i Squeeze - same problem
-there), I see that the source of these NFS calls are access(2) system
-calls for non-existing files. KDE can do hundreds of access(2) calls
-to find one icon file. In my example, just finding the mplayer icon
-required around 230 access(2) calls.</p>
+menu was responding slow when using it for the first time, was mostly
+due to the way KDE find application icons. I discovered that showing
+the Multimedia menu would cause more than 20 000 IP packages to be
+passed between the LTSP client and the NFS server. Most of these were
+
+NFS LOOKUP calls, resulting in a NFS3ERR_NOENT response. Because the
+ping times between the client and the server were in the range 2-20
+ms, the menus would be very slow. Looking at the strace of kicker in
+Lenny (or plasma-desktop i Squeeze - same problem there), I see that
+the source of these NFS calls are access(2) system calls for
+non-existing files. KDE can do hundreds of access(2) calls to find
+one icon file. In my example, just finding the mplayer icon required
+around 230 access(2) calls.</p>