Dynamic Tracing and Profiling - Red Hat People

More documents

Recommendations

Info

Mapping OProfile Data to Source ● If gdb can debug code, e.g. get line numbers, then OProfile can map information back to source. ● "g" used information to map back to lines ● Per function view (opreport l) doesn't use debug symbols ● Debuginfo RPMs now being built by default, allow characterization of executables in stock RPMs 12
Data Collection from OProfile RPM Build ● Find out where the process spends time during a build of the OProfile RPM ● Environment: ● Processor: Intel Pentium M 1.6GHz ● Memory: 1536MB RAM ● Disc: ● hda: Hitachi Travelstar 5K80 family, ATA DISK drive ● Running RHEL5.3 13
Page 1 and 2: Performance Monitoring and Tuning w
Page 3 and 4: Performance Tuning Issues: Software
Page 5 and 6: OProfile Introduction ● Started a
Page 7 and 8: OProfile Database ● All the data
Page 9 and 10: Events to Measure (cont.) ● Perfo
Page 11: Shared Library and Kernel Samples
Page 15 and 16: Procedure (cont) ● When OProfile
Page 17 and 18: More Detailed Look at Executables
Page 19 and 20: Look at Compiler executable $ oprep
Page 21 and 22: Events Available to Monitor ● OPr
Page 23 and 24: Analyzing Kernel Modules ● OProfi
Page 25 and 26: Processor Hardware Optimizations
Page 27 and 28: ● Poor spatial locality: Cache Pr
Page 29 and 30: ICache Output $ opreport l sess
Page 31 and 32: Dcache Output $ opreport l sessio
Page 33 and 34: Pipelined, Superscalar, and OOO Exe
Page 35 and 36: Branch Prediction Problems ● Bran
Page 37: Branch Results $ opreport l sessi

Dynamic Tracing and Profiling - Red Hat People

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?