that decision to the specific
> developers.
>
> Thanks,
> Esteban
>
> -Original Message-
> From: Ben Pfaff [mailto:b...@ovn.org]
> Sent: lunes, 14 de marzo de 2016 11:10
> To: Rodriguez Betancourt, Esteban
> Cc: dev@openvswitch.org
> Subject: Re: [ovs-dev] [PAT
the specific
developers.
Thanks,
Esteban
-Original Message-
From: Ben Pfaff [mailto:b...@ovn.org]
Sent: lunes, 14 de marzo de 2016 11:10
To: Rodriguez Betancourt, Esteban
Cc: dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH] Add --enable-jemalloc argument to build
On Tue, Feb 23,
On Tue, Feb 23, 2016 at 10:21:21PM +, 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 p
"dev" wrote on 03/13/2016 03:48:19 AM:
> 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
Hi,
I tested the patch in our scalability test environment, the test case as blow:
- 1000 sandboxes are created
- Each time create 5 lswitches each has 200 lports, that is, 1000 lport in
total, then bind lports one by one to sandboxes randomly
After linked ovsdb-server, ovn-controller with jemal
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 jemal
