I/O Tracing - Oracle® Solaris Studio 12.4: Performance Analyzer

Oracle^® Solaris Studio 12.4: Performance Analyzer

Exit Print View

» ...Documentation Home » Oracle Solaris Studio 12.4 Information Library » Oracle^® Solaris Studio 12.4: ... » Understanding Performance Analyzer and Its Data » Interpreting Performance Metrics » I/O Tracing

Updated: January 2015

Oracle^® Solaris Studio 12.4: Performance Analyzer

Document Information

Using This Documentation

Chapter 1 Overview of Performance Analyzer

Chapter 2 Performance Data

Chapter 3 Collecting Performance Data

Chapter 4 Performance Analyzer Tool

Chapter 5 er_print Command-Line Performance Analysis Tool

Chapter 6 Understanding Performance Analyzer and Its Data

How Data Collection Works

Experiment Format

Recording Experiments

Interpreting Performance Metrics

Clock Profiling

Hardware Counter Overflow Profiling

Dataspace Profiling and Memoryspace Profiling

Synchronization Wait Tracing

Call Stacks and Program Execution

Mapping Addresses to Program Structure

Load Objects and Functions

Aliased Functions

Non-Unique Function Names

Static Functions From Stripped Shared Libraries

Fortran Alternate Entry Points

Cloned Functions

Inlined Functions

Compiler-Generated Body Functions

Outline Functions

Dynamically Compiled Functions

<Unknown> Function

OpenMP Special Functions

<JVM-System> Function

<no Java callstack recorded> Function

<Truncated-stack> Function

<Total> Function

Functions Related to Hardware Counter Overflow Profiling

Mapping Performance Data to Index Objects

Mapping Performance Data to Memory Objects

Mapping Data Addresses to Program Data Objects

Data Object Descriptors

Chapter 7 Understanding Annotated Source and Disassembly Data

Chapter 8 Manipulating Experiments

Chapter 9 Kernel Profiling

Language:

I/O Tracing

The Collector records tracing data for calls to the standard I/O routines and all I/O system calls.

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices