ThinClientMemoryUsage

Differences between revisions 17 and 18
Revision 17 as of 2005-11-03 22:01:07
Size: 5245
Editor: 197_220_103_66-WIFI_HOTSPOTS
Comment:
Revision 18 as of 2005-11-03 23:21:45
Size: 5825
Editor: 245_220_103_66-WIFI_HOTSPOTS
Comment: add comments
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:

'''MattZimmerman: which modules? how will they be blacklisted? (check with ScottJamesRemnant to ensure the implementation is compatible with HardwareDetection)
Line 38: Line 41:

'''MattZimmerman: need to go into detail regarding how this will be implemented. The existing implementation relies on the kernel metapackages, which don't allow this.'''
Line 42: Line 48:

'''MattZimmerman: need to go into detail as to how nbd will be implemented on the client and how swap will be configured; it isn't plug-and-play'''
Line 52: Line 60:

'''MattZimmerman: choose one. I recommend doing it once, in ltsp-build-client.'''

Summary

In order for Dapper to be considered as a solution for breathing new life into old machines by using them as thin clients, Dapper will have to be able to boot thin clients that have as low as 32 megabytes of memory.

Rationale

There are a lot of older machines out there, and one of the huge selling points of any thin client GNU/Linux solution will be to use existing, older hardware that's unable to be used with other operating systems. Developing countries, schools, non-profits, and cost-conscious companies will all be interested in taking advantage of hardware they already own.

Use cases

Jeff has an old lab with a bunch of old Pentium 120's with 32 megabytes of memory. He's been informed that to upgrade his current operating system that he bought in 1998, to the current one will be both expensive and painful, as it will require him to replace all of his lab machines. However, he hears about Edubuntu on Slashdot, and downloads a Dapper Drake Ubuntu CD, and within a few hours, he's got it installed on a spare file server. He shows his boss the shiny new lab with great educational software without having to upgrade a single workstation, or buy a software license.

Scott is a systems administrator at a government agency that is chronically underfunded. His boss wants email, web browsing, office suite, and other applications on every box, but tells him he must do it without upgrading machines, as, "it isn't in the budget". His friend Oliver meets with him for lunch, and gives him a Dapper Drake CD, and offers to come by and help to get it installed. It fits the bill perfectly, and Scott's boss is impressed with the speed, and ease of administration. She tells him to deploy it in some of their out of town offices as well.

Amina and Tiye are the founders of a small start up company working on an embedded thin client kiosk solution to be used in homeless shelters in a developing country. Money's tight, being a startup, and their kiosk portal's a web based solution, but they need something to power the minimal kiosk machine. Dapper once again to the rescue, and the embedded boards they chose to use (with only 48 megs of ram) work wonderfully.

Design

To provide the thin client with the thinnest possible footprint, the following steps are needed:

  • Eliminate the loading of the restricted modules. The nVidia drivers usually aren't needed on a thin client anyway.
  • Blacklist the loading of certain other modules which won't need to be loaded.

MattZimmerman: which modules? how will they be blacklisted? (check with ScottJamesRemnant to ensure the implementation is compatible with HardwareDetection)

  • Reduce the amount of video ram needed by the client. We should calculate how much is needed to do 1024x768 in 16 bit colour (reasonable for most older machines) and set the VideoRam parameter appropriately in xorg.conf. The administrator should have the ability to manually set this value up or down, depending on if his local clients have more or less memory.

  • On the server, provide some kind of nbd swap daemon so that when a thin client does run out of ram, it will simply get a bit slower, as opposed to hard failing because ram's been exhausted.

Implementation

  • Removing unnecessary modules and startup scripts will not only reduce memory, but will speed up the booting. This is being handled by ThinClientFasterStartup.

  • Remove the restricted modules, and the ramdisk that holds them. This will free up to 12 megabytes of ram.

MattZimmerman: need to go into detail regarding how this will be implemented. The existing implementation relies on the kernel metapackages, which don't allow this.

  • Limit the X.org video memory to 2048 kilobytes by default. Add the appropriate shell scripting into ltsp-client-setup to read the X_VIDEORAM parameter from the lts.conf file and pre-seed the debconf value for configuring the xorg.conf file. This will allow the administrator to easily set it up or down as needed.
  • Each getty running on a console uses up memory. Reduce the number of gettys being spawned in the inittab to save memory. You should need one or two at the maximum.
  • Use swap over nbd to provide a virtual memory solution. If the terminal runs out of ram, it will begin swapping over the network, and slow down considerably, but this is preferable to having the thin client crash or reboot due to memory starvation. The LTSP project has modified the nbd-swapd server to automatically create the swap file on connect if it hasn't been created already. This saves the Ubuntu server administrator the task of having to do this as a manual process. The source for ltsp-swapd can be found at:
    • cvs -d :pserver:anonymous@cvs.ltsp.org:/usr/local/cvsroot co ltspswapd

MattZimmerman: need to go into detail as to how nbd will be implemented on the client and how swap will be configured; it isn't plug-and-play

Code

Videocard memory problem:

Preseed the debconf value xserver-xorg/config/device/video_ram to 2048 byte as a default in /etc/init.d/ltsp-client-setup, but make it respect a different value from lts.conf if one was set.

Inittab change:

The change to intittab should be done either on generation of inittab by changing svsvintis generation of /etc/inittab in the chroot or post deboostrap from the ltsp-build-client script.

MattZimmerman: choose one. I recommend doing it once, in ltsp-build-client.

ThinClientMemoryUsage (last edited 2009-07-24 03:12:16 by 201)