|
From: Nicholas N. <n.n...@gm...> - 2010-12-06 22:32:54
|
On Tue, Dec 7, 2010 at 7:59 AM, Bruce Merry <bm...@gm...> wrote: > > The intended use is to be able to visually identify poor memory access > patterns. Cachegrind is all well and good for telling you that one > small area of code is hammering the cache, but there are a lot of > things it doesn't show so clearly. For example, code that simply has > to iterate across megabytes of data but has a nice linear access > pattern will show up much hotter in cachegrind than code that touches > one byte in each of a few hundred cache lines, even though the latter > is the only one you can do much about. I've already used it to spot > several places where data structure layout can be improved in a > performance-critical application. Fair enough, I can believe that would be useful. > Perhaps at this stage a more appropriate way to advertise this to > interested parties would be with a link on > http://valgrind.org/downloads/variants.html? Obviously I'd need to > actually write a web page for it to link to first. Yes, I'd be happy to put a link there once you have something to link to. Nick |