IBM®
Skip to main content
    Country/region [select]      Terms of use
 
 
    
     Home      Products      Services & solutions      Support & downloads      My account     
 
developerworks > My developerWorks >  Dashboard > Linux for Power Architecture > ... > Performance > Performance Problem Determination
developerWorks
Log In   View a printable version of the current page.
Overview Connect Spaces Forums Wikis
Performance Problem Determination
Added by wburos, last edited by wburos on May 05, 2009  (view change)
Labels: 
(None)

Performance "problems" come in many flavors. Here we begin capturing real-life problem determination examples and techniques, showing how easy it can be to drive towards understanding and fixing the root-cause issues, or in many cases simply to better understand the performance comparisons being made.

Contents


Gathering basic performance data

For details on the initial data to consider, see gathering basic performance data .


Who's doing a "stat" on a file?

See Using SystemTap for stat for an example of looking for which process is stat'ing a file.


Who's sending so many SIGUSR2 signals?

See SystemTap SIGUSR2 Tracing. This page explains how to easily determine the source of software-generated signals, which in this example were causing a system to become 100% CPU busy.


Docs Gather Performance Data (Linux for Power Architecture)
Docs Gathering basic performance data (Linux for Power Architecture)
Docs SystemTap SIGUSR2 tracing (Linux for Power Architecture)
Docs Using SystemTap for stat (Linux for Power Architecture)


 
    About IBM Privacy Contact