The PowerStation comes with Yellow Dog Linux 6 pre-installed. YDL began life in 1999 as an alternative to the Mac OS on Apple's PowerPC hardware. It is based on Red Hat Enterprise Linux and Fedora. Like every Red Hat/Fedora derivative I have ever used, it uses RPM for package management. Yum, which started as a Yellow Dog-specific add-on for simplifying package updates (and has been adopted by most RPM-based distributions) is naturally included, along with the graphical yum updater, Pup.
When first booting the PowerStation, you go through the normal Anaconda new-user setup. Unfortunately, this process crashed on me at the very end, forcing me to reboot the computer. It seemed like it was just a fluke, so I didn't worry about it too much, but I think it may have contributed to my Firefox problems (more on that later).
The package selection available in the default YDL repositories is decent, but it's not as large as I am used to on Ubuntu and Fedora. The repositories configured out of the box include the Yellow Dog Base, Extras and Updates repositories, along with a PowerStation-specific one. Most of the basic apps—from Firefox to OpenOffice.org to The GIMP to PostgreSQL to Pidgin—are present and accounted for.
Although most of the packages I expected to find were available, a couple interesting ones were absent. One in particular (which happens to be one of my favorite applications), Inkscape, was missing. Thanks to the PowerPC Fedora Extras repository, I was able to install it easily.
A couple packages I wanted to use on the box, such as the renameutils (from www.nongnu.org/renameutils), were not available as pre-built RPM packages (as far as I could see, anyway). In the case of renameutils, I was able to download, compile and install the package manually.
One big thing I had to get used to on the PowerStation was the lack of GRUB. Yaboot is the bootloader for the PowerStation.
Being unfamiliar with Yaboot, I elected not to tinker with it or even spend much time looking at it. The system booted fine, and I didn't want to render the box unbootable inadvertently. The Yaboot configuration does look marginally similar to GRUB's, and I'll leave it at that.
Enlightenment is the default desktop environment for the PowerStation. The default theme and layout are nice, and the menus are well organized.
One interesting decision Terra Soft made was to configure the first Enlightenment desktop to run Nautilus full screen for file management purposes. This was a little confusing at first when I tried to change the Enlightenment wallpaper and nothing happened. To change the wallpaper of the first desktop, I had to change the GNOME wallpaper. Wallpaper issues aside, using Nautilus is a smart move, because it is one of the most advanced file managers available. I soon got used to using the first desktop for file management and the rest for running apps. This arrangement actually forced me to become better organized as different tasks were more clearly and cleanly separated. The other three desktops do not have Nautilus running on them, so they behave like regular Enlightenment desktops, animated backgrounds and all.
GNOME also is available out of the box as a session login option for those who prefer it, and KDE can be installed with the package manager.
There's no difference in running apps like The GIMP, OpenOffice.org or Firefox on an IBM Power processor as opposed to an Intel or AMD processor, so I won't go into running them other than to say they ran fine.
Performance is one of those tricky areas that are hard to define and nail down—especially when trying to compare the PowerStation to x86 workstations. One thing I can say without any equivocation is that the PowerStation definitely is speedy. Applications launch instantly (or nearly so), and everything feels fast and snappy. But “feelings” sometimes can lie, so to get a more accurate view, I turned to some performance testing.
For testing, I installed the Phoronix test suite. Unfortunately, although I was able to install it without trouble by following the directions on the Phoronix Test Suite Web site and run most of the tests, a few of them, including compiling the Linux kernel and calculating Pi to 32 million digits, failed. In the case of the Linux kernel compilation test, Phoronix reported that the test completed in 4.12 seconds. This compares to a time on my laptop of 4,407.53 seconds. Now, I am the first to admit that the PowerStation is much faster than my old laptop, but it is not a thousand times faster.
In the case of the Pi calculation test, the issue was that the test assumes you are running on x86, and it tries to load an x86 binary, which obviously won't run on the IBM 970MP-powered PowerStation. Thankfully, other tests in the Phoronix test suite provided more trustworthy results. The mencoder test, for example, which converts an 89MB avi file, took a respectable average of 42.13 seconds. See Table 1 for the results of some of the other Phoronix test suite tests I ran on the PowerStation.
Table 1. Phoronix Test Results on the PowerStation
|RAMspeed Average Integer Test||2,661.78MB/s|
|OpenSSL||36 signs per second|
|GnuPG 1GB file encryption||21.96 seconds|
|Compress a 128MB file with lzma||315.53 seconds|
|Compress a 512MB file with gzip||39.38 seconds|
|Compress a 512MB file with parallel-bzip2||67.60 seconds|
|SQLite 2,500 insertions on indexed db||74.05 seconds|
|SciMark composite test||264.64Mflops|
|Timed PHP compilation||82.93 seconds|
|IOMeter file server access pattern||89.87 seconds|
|Timed Apache build||54.48 seconds|
One caveat in my testing is that all of the tests shown in Table 1 finished with minor errors, such as “PHP Notice: Undefined offset: 0 in /usr/share/phoronix-test-suite/pts-core/functions/pts-functions_system_cpu.php on line X”. I don't think the errors skewed the results in either direction, but there is a bug somewhere that does not exist when the tests are run on an x86-based machine.
My original plan was to run these tests head to head against a quad-core Xeon system I was testing at the time. However, due to delays in receiving the PowerStation and some unforeseen issues with the Xeon system, I was not able to do this. Feel free to run the same tests on your workstation and compare your performance to the PowerStation.
One curious thing about the test results is that some of them are slower than the score achieved by my laptop—for example, the SQLite test. My old laptop is able to complete that test in an average of 62.63 seconds—more than ten seconds faster than the PowerStation. This may be because of the way the SQLite test works, or maybe it favors Intel processors—I don't know. In most tests, the PowerStation was faster, and in some tests significantly faster, which is what I expected.
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
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader 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