IBM's IntelliStation A Pro
The A Pro appears to be aimed solidly at a graphic workstation market. As such, I tested it using some GIS exploration software I have experience with, so I could get a feel for how well IBM has succeeded at providing a machine for that market.
The machine ships with a pretty standard Red Hat Enterprise Server load. As mentioned above, there were a few hiccups during load, mostly connected to video configuration and port selection. Past that, it doesn't look like IBM did much at all to the distribution, short of loading the NVIDIA driver as noted above. Although I'd like to see more “welcome to your A Pro Super Machine, here's what you've got”, a stock distribution is less likely to be overwritten immediately, so IBM's decision is understandable.
Partitioning was done competently in my opinion, with /var suitably reined in. When you are in the Linux hardware business you quickly realize there is no one true partitioning scheme. I imagine you would want to tell IBM your preferred layout if you were to buy in quantity, though. Like many Linux users, I have a set of things I do to any base load—change Mozilla's search to Google, set up the monitor to reflect my ideas about color depth and resolution—and the system didn't gag on anything I did to it in that vein.
The A Pro comes with the regular array of apps, including Mozilla, OpenOffice.org and everything else that ships with Red Hat ES. IBM chose to load all the apps, which is a valid decision for a desktop machine. Again, when buying, you might want to specify the parameters of your load.
Java is the only major language not supported out of the box, unless you consider Pascal major. This struck me as odd considering IBM's dedication to the language.
Games are a good way to test the OpenGL subsystem, and they also are fun. Tux Racer ran fine—no graphic glitching. The sound was not turned on out of the box, though, so I set that up using the standard Red Hat sound card setup program to good result. It struck me as odd that IBM hadn't done this as part of the load.
Because I wanted a program that could test the graphics, processors and memory handling of this machine, I chose the geographical exploration application TerraVision, which allows you to do 3-D flythroughs of GIS height map data with textures created from satellite data. I loaded four data sets into the system—the Palo Alto resolution set, global set, Lawrence Livermore and San Francisco—all at various resolutions, spanning 1km to 3 meters. This represents a total of about 4GBs of data, and although the program is good with swapping the data into the program's memory, it is quite consumptive. The A Pro performed quite well—no real glitching of the data set and the flythrough was smooth. You can download TerraVision and a number of data sets off the SRI Web site (www.ai.sri.com/TerraVision).
When comparing the A Pro against two white box vendors, the IBM machine seems to run about $1,800 US more. Is it worth it? Perhaps, as IBM's casework and layout generally is excellent, but I have to admit I wasn't overwhelmed with the machine to the tune of $1,800, mostly due to the noise profile. I have to say, from a sound perspective, it was a relief to shut off the A Pro, which is never a good thing. The Opteron is a cool-running 64-bit chip, so it shouldn't take this many decibels to cool it.
The case is designed to hold and power a vast number of drives, so it has cooling to spare, but there is no clear way to turn down the fans and make them less intrusive. The scope of the machine should be taken into account as the valid excuse for the noise level, however. If you need the beefiest, most solid workstation on the market, then the IBM A Pro is what you'll be buying, and I think you'd be both happy and well served by it.
IBM Responds to the “Memory Hole”
The IBM IntelliStation A Pro uses an x86 industry-standard method to assign memory space for drivers of installed devices, which indicates that less memory is available to the operating system than the actual “physical” memory installed in the system. The memory reported by the operating system does not account for space reserved for the drivers that must reside in memory for devices such as the network controller, SCSI, IEEE 1394 and graphics cards.
The A Pro is packed with integrated technologies to provide our high-end customers with the scalability and functionality they demand. The industry-standard method implemented in the A Pro has an architectural limitation, because it is an x86-based system that must support both 32- and 64-bit operating systems. Therefore, the system BIOS must allocate memory for these device drivers within the first 4GB of memory in order to support the 32-bit operating systems.
As the first worldwide tier-one vendor to ship x86 64-bit capable workstations, IBM is leading the design of new solutions to take advantage of the full capabilities of the IntelliStation A Pro. We are in the process of working with our hardware and software vendors to design an open solution to eliminate the memory restriction in systems running a 64-bit operating system in future releases of the A Pro.
Chris DiBona is the cofounder of Damage Studios and works on the new massively multiplayer on-line role-playing game Rekonstruction. Chris is an internationally known open-source advocate. He writes for the LJ Web site and the book he co-edited, Open Sources, won the Linux Journal book-of-the-year award in 1999. A sequel currently is in the works. His personal Web site can be found at dibona.com.
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!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- SourceClear Open
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
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