On Tue, Feb 23, 2016 at 10:21:21PM +0000, Rodriguez Betancourt, Esteban wrote: > During our tests with OVSDB we found out that memory allocation is > used intensively by the server, so we thought that using a different > memory allocator could increase the performance. We tried jemalloc > and the performance gain was between 20% and 40%. > > This patch would allow anyone to enable jemalloc on their systems > in case you want to try out this memory allocator. > > The patch adds the --enable-jemalloc flag to link ovsdb-server with jemalloc > instead of the default memory allocator. This can improve the OVSDB > Server performance under certains loads. > > Signed-off-by: Esteban Rodriguez Betancourt <esteb...@hpe.com>
I've been thinking about this for a while. It's nice that jemalloc can speed up ovsdb-server, and I'm happy to find that out. Given that, I'm also happy to encourage users to use jemalloc. But this patch seems like a bit of overkill. In the end, I guess I have a couple of questions: Why is it worthwhile to add a new configure flag, instead of just encouraging users to run "./configure LIBS=-ljemalloc"? Why is jemalloc only suitable for ovsdb-server? Thanks, Ben. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
