[Zeek-Dev] Compiling with --coverage flag
robin at corelight.com
Tue Jun 11 07:09:17 PDT 2019
interesting, could you send some numbers on the kind of improvements
you saw, and on what traffic?
On Mon, Jun 10, 2019 at 11:30 -0700, Jim Mellander wrote:
> I've been tinkering with the --coverage flag to capture runtime statistics
> which can then be used to compile zeek with branch prediction hints. My
> preliminary tests indicate a substantial performance increase, enough to
> justify engaging the zeek community.
> I noticed that the configure script includes --enable-coverage, which
> doesn't quite do what I want, as it compiles with debug support. and I'm
> most interested in optimization for production use.
> In brief, I've been testing:
> ./configure --enable-coverage
> for the initial compile, then run against pcaps and live traffic, and use
> that profiling data to recompile:
> CFLAGS=’-fprofile-use -fprofile-correction -flto’ CXXFLAGS=’-fprofile-use
> -fprofile-correction -flto’ ./configure
> with a substantial performance boost against a regular compile (can
> additionally do --build-type=Release for compiling with -O3 flag).
> Has anyone else tinkered with this? - I would be happy to elaborate, and
> discuss with others.
> zeek-dev mailing list
> zeek-dev at zeek.org
Robin Sommer * Corelight, Inc. * robin at corelight.com * www.corelight.com
More information about the zeek-dev