VA Linux Workstation VArStation XMP
Manufacturer: VA Linux Systems, Inc.
Price: $3,000 to $9,000
Reviewer: Jason Kroll
The VArStation XMP (analogous to the StartX ZP) is a top-quality, high-powered workstation from VA Linux Systems. In the years since its 1993 inception, VA has earned a reputation for producing rock-solid, dependable, performance-maximizing, Linux-based workstations, servers and clusters. Once upon a time, VA also built laptops and hopefully will do so again soon. VA even has an entry-level machine, the SP, if you want to get a taste of the “good life”. The XMP lives towards the upper range of workstation machines and is indicative of a typical VA Linux system. Most VA workstations come in the same tower, which is an attractive, solid, heavy container with plenty of space and a powerful fan. Beyond that, VA allows any type of customization you want and provides an on-line system for piecing together whichever components you like. Here's a description of the machine VA Linux Systems sent to Linux Journal for review.
The core of the system is an Intel MS440GX motherboard featuring dual Pentium III Xeon 550MHz processors with 32KB of L1 cache and 512KB of L2 cache, 512MB of RAM and an 8.4GB SCSI drive from Quantum. For comparison (to be somewhat up to date), current VA workstations come with an Ms4406x or Tyan 1832 motherboard, are available with Pentium III and Pentium III Xeon processors, and typically have 512KB of L2 cache with the option of expanding to 2MB of L2 cache. Modern machines also have larger hard drives, usually SCSI of 18.2GB or so and often 512MB or more of SDRAM. What does this jargon mean?
L1 cache is “level 1 cache”, static RAM which sits on the processor. When your processor asks for an instruction from memory, it's very likely that the next instruction it will ask for is the one right below the current instruction in memory. Likewise, when one piece of data is loaded, the next piece of data the program will want is probably sitting right below that. Instead of loading the instructions individually, the processor caches 32KB or more on the chip (usually 16KB for instructions and 16KB for data) so it can get at the instructions and data immediately, instead of loading them from RAM every single time. This dramatically improves processor speed. The larger the L1 cache, the less loading from L2 cache and the faster the operation.
L2 cache is the “level 2 cache”, static (or sometimes dynamic and static) RAM which sits between L1 and the memory at large. Normal RAM is very slow (but cheap) compared to L2 cache (which in turn is slower and cheaper than L1 cache), so the L2 cache acts as a buffer to store large chunks of memory to be grabbed by the L1 cache, except L2 grabs 512KB or more at a time (depending on the size of your L2 cache) compared to the usual 32KB grabbed by L1. L2 is often considered the bottleneck in computer performance, but VA helpfully recommends that you buy bigger cache only if you do very many floating-point operations and your application is noticeably limited by L2 cache dependency. L1 cache loads instructions very quickly from L2 cache, which loads instructions from RAM, so the system is a kind of filtering pyramid to make sure the most needed instructions are most readily accessible.
One might expect a multitasking OS like Linux, which frequently grabs instructions and data from all over in memory, to attenuate the benefits of cache, but the granulation of multitasking systems is large enough that the effect is minimal, especially on fast processors. (Granulation in this case is the division of tasks into pieces, since multi-processing operating systems actually execute many lines of a task before going on to the next task in a queue, and on a 500MHz chip, many instructions and much data can be covered in a few microseconds before moving to the next task, hence the cache is definitely utilized.) Still, VA Linux recommends increasing performance by adding more memory (since we all know how well Linux takes advantage of extra memory) or using multiple machines rather than overloading on cache, as the most economical approach.
SDRAM, or synchronous dynamic RAM, is dynamic RAM which is synchronized for the system bus speed (which is different from the processor speed). That is, dynamic RAM loses its charge and constantly requires refreshing, and if the RAM refresh is synced to the speed of the processor's system bus, a noticeable performance improvement can be made. VA uses SDRAM which is the most fashionable at the moment. Although it doesn't translate into a monstrous performance increase, especially because of the very high speeds of L1 and L2 cache and the efficiency of this system, at the very least it's not a weak link. The core of hardware performance tends to be based around the CPU.
The motherboard of the VArStation contains two Intel Pentium III Xeon 550MHz chips, though one is by no means compelled to choose such a setup. At the moment, VA Linux offers a range of processors starting with Intel's Celeron 400MHz and ranging up to 600MHz Pentium IIIs and 550MHz Xeons. Workstations have one or two processors, servers are available with four, and clusters have more. The Linux kernel can take advantage of two processors and is said to do well with four, although it is rumored more might be gratuitous and a bit less efficient than distributed computing.
The difference between various chips can be confusing. Why is a Pentium III better than a Pentium II, and what do terms like MMX and Xeon mean? Chip design is actually quite complicated, especially with complex instruction set chips (CISC) like the x86, of which I'm not particularly fond. While there are issues of how a chip manages caching of instructions (and microarchitecture techniques such as multiple-branch prediction, data-flow analysis and speculative execution), much of the performance increase in the latest Pentiums and the like comes from raw speed and cache size, and differences between chip models have to do with cache and assembly-code instructions. For example, MMX means MultiMedia Extensions, which is 57 extra multimedia instructions, eight new registers, larger L1 cache and the ability to perform a single instruction on multiple data, known as SIMD. Xeon is the futuristic name given to the top of the Pentium line, designed for server applications. Xeons are made for multiprocessing and use 100MHz buses and 32KB of L1 cache via a 64-bit bus, with support for larger addresses for dealing with big machines. Xeon 36-bit addressing, for example, can access 64GB of physical memory, which may be 62GB more than Linux kernels support. At the moment, VA Linux uses Pentium IIIs for single-processor machines and Pentium III Xeons for dual-processor workstations. Suffice it to say, III is better than II on the whole, and Xeon is better where parallel processing is concerned. The entry-level machine from VA, the StartX SP, is based on the Celeron 400MHz, which has smaller L2 cache (128KB), although it is located directly on the chip for faster results.
All in all, VA matches the right chips to the right machines so that you get maximum performance for the price. For example, a Celeron is good for a home computer, whereas a Xeon would be inefficient overkill on a single-processor desktop machine. The important thing about Linux box builders, especially VA, is that they know how to optimize systems. VA is quite knowledgeable and helpful in recommending how to get the best performance for the dollar, and there really is an advantage to getting a system that's built especially for Linux machines.
Everything else on the VA boxes is top of the line, from SCSI drives to Ethernet cards to modems. There are no weak links in VA boxes. My only complaint is that the sound cards are not spectacular (for example, I would really like digital I/O), but Linux has a way to go as far as sound support. Video, on the other hand, is top quality and utilizes the latest Matrox cards. Of course, VA Linux computers come optimally preconfigured for the monitors VA sells. The keyboard is nice and heavy, although it has three stupid Windows keys. The mouse is a Logitech (for a right-hander, I might add). You don't have to worry about getting cheap components on a VA system. I asked VA about this. “We want overall quality to be high; we will not sacrifice quality to get the world's cheapest prices,” I was told. As for support, VA has 24x7 support staff, but the manual is so thorough you probably won't need support. The manual is actually a very large, thick, technical-looking collection of hardware data for everything in the machine. In addition, VA included Que's Using Linux book, SuSE's Linux Office Suite 99, a rescue disk, a couple of CD-ROMs for the video card and motherboard, and a CD-ROM of the OS. The system software for VA Linux workstations is the VA Linux OS.
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!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
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