Linux in Government: Optimizing Desktop Performance, Part I
In his article, "Linux for Suits: The No-Party System", Doc Searls makes an observation about Linux that can help us understand why we might want to tweak the performance of Linux desktops. Referring to Linux as raw material with which people can build distributions, he says:
As one Linux programmer once told me, "Linux can't sue anybody." In fact, Linux isn't even a platform of the sort defined by Windows and Mac OS. Instead, Linux is a form of building material that grows in the wild and naturally is suited for making foundations and frameworks. The wild in this case is fertile human mentation, which is why it evolves and improves in the course of being put to use.
People distribute Linux rather than build it. Unlike traditional operating systems, anyone with some knowledge of Linux can pull the pieces together and create a distribution. So, although many different distributions of Linux are available, they come from the same building materials. The differences among distributions take the form of tweaks here and there or various ways in which users perform the same tasks and what kind of themes are used. But as many have said, "Linux is Linux"--and it has flavors. Distributors create those flavors, and underlying these flavors are default configurations.
For most of its existence, people have distributed Linux as a workstation or a server rather than as a desktop. In effect, the default workstation that has evolved has existed mostly for developers. So, when you install a Linux distribution with a graphical interface, it generally looks like what a developer might want. It performs similar to many UNIX workstations, which can seem slow for many knowledge workers.
In this article, we look at the Linux desktop in a slightly different light. We think of it as a computer system that maximizes its strength as a consumer product. When we optimize Linux for the consumer, it becomes a fast interface.
If you have complained about the speed of OpenOffice.org or Firefox or about the amount of time Linux takes to boot up, this set of optimizations should change your perception. Linux can boot up quickly, the word processor can spring open and the browser can fly. So, let's make these adjustments so your computer can fly.
Note: We use the two most popular Linux distributions for this article, Fedora Core 3 and Ubuntu 5.04. Red Hat builds and releases Fedora using an RPM-based package management system. The Ubuntu developers base their distribution on the deb package management system. Mandriva, SUSE and Red Hat Enterprise Linux, among others, use the RPM package management systems. Linspire and Xandros, among others, use the deb package management system.
Many points exist in a PC where an operating system can bottleneck and slow down. One of the most common places for this to happen lies between random access memory (RAM) and the hard drive. Even if your system does have an ample supply of fast RAM, it might decide to conserve it and use virtual disk memory, which is contained in the swap file on the hard drive. The hard drive runs 100 times slower than RAM, so that's one place system speed goes.
You can fix this problem with system speed by adding more RAM. A few years ago, I often bought computers and added memory that doubled and tripled the price of the base system. I had to do this because as a writer I used graphics programs, and they used a lot of RAM. Fortunately, RAM doesn't cost much any more. You can buy a 1GB stick of generic RAM for most desktop computers for about $150. If you use a laptop, the memory costs more. Still, the increased performance of your computer makes the cost seem insignificant.
If you have enough RAM available, Linux uses that instead of the hard drive. In Figure 1, you can see a screenshot of Fedora's performance monitor on a system containing 768MB of RAM. Notice in a couple of places how the CPU jumped up while the memory remained steady. The monitored system is an AMD Sempron 2200 with a 1.5GHz processor. This system came from the Micro Center with 256MB of RAM and sells for approximately $250. It's a PowerSpec SBB1. I added 512MB of memory for $70.
To keep this system from immediately accessing the swap drive, I utilized one of the features of the Linux kernel and reduced its propensity for immediately looking for the swap file. People call this kernel aspect swappiness. It's a run-time tunable available through the proc interface for anyone needing to adapt kernel behavior to his or her own requirements.
The higher the parameter, the more the computer uses the disk. So, if you compile a large piece of software, you might want to use RAM for other things while you let the computer sit and compile. But, if you want to write a proposal and need to get to the Internet to do research, answer e-mail and use instant messaging, you probably want to use RAM instead of the disk.
On my system, I reduced the tendency for the kernel to use the swap file. I did so by running this command:
$ sudo cat /proc/sys/vm/swappiness
and found the setting at 60. That's the default set by the kernel developers. I wanted a lower number, so I ran:
$ sudo sysctl -w vm.swappiness=10
and ran the cat command again and it registered 10. I added
vm.swappiness=10 to /etc/sysctl.conf
I put this on the last line. No comments existed for that entry, so it looks naked in the configuration file. I noted an immediate improvement in responsiveness, and with the entry in /etc/sysctl.conf, the system booted up with the value of 10 as the new default.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- Interview with Patrick Volkerding
- SUSE LLC's SUSE Manager
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Returning Values from Bash Functions
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Managing Linux Using Puppet
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide