On Thu, 2013-04-18 at 08:50 -0700, Brian Budge wrote: > Hi Paul. I am at <20% of memory use. I should also note that I > followed Julian's advice for increasing vg_n_segments and memory size > to 128 GB. > > Does valgrind itself do anything multithreaded? My program uses all > cores on the machine at various stages of the program running. But my > understanding was that it was always serialized while running > memcheck. In fact, any tool is (almost fully) serialising the execution: there is only one thread that can "execute" code. the only parallelism is with the threads that are executing a system call.
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 ------------------------------------------------------------------------------ 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
