On Wed, Jul 6, 2011 at 7:44 PM, David Burgess <[email protected]> wrote: > 2. The CPU frequency scaling governor is set to Performance by > default. The /etc/init.d/ondemand file exists in the chroot, but the > governor does not change, even after the 60-second sleep period and > I'm not sure why.
Ubuntu/LTSP disables a lot of needed services by default for both thin and fat clients, I've filed a bug about this in https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/694066 Apart from the governor, that probably includes the CUPS service as well, see if that's what's causing your printer-related issues. >> 3. It is commonly said that Ubuntu LTSP uses NBD instead of NFS > because it is faster, but my experience on an Athlon X2 is that > nbdproxy maxes the CPU around 60 MB/s, while NFS maxes the hdd around > 80 MB/s with much lower CPU usage. Am I doing it wrong? Can I > configure my fat client to use NFS only in the same way it can be done > with thin clients? Disable nbd-proxy to lower CPU usage (see comment #13 in https://bugs.launchpad.net/ltsp/+bug/589034) and re-enable compression in /etc/ltsp/ltsp-update-image.conf to allow about 2.5 times more data to be sent with the same bandwidth. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
