The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Cell/B.E. SDK 3.0 tools, Part 1: Using performance tools

Explore a practical example on the use of performance tools with the SDK 3.0

Gad Haber (gadi@us.ibm.com), Senior Architect, IBM Japan

Dr. Gad Haber joined the IBM Haifa Labs in 1993 as a research staff member in the area of performance analysis and post-link optimization. He managed the Performance Analysis and Optimization Technologies (PAOT) group until 2006, and he is currently involved with promoting the Cell/B.E. performance tools in the IBM Austin Labs. Dr. Haber works in the IBM Systems and Technology Group in Enterprise Systems Development.

Summary: This introductory tutorial, designed as a companion for the IBM SDK for Multicore Acceleration, Version 3.0 (otherwise known as the Cell Broadband Engine® SDK), teaches you how to use five performance tools that reside in the SDK 3.0: OProfile, Cell Performance Counter, Performance Debugging Tool, the PDT Trace Reader, and FDPR-Pro. The Visual Performance Analyzer, available separately, is also highlighted.

Date: 08 Apr 2008
Level: Introductory
PDF: A4 and Letter (1063 KB | 30 pages)Get Adobe® Reader®

Activity: 29603 views
Comments:

Introduction

This tutorial explores a practical, hands-on example on the use of performance tools, explaining how to collect proper information and how to access relevant visualization features. In this tutorial, you will analyze an example of a FFT16M application.

The example application for analysis is the FFT16M application that can be found in the Cell/B.E. SDK 3.0 demos bundle /opt/cell/sdk/src/demos/FFT16M. This hand-tuned application performs a four-way SIMD single-precision complex FFT on an array of size 16,777,216 elements. The two available command options are:

Old usage: fft <ncycles> <printflag>
New usage: fft <ncycles> <printflag> [<log2_spus> <numa_flag> <largepage_flag>]

The old usage assumes that log2_spus is 3, numa_flag is 0, and largepage_flag is 1. Also:

If numa_flag equals 1, then numa is used.
If largepage_flag equals 1, then large pages are used.

(When you get to the section Create and work with trace data, you will see that the newer format was used to collect some of the traces in this section.)