On Tue, 2013-04-23 at 13:08 -0700, Brian Budge wrote:
> Some prototyping was done of a non serialised valgrind. > See https://bugs.kde.org/show_bug.cgi?id=301830 > and the MTV branch in svn. > This prototype is not usable in its current state: only the > none tool was used. There are still many thread unsafe things. > The performance of the memcheck data structures is a.o. a > difficult > problem to look at. > > Philippe > > > Hi Philippe - > > > I can definitely understand that :) I wasn't really suggesting that > it should do so (though, of course, any performance improvement would > be great). I was more just confused that memcheck was using so many > cores concurrently. Yes, it is not very understandable, unless you have a lot of threads, with many of them executing (heavy) system calls. (but I am still amazed that you could obtain something like 1000% of cpu). Philippe ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
