On Sun, 2018-11-04 at 20:36 -0800, John Reiser wrote:
> > What techniques can we employ to speed things up (whilst retaining most of
> > the value)?
> The memcheck option --expensive-definedness-checks= already defaults to 'no'.
Note that it defaults to 'auto' in 3.14.
> Specifying --redzone-size=8 might save 16 bytes of memory for each allocation,
> which helps if there are many small allocations. But default --alignment=16
> is required for common SSE2 instructions [used by other glibc routines on the
> blocks,
> etc.], and the redzone is not the only per-block overhead (see
> --keep-stacktraces=
> and --num-callers=), so experimentation may be required.
>
> If all you care about is memory leaks, then experiment with
> --undef-value-errors=no
> and even non-valgrind tools [such as mtrace (malloc trace)] that are
> specialized
> for detecting leaks.
You might look at the FOSDEM presentation
'Tuning Valgrind for your Workload
Hints, tricks and tips to effectively use Valgrind on small or big
applications'
https://archive.fosdem.org/2015/schedule/event/valgrind_tuning/
for other suggestions.
Philippe
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
