Change installing documentation to suggest to use
jemalloc memory allocator.
This memory allocator showed great performance gains
when used at ovsdb-server and other components.
Signed-off-by: Esteban Rodriguez Betancourt <esteb...@hpe.com>
---
.travis.yml | 3 +++
INSTALL.md | 7 +++++++
2 files changed, 10 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index 2b262e4..6618073 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -10,6 +10,8 @@ addons:
- gcc-multilib
- libssl-dev
- llvm-dev
+ - libjemalloc1
+ - libjemalloc-dev
before_install: ./.travis/prepare.sh
@@ -30,6 +32,7 @@ env:
- KERNEL=3.14.60
- KERNEL=3.12.53
- KERNEL=3.10.96
+ - TESTSUITE=1 LIBS=-ljemalloc
script: ./.travis/build.sh $OPTS
diff --git a/INSTALL.md b/INSTALL.md
index 9dadcee..fa7b40e 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -247,6 +247,13 @@ Here is an example:
`% mkdir _gcc && (cd _gcc && ../configure CC=gcc)`
`% mkdir _clang && (cd _clang && ../configure CC=clang)`
+Under certains loads the ovsdb-server and other components perform
+better when using the jemalloc memory allocator, instead of the GLibC
+memory allocator.
+
+If you wish to link with jemalloc add it to LIBS:
+
+ `% ./configure LIBS=-ljemalloc`
Building the Sources
--------------------
--
1.9.1
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
