Dynamic Tracing and Profiling - Red Hat People

More documents

Recommendations

Info

Oprofile Limitations ● Requires root access to set up <strong>and</strong> control oprofile ● Complicated set of architecturespecific events ● Sampling imprecision ● Simpleminded analysis tools 20
Events Available to Monitor ● OProfile uses time based events at the default event ● Timebased sampling focuses attentions correctly ● Would like to narrow down the cause of slowdown: ● Processors have specific hardware events ● Hardware events vary between processors ● ophelp will list the available events with short descriptions 21
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 and 12: Shared Library and Kernel Samples
Page 13 and 14: Data Collection from OProfile RPM B
Page 15 and 16: Procedure (cont) ● When OProfile
Page 17 and 18: More Detailed Look at Executables
Page 19: Look at Compiler executable $ oprep
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

Create successful ePaper yourself

Delete template?

Save as template?