Software Tuning, Performance Optimization & Platform Monitoring
Discussion around monitoring and software tuning methodologies, Performance Monitoring Unit (PMU) of Intel microprocessors, and platform monitoring
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.

Profiling memory accesses - which counters overlap with which?

Adrian_C_1
Beginner
105 Views

Hi!

I have some Perl scripts that implement some of the top-level vtune profiling for sandy bridge (and SB Xeon.)

Noticably:

* % cycles spent LLC miss: ~ 53%

* % cycles spent doing DTLB walks: ~ 10%

* % cycles spent accessing data modified by another core: ~ 3.5%

My question: when doing DTLB walks (DTLB_LOAD_MISSES.WALK_DURATION) and cycles spent hit'ing on data modified by another core (MEM_LOAD_UOPS_LLC_HIT_RETIRED.XSNP_HITM) - do these overlap in any way with the LLC_MISS (ie memory access - MEM_LOAD_UOPS_MISC_RETIRED.LLC_MISS) ? Partially overlap? Don't overlap at all?

I'm especially interested in whether the DTLB walks count towards MEM_LOAD_UOPS_MISC_RETIRED.LLC_MISS.

Thanks!

-adrian

0 Kudos
0 Replies
Reply