Optimizing Linux Performance

• Phillip G. Ezolt
• Prentice Hall
• 0131486829

Order (or just read more about) Optimizing Linux Performance  from Amazon.com

More Books

I found a lot to like here, but I do need to complain about a few things. We'll do the good stuff first: there's excellent attention to detail often overlooked in performance books, the explanations are clear and illuminating, and the case studies are well done and quite interesting.

Too often a book like this will show a tool like vmstat, explain part of the output, and simply ignore the more esoteric or less interesting parts of the data. This can leave the reader wondering what certain headers mean, and send them scrambling to the man page. All too often the man page comes up short also, or gives a terse explanation that really isn't helpful. This book does better than most in that regard. I'd always like too see more, but this did fill in some gaps that man pages and other books don't bother with.

There's good attention given to explaining the relationships of data. For example, the author points out that if the number of context switches are much more than the number of timer interrupts, this must be because of sleeps or I/O waits. That's "obvious", but is easily lost in the confusion of looking at too many things at once.

The case studies are excellent, but concentrate on bugs or code optimizations rather than true system optimization. I liked that there was this kind of case study, because these often are not shown in performance books, but I wished that the author had included kernel and file system tuning studies also.

One minor annoyance cropped up throughout. When showing command line examples, the author has his prompt set to the machine name and directory, so you'll see something like this:

[ezolt@scrffy manuscript]$ sar -w -c -q 1 2
 

As he runs commands on different machines, the next example might be:

[root@wintermute root]# opcontrol --vmlinux=/boot/vmlinux-2.4.22-1.2174.nptlsmp
 

Those changing prompts distracted my eyes and often momentarily confused me. I think it's best to stick to plain "#" and "$" in examples.

I would have also appreciated a little better typography. The major chapter section headings are in a larger font, but after that everything blends together. So you get something like this:

2.2.1 vmstat (Virtual Memory Statistics)

(text ..)

2.2.1.1 CPU Performance Related Options

(text ..)

2.2.1.2 Example Usage

(text ..)

2.2.2 top (v. 2.0.x)

(text ..)

2.2.2.1 CPU Performance Related Options

(text ..)

2.2.2.2 Example Usage

(text ..)

This uniformity makes it hard to go back and quickly find the beginning of a section.

Overall, I liked this and think it will find a permanent spot in my bookcase.

Take Control of Switching to the Mac

Take Control of VMware Fusion 3

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.