Re: HPCs for DRAM

Dimitris Ganosis <[email protected]>
Newsgroups gmane.linux.oprofile
Message-ID <CAKjSCTXHBPn4CdsJXcJGUy+f1=1gSM5EvTQ+H3-Yjbc-48aH9A@mail.gmail.com>
PS. The ideal would be to distinguish memory bandwidth and memory capacity
like MEMORY_BW_READS
<https://yunmingzhang.wordpress.com/2015/07/22/measure-memory-bandwidth-using-uncore-counters/>
but it's not available, at least with this name, in my machine.

On 18 June 2016 at 15:29, Dimitris Ganosis <[email protected]>
wrote:

> I run an Intel(R) Xeon(R) CPU E5520 @ 2.27GHz and follow, apart from perf
> list, this list
> <http://oprofile.sourceforge.net/docs/intel-corei7-events.php>for the
> available counters.
> Based on Linux perf events Event Sources
> <http://www.brendangregg.com/perf.html> I expected that counters like
>
> MEM_STORE_RETIRED and MEM_LOAD_RETIRED
>
> would capture only DRAM's activity. I mean that if I don't use DRAM it's
> bizarre to me to see these counters have the same trend with CPI and other
> cpu counters. I run a cpu intensive benchmark which does not use DRAM, as I
> could see from htop, and these two counters followed the same trend, in the
> graph that I created later, with almost all the other counters. So, my
> question is if there are any counters which are "triggered" only when I use
> DRAM?
> Like the IO_TRANSACTIONS which is triggered only when I have I/Os.
> Thank you!
>

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine

_______________________________________________
oprofile-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oprofile-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.