Always Learning

Advanced Search

Optimizing Linux Performance

Optimizing Linux Performance

A Hands-On Guide to Linux Performance Tools

Phillip Ezolt

Apr 2005, Paperback, 384 pages
ISBN13: 9780131486829
ISBN10: 0131486829
This title is ordered on demand which may result in extended delivery times.
  • Print pagePrint page
  • Email this pageEmail page
  • Write a reviewWrite a review
  • Share

Readers learn to use Linux's rich set of performance tools to make their applications run better.

  • Readers learn how to find and remove performance bottlenecks and increase the performance of Linux applications.
  • Useful format -- Reader learns tool's purpose, the tool's options, than a hands-on example of how to use the tool.
  • Author is key -- enhanced the industry standard and established benchmarks for greater performance.

  • The first comprehensive, expert guide for end-to-end Linux application optimization

  • Learn to choose the right tools—and use them together to solve real problems in real production environments

Superior application performance is more crucial than ever—and in today's complex production environments, it's tougher to ensure, too. If you use Linux, you have extraordinary advantages: complete source code access, plus an exceptional array of optimization tools. But the tools are scattered across the Internet. Many are poorly documented. And few experts know how to use them together to solve real problems. Now, one of those experts has written the definitive Linux tuning primer for every professional: Optimizing Linux® Performance.

Renowned Linux benchmarking specialist Phillip Ezolt introduces each of today's most important Linux optimization tools, showing how they fit into a proven methodology for perfecting overall application performance. Using realistic examples, Ezolt shows developers how to pinpoint exact lines of source code that are impacting performance. He teaches sysadmins and application developers how to rapidly drill down to specific bottlenecks, so they can implement solutions more quickly. You'll discover how to:

  • Identify bottlenecks even if you're not familiar with the underlying system

  • Find and choose the right performance tools for any problem

  • Recognize the meaning of the events you're measuring

  • Optimize system CPU, user CPU, memory, network I/O, and disk I/O—and understand their interrelationships

  • Fix CPU-bound, latency-sensitive, and I/O-bound applications, through case studies you can easily adapt to your own environment

Install and use oprofile, the advanced systemwide profiler for Linux systems

If you're new to tuning, Ezolt gives you a clear and practical introduction to all the principles and strategies you'll need. If you're migrating to Linux, you'll quickly master Linux equivalents to the tools and techniques you already know. Whatever your background or environment, this book can help you improve the performance of all your Linux applications—increasingbusiness value and user satisfaction at the same time.


© Copyright Pearson Education. All rights reserved.

Preface

1. Performance Hunting Tips.

General Tips.

Take Copious Notes (Save Everything).

Automate Redundant Tasks.

Choose Low-Overhead Tools If Possible.

Use Multiple Tools to Understand the Problem.

Trust Your Tools.

Use the Experience of Others (Cautiously).

Outline of a Performance Investigation.

Finding a Metric, Baseline, and Target.

Track Down the Approximate Problem.

See Whether the Problem Has Already Been Solved

The Case Begins (Start to Investigate).

Document, Document, Document.

Chapter Summary

2. Performance Tools: System CPU.

CPU Performance Statistics

Run Queue Statistics.

Context Switches.

Interrupts.

CPU Utilization.

Linux Performance Tools: CPU.

vmstat (Virtual Memory Statistics).

top (v. 2.0.x).

top (v. 3.x.x).

procinfo (Display Info from the /proc File System).

gnome-system-monitor.

mpstat (Multiprocessor Stat).

sar (System Activity Reporter).

oprofile.

Chapter Summary

3. Performance Tools: System Memory.

Memory Performance Statistics.

Memory Subsystem and Performance.

Memory Subsystem (Virtual Memory).

Linux Performance Tools: CPU and Memory.

vmstat (Virtual Memory Statistics) II.

top (2.x and 3.x).

procinfo II.

gnome-system-monitor (II).

free.

slabtop.

sar (II).

/proc/meminfo.

Chapter Summary

4. Performance Tools: Process-Specific CPU.

Process Performance Statistics.

Kernel Time Versus User Time.

Library Time Versus Application Time.

Subdividing Application Time.

The Tools.

time.

strace.

ltrace.

ps (Process Status).

ld.so (Dynamic Loader).

gprof.

oprofile (II).

Languages: Static (C and C++) Versus Dynamic (Java and Mono).

Chapter Summary.

5. Performance Tools: Process-Specific Memory.

Linux Memory Subsystem.

Memory Performance Tools.

ps.

/proc/<PID>.

memprof.

valgrind (cachegrind).

kcachegrind.

oprofile (III).

ipcs.

Dynamic Languages (Java, Mono).

Chapter Summary.

6. Performance Tools: Disk I/O.

Introduction to Disk I/O.

Disk I/O Performance Tools.

vmstat (ii).

iostat.

sar.

lsof (List Open Files).

What’s Missing?

Chapter Summary.

7. Performance Tools: Network.

Introduction to Network I/O.

Network Traffic in the Link Layer.

Protocol-Level Network Traffic.

Network Performance Tools.

mii-tool (Media-Independent Interface Tool).

ethtool.

ifconfig (Interface Configure).

ip.

sar.

gkrellm.

iptraf.

netstat.

etherape.

Chapter Summary

8. Utility Tools: Performance Tool Helpers.

Performance Tool Helpers.

Automating and Recording Commands.

Graphing and Analyzing Performance Statistics.

Investigating the Libraries That an Application Uses.

Creating and Debugging Applications.

Tools.

bash.

tee.

script.

watch.

gnumeric.

ldd.

objdump.

GNU Debugger (gdb).

gcc (GNU Compiler Collection).

Chapter Summary

9. Using Performance Tools to Find Problems.

Not Always a Silver Bullet.

Starting the Hunt.

Optimizing an Application.

Is Memory Usage a Problem?

Is Startup Time a Problem?

Is the Loader Introducing a Delay?

Is CPU Usage (or Length of Time to Complete) a Problem?

Is the Application’s Disk Usage a Problem?

Is the Application’s Network Usage a Problem?

Optimizing a System.

Is the System CPU-Bound?

Is a Single Processor CPU-Bound?

Are One or More Processes Using Most of the System CPU?

Are One or More Processes Using Most of an Individual CPU?

Is the Kernel Servicing Many Interrupts?

Where Is Time Spent in the Kernel?

Is the Amount of Swap Space Being Used Increasing?

Is the System I/O-Bound?

Is the System Using Disk I/O?

Is the System Using Network I/O?

Optimizing Process CPU Usage.

Is the Process Spending Time in User or Kernel Space?

Which System Calls Is the Process Making, and How Long Do They Take to Complete?

In Which Functions Does the Process Spend Time?

What Is the Call Tree to the Hot Functions?

Do Cache Misses Correspond to the Hot Functions or Source Lines?

Optimizing Memory Usage.

Is the Kernel Memory Usage Increasing?

What Type of Memory Is the Kernel Using?

Is a Particular Process’s Resident Set Size Increasing?

Is Shared Memory Usage Increasing?

Which Processes Are Using the Shared Memory?

What Type of Memory Is the Process Using?

What Functions Are Using All of the Stack?

What Functions Have the Biggest Text Size?

How Big Are the Libraries That the Process Uses?

What Functions Are Allocating Heap Memory?

Optimizing Disk I/O Usage.

Is the System Stressing a Particular Disk?

Which Application Is Accessing the Disk?

Which Files Are Accessed by the Application?

Optimizing Network I/O Usage.

Is Any Network Device Sending/Receiving Near the Theoretical Limit?

Is Any Network Device Generating a Large Number of Errors?

What Type of Traffic Is Running on That Device?

Is a Particular Process Responsible for That Traffic?

What Remote System Is Sending the Traffic?

Which Application Socket Is Responsible for the Traffic?

The End.

Chapter Summary.

10. Performance Hunt 1: A CPU-Bound Application (GIMP).

CPU-Bound Application.

Identify a Problem.

Find a Baseline/Set a Goal.

Configure the Application for the Performance Hunt.

Install and Configure Performance Tools.

Run Application and Performance Tools.

Analyze the Results.

Jump to the Web.

Increase the Image Cache.

Hitting a (Tiled) Wall.

Solving the Problem.

Verify Correctness?

Next Steps.

Chapter Summary

11. Performance Hunt 2: A Latency-Sensitive Application (nautilus).

A Latency-Sensitive Application.

Identify a Problem.

Find a Baseline/Set a Goal.

Configure the Application for the Performance Hunt.

Install and Configure Performance Tools.

Run Application and Performance Tools.

Compile and Examine the Source.

Using gdb to Generate Call Traces.

Finding the Time Differences.

Trying a Possible Solution.

Chapter Summary

12. Performance Hunt 3: The System-Wide Slowdown (prelink).

Investigating a System-Wide Slowdown.

Identify a Problem.

Find a Baseline/Set a Goal.

Configure the Application for the Performance Hunt.

Install and Configure Performance Tools.

Run Application and Performance Tools.

Simulating a Solution.

Reporting the Problem.

Testing the Solution.

Chapter Summary.

13. Performance Tools: What’s Next?

The State of Linux Tools.

What Tools Does Linux Still Need?

Hole 1: Performance Statistics Are Scattered.

Hole 2: No Reliable and Complete Call Tree.

Hole 3: I/O Attribution.

Performance Tuning on Linux.

Available Source.

Easy Access to Developers.

Linux Is Still Young.

Chapter Summary.

Appendix A. Performance Tool Locations.

Appendix B. Installing oprofile.

Fedora Core 2 (FC2).

Enterprise Linux 3 (EL3).

SUSE 9.1.

Index.

Readers learn to use Linux's rich set of performance tools to make their applications run better.

° Readers learn how to find and remove performance bottlenecks and increase the performance of Linux applications.

° Useful format -- Reader learns tool's purpose, the tool's options, than a hands-on example of how to use the tool.

° Author is key -- enhanced the industry standard and established benchmarks for greater performance.

Phillip G. Ezolt has nearly a decade's experience optimizing Linux and Unix systems. For six years, he ported and designed Linux performance tools for Compaq's Alpha performance group. As Compaq's primary representative to the SPEC CPU subcommittee, he helped shape SPEC CPU 2000 and successor CPU benchmarks. Ezolt is known throughout the industry for his expertise in teaching Linux performance optimization to developers and administrators.


© Copyright Pearson Education. All rights reserved.

Your opinions count

Be the first to review this product. Write your review now.