Building the Ultimate Linux Workstation
In 1996, Eric Raymond wrote a popular article for LJ called “Building the Perfect Box: How to Design Your Linux Workstation”. Lately, some of us have gone hardware shopping, and noticed that the hardware choices have changed a little since Eric recommended a Pentium 133 or 166 with 2GB of disk space. So, we asked Eric and some other experts to help us update the recommendations for building the ultimate Linux workstation.
Back in 1996, Eric advised Linux Journal readers to “buy one or two levels lower than commercial state-of-the-art”. That's still good advice in general. If you're trying to save money, there's a lot of price difference between a manufacturer's fastest CPU and the ones just a little slower; and your money will be better spent on more RAM or other parts.
Even though Eric's advice is still good on the planet Earth, we're building the ultimate Linux box, so we'll select the fastest CPUs we can get. Yes, CPUs, plural. With background tasks on their own CPU, your cycle-hog processes, such as MP3 encoding and the GIMP, will have the other all to themselves, and that's good news. However, if you're on a budget and are going for a general feeling of “responsiveness” when starting programs or opening files, SMP won't help much, and you'll be better off with one CPU and 10,000RPM SCSI drives than with slow drives on an SMP system.
Which CPUs? Darryl Strauss worked on the render farm of Alpha-based Linux machines that rendered many scenes in Titanic (see the February 1998 issue of Linux Journal). “I really love Alphas”, he says. “I have a dual 264 system at home and it rocks. They are also doing some great work on their upcoming boxes that will include faster processors, a faster bus and AGP graphics. The problem is that they are niche. If you have a specialized application that runs on the Alpha, you can't beat them. If you want a general-purpose system, then Intel-compatible is the way to go.”
Most of the people writing the software you want to run are testing it on Intel-architecture systems, so we'll stick with Intel's current top-of-the-line processors for now. AMD CPUs are binary-compatible with Intel, and performance-wise they can take Intel one-on-one, but currently there's no motherboard that supports two of them.
The list of available motherboards changes constantly. There are enough new motherboards coming out to sustain entire web sites with just motherboard news. How can you pick one? Jason Collins, a software engineer for VA Linux Systems and developer of the Cerberus test suite, is building his own Linux system for home use, and has some advice on selecting a motherboard. “I look at overclocking sites. If a board is stable when it's overclocked, it's going to be very stable at its intended speed”, he says.
Sam Ockman, CEO of Penguin Computing, says, “Spend some money, get a nice Tyan board.” Tyan motherboards have a reputation for reliability among the Linux system vendors. Mike Higashi is a Linux consultant who builds many of his own machines, and he recommends Asus boards.
Darryl Strauss is using the Asus P2B-DS, which is based on Intel's old but reliable 440BX chipset. The BX motherboards are still a decent choice for SMP on a budget. If you're not going SMP, the current CPU and motherboard combination of choice is an AMD Athlon on an ABit KA7-100.
When choosing a motherboard, be sure it supports ECC RAM, and enough of it for your foreseeable needs. Considering the amount of RAM in an ultimate Linux workstation and the length of time it runs, you will get bit flips if you don't use ECC. There's a new “Linux ECC” driver that provides extended logging of single-bit ECC errors, which are normally invisible. If you have a supported motherboard, you can use it for testing.
Open up a large white window on your screen, and look over the top of your monitor at something in the distance. If you can detect flicker out of your peripheral vision, your video card or monitor is bad or misconfigured. Flicker that you don't ordinarily notice can give you a headache or other health problems. Different people seem to require different refresh rates—most are around 75-85Hz. The video card in any Linux box should be capable of an adequate refresh rate. For an ultimate Linux box, you'll need that high refresh rate on a very large monitor at 24 or 32 bits per pixel. Even if you aren't interested in 3-D, get a good video card to spare your eyes.
The ultimate Linux workstation needs 3-D. Darryl Strauss says, “The up-and-coming board to watch is the Radeon,” which is ATI's entry in the 3-D graphics performance race. “Performance is about the same as the GeForce2 and they want to do open-source drivers. It's just not out for Linux yet.” Watch your favorite Linux news sites for details. As we go to press, the speed leader is the NVIDIA GeForce2, which Strauss calls, “a great board except for the license”. This January, VA Linux Systems took a hit from the UNIX vendors' crack pipe and broke ranks with the rest of the Linux community to offer a fast but proprietary 3-D package for NVIDIA cards.
Trying to plug binary-only proprietary software into the low levels of a sleek open-source environment is like pilling a cat with chopsticks, so until NVIDIA gets on the clue bus, it's safest to go with one of the second-ranked boards—either the Voodoo 5 from 3dfx, or the new Matrox G450. Jason points out that the Matrox cards are good at taking advantage of more CPU power. “With a fast CPU, you can start to approach NVIDIA's speed.”
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
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