Intel® Performance Bottleneck Analyzer

Download now


Introduction :
The Intel® Performance Bottleneck Analyzer (Intel® PBA) framework seeks to relate knowledge of static assembly and latest performance monitoring techniques to automatically find and prioritize architectural bottlenecks for the Intel® Core™ Processor Family and the Intel® Atom™ processor. The bottlenecks which cannot be explained are prioritized and tagged for further analysis. To accomplish this goal, the tool utilizes performance monitoring data to recreate the hottest paths of instruction execution through a binary. The recreated paths of execution are then passed through an analysis which combines searches for well known code generation issues with knowledge of hundreds of the performance monitoring events. The toolset is designed, written, and maintained by performance engineers who work in the field to resolve performance bottlenecks every day. All features enabled in the toolset have already been used to study and identify performance opportunities on software.

New in Version 4.0.1:
  • XED disassembler bug fix.
  • Precise instruction distribution bug fix.
  • Last branch record bug on Atom is fixed.
  • Two bug fixes in instruction look-up.
Prerequisites :
  • Java* runtime (JRE) version 6 Update 10 or greater
  • Intel® VTune™ Amplifier XE – needed for parsing sampling collector data. Get it here: Intel® VTune™ Amplifier XE
  • SEP – for data collection. This is packaged with Intel® Performance Tuning Utility (Intel® PTU) software. You must download Intel PTU 4.0 Update 5 to use all the latest analysis capabilities of PBA. Get Intel PTU here: Intel® Performance Tuning Utility
Installation, Setup, and Running the Framework :
More detailed information on installation, setup, and running of the Intel® PBA framework and its capabilities can be found in the user manual. Get the user manual here: Intel® Performance Bottleneck Analyzer User Manual

Known Issues or Limitations :
Please refer to the user manual for all current issues and limitations.

* - Other names and brands may be claimed as the property of others.
For more complete information about compiler optimizations, see our Optimization Notice.
There are downloads available under the What If Pre-Release License Agreement license. Download Now


Zhoulong J. (Intel)'s picture

Hi, if I want to add the module which is jitted code, like after running the sep, there will be a file name localhost.(pid).jit file, how can i add it to analyze? I use : full_analyze localhost.(pid).jit sep.tb6 SLM, it seems it can't recognize the jit file. Thanks very much

Alan Bain's picture

The install instruction for PBA require PTU to be installed, but the PTU link now says that this is an EOL product and replaced by Vtune. This isn't a problem as I have Vtune 2013 licence already, but it's not clear how to make this work with xIF.

Osvaldo Galicia Gasperin's picture

I is a good tool it is very helpful on low-end systems as in Servers , but its dependency of the Intel® VTune™ Amplifier XE it makes difficult their use. Maybe if the next release it is and independent application i could be a hit.

Thank you for
let me participate

anonymous's picture

whatif member

anonymous's picture

This tool has been immensefully helpful for my new Atom, which suffers heavily under Win7. Thanks!

Rajshree Chabukswar (Intel)'s picture

We have noticed on several customer systems that the tool may fail to load the sampling data. If this issue is seen, please make sure that the only license file you have in path is for VTune Amplifier XE mentioned in the prerequisites above. Having older versions of VTune licenses in path may cause failure to run analysis.


Michael Chynoweth (Intel)'s picture

We have logged Jeff's bug (1st comment) and will put out a fix in our patch due out in a month. In the meantime the procedure Jeff has provided is a good workaround for 32-bit WinXP users who run into the XED issue.
Jeff: Thanks for the bug and the workaround!



anonymous's picture

Using this tool on 32 bit Windows XP I had a problem where module disassembly would fail:

Running XED for disassembly on raw text section
ERROR: Dump file generated for Receiver is invalid.

This turned out to be due to the version of xed.exe not being compatible with 32 bit XP. Running xed.exe directly caused a Windows error message to appear that said: "The procedure entry point Wow64DisableWow64FsRedirection could not be located in the dynamic link library KERNEL32.dll".

I did a google for "XED dissasembler" and found I downloaded this using the "DOWNLOAD WINDOWS IA-32 and Intel64" link and a got file called sde-ivb-external-3.88-2010-12-21-win-intel64-and-ia32.tar.bz2 file. I extracted this and in it was a xed.exe. I used this to replace the version in the Performance Bottleneck Analyzer and after this everything worked fine.

Add a Comment

Have a technical question? Visit our forums. Have site or software product issues? Contact support.