Some Profiler Work

1
Some Profiler Work

• Jim Kowalkowski

2
Motivations

• For spending some time recently on this
• Check performance of CMS simulation code
• Create call traces from LQCD MILC code to learn
  what it is doing
• Check performance of LQCD MILC code to see if
  certain routines are taking any time
• Looking at some R/ROOT code with Adam
• For creating a tool (recalled from a while back)
• Reports names from static dynamic libraries.
• Runtime instrumentation
• Low overhead
• Call path analysis (which module is causing
  trouble)

3
Recent Activities

• Got a demo of Linux version of Rationals
  PurifyPlus performance analysis tool
• Use is like Purify runtime instrumentation
• Produced information looks good looks like a
  nice tool
• Slow to run (like Purify)
• http//www-306.ibm.com/software/awdtools/purifyplu
  s/unix/features
• Looked at CallGrind (Valgrind tool)
• Trouble compiling visualization tools (web
  pictures look nice)
• Text output looks interesting
• Slow to run
• http//kcachegrind.sourceforge.net/cgi-bin/show.cg
  i/KcacheGrindIndex
• Upgraded my simple tool
• Recent version of gcc
• Still having trouble decoding stack under certain
  conditions
• Attempted to use Linux RT signals (results not
  good)
• Embedded into CMS framework service for testing

4
Other

• Wished I had time to look at recent version of
  other tools I tried in the past
• VTune from Intel
• OProfile
• Simics x86 emulator that runs Linux