- Paperback: 250 pages
- Publisher: MIT Press (18 Jun 1999)
- Language English
- ISBN-10: 026269218X
- ISBN-13: 978-0262692182
- Product Dimensions: 22.9 x 20.3 x 1.9 cm
- Amazon Bestsellers Rank: 1,383,163 in Books (See Top 100 in Books)
| |||||||||||||||
|
Amazon.co.uk Trade-In Store
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Plus, get an extra £5 Gift Certificate when you trade in books worth £10 or more before June 30, 2012. Visit the Books Trade-In Store for more details. |
Product details
|
After an introduction to Beowulf and parallel computing in general, the authors describe the advantages to and organisation of a typical Beowulf setup. They next describe the basic PC hardware (which will be familiar to many Intel users). The do-it-yourself impulse in Beowulf supercomputing is strong, and the authors show how to choose everything from a CPU and memory to networking options (including TCP/IP basics and Fast Ethernet). They cover hardware and software installation and the basics of configuring Linux on Beowulf nodes (which do the work of parallel processing).
Next the book covers issues of security and system administration of a Beowulf cluster. (Here the authors strike a balance between accessibility and security with the concept of a "guarded Beowulf.") They cover a variety of Linux utilities for remote computing and administration.
An essential piece of Beowulf technology is the Message Passing Interface (MPI), a set of APIs that permit programmers to develop parallel programs in C/C++ and FORTRAN. With MPI, programs running on different CPUs can pass messages and share the same data. The samples that round out this book are excellent--a ray-tracing example, a parallel sorting algorithm, and a cellular automata program. The authors do a good job of explaining the issues of taking advantage of parallelism within Beowulf software. --Richard Dragan
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
IT IS NOT (nor do I believe it was intended as) a detailed roadmap of EXACTLY how to build one. The Beowulf architecture isn't so much a single type of implementation, but rather an approach to applying COTS technology to solving computational problems. The details of any single Beowulf implementation depend greatly on the specific computational problem being attacked. (Something that is pointed-out within the book.) The authors therefore took a different approach.
Some of the topics covered in the book WILL, eventually, be outdated: specifically, the section on the PCI bus, some of the material on network technology, and the section on available processors. As COTS technology advances, and as Beowulf architectures change to take advantage of those advances, some sections will become outdated. However, this is unavoidable for any text reviewing the current state-of-the-art. There is also a lot more here that is NOT likely to be outdated within the next several years..
There may also be sections in the text that the reader will already be familiar with, and can therefore skip. This is also inevitable considering the nature of the text and will obviously vary depending on the reader.
I can recomend this text highly as a starting point in learning what a Beowulf is, some of the ways they are put together, and for exploring many important design and implementation decisions. In my own case, it helped me resolve a number of design issues I was wrestling with about my own system. It does not, however, stand alone. After starting with this text, most readers will then certainly need to refer to online sources for further information.
At the end of the day I DID build my own low-end beowulf, but sadly I can't say that any of the information that I needed was found in this book. It might have been there but the unorganized layout mad it impossible to find anything.
|