13.07.2015 Views

Intel® 64 and IA-32 Architectures Optimization Reference Manual

Intel® 64 and IA-32 Architectures Optimization Reference Manual

Intel® 64 and IA-32 Architectures Optimization Reference Manual

SHOW MORE
SHOW LESS
  • No tags were found...

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

USING PERFORMANCE MONITORING EVENTSStores RetiredAll WCB EvictionsWCB Full EvictionsTable B-4. Performance Metrics - Memory (Contd.)Metric Description Event Name or MetricExpressionNumber of retiredstored operations thatwere tagged at frontendThis stat is often usedin a per-instructionratio.Number of times a WCbuffer evictionoccurred due to anycauseThis can be used todistinguish <strong>64</strong>-KBytealiasing cases thatcontribute moresignificantly toperformance penalty,for example: storesthat are <strong>64</strong>-KBytealiased.A high count of thismetric when there isno significantcontribution due towrite combining bufferfull condition mayindicate the abovesituation.Number of times a WCbuffer evictionoccurred when all ofWC buffers allocatedFront_end_event; setthe following front endtag: Memory_storesWC_bufferWC_bufferEvent Mask ValueRequiredNBOGUSWCB_EVICTSWCB_FULL_EVICTNOTES:1. A memory reference causing <strong>64</strong>K aliasing conflict can be counted more than once in this stat. Theresulting performance penalty can vary from unnoticeable to considerable. Some implementationsof the Pentium 4 processor family can incur significant penalties from loads that alias to precedingstores.2. Currently, bugs in this event can cause both overcounting <strong>and</strong> undercounting by as much as a factorof 2.B-16

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!