Author: Vladimir Silva
Publisher: Charles River Media (Thomson
Price: US $49.95
Vladmimir Silva's Grid Computing for Developers
promises so much, offering to teach developers today's standards for
Grid computing, with the Globus Toolkit (GT) taking center stage. I
initially thought I was onto something very useful when I got the book
and was looking forward to learning more about grids. Soon, however, I
realized the book has a number of problems.
To start, the back cover refers to the book as "A Developer's Guide to
Grid Computing". It also states that the book is aimed at "beginner to
intermediate" level users, which it is not. After 50 pages of introductory
material, which sometimes is confusing and often is more marketing-speak
than technically useful information, a real shock came on page 55. That's
when the first source code is presented. The code is preceded by a short
disclaimer about how the code assumes the reader already is familiar with
parts of the GT, even though another 200 pages go by before the author
discusses those GT parts. Without that familiarity with GT, the code is
hard to follow. And, being that the book is aimed at developers, there
are pages upon pages of such code. Unfortunately, little accompanying
explanation is offered beyond brief overviews.
Beyond the problems with its content, the book has presentation problems
as well. It contains a number of glaringly obvious and embarrassing
spelling mistakes, the worst examples being "Baatch System" (page 119),
"Virtual zorganizations" (page 181), "Diffie and Helman" (page 193) and
"Web Ervices" (page 291). In addition, the included images mostly are
grainy bitmaps that look as though they were knocked together in a desktop
spreadsheet program. Screenshots are no better; they're grainy, poorly
labeled and sometimes incredibly small. For example, the screenshots
on page 260 are no bigger than a one-and-a-half inch square. And, the
less I say about the impossible to read let alone follow UML diagrams,
the better. Furthermore, the index is next to useless: try looking up
"OGSA-C", which appears on both the front and back covers but is not
listed in the index. Finally, being a computing text on a hot new topic, this
book is full of acronyms. But, no glossary and no list of acronyms are
provided. This book badly needs both.
In truth, I should have listened to the little warning that went off in
the back of my brain when I read on page 4 that the creation of
the ARPANET was one of the "milestones of the 1950s". Again, another
If you already are familiar with grids and the GT, there's probably
material in this book that is worth reading, although discussion of GT4
is thin on the ground. If you are new to grids, look elsewhere for a better
Paul Barry (firstname.lastname@example.org) lectures at the Institute of
Technology, Carlow, in Ireland. Information on the courses he teaches,
in addition to the books and articles he has written, can be found on
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
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- 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