Dynamic Tracing and Profiling - Red Hat People

More documents

Recommendations

Info

Events to Measure ● Processor specific ● Many events to choose from ● Can sample between 2 <strong>and</strong> 8 events concurrently ● ophelp lists available events ● Select events in the “opcontrol setup” ● Initially timebased samples most useful: ● PPro/PII/PIII/AMD: CPU_CLK_UNHALTED ● P4: GLOBAL_POWER_EVENTS ● IA64: CPU_CYCLES ● TIMER_INT (fallback profiling mechanism) default 8
Events to Measure (cont.) ● Performance monitoring hardware can provide additional kinds of sampling ● Pipeline stalls/serializing instructions ● Branch mispredictions ● Cache misses ● TLB misses 9
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: OProfile Database ● All the data
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 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

Create successful ePaper yourself

Delete template?

Save as template?