From 54e86875b84cd00492ec403c67339d1520117c50 Mon Sep 17 00:00:00 2001
From: Ludovic Poitou <ludovic.poitou@forgerock.com>
Date: Thu, 08 Dec 2011 11:02:40 +0000
Subject: [PATCH] Fix for OPENDJ-379. Improve description for the db-evictor-nodes-per-scan configuration parameter.

---
 opends/src/admin/defn/org/opends/server/admin/std/LocalDBBackendConfiguration.xml |   14 +++++++++-----
 1 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/opends/src/admin/defn/org/opends/server/admin/std/LocalDBBackendConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/LocalDBBackendConfiguration.xml
index ff6683f..a114369 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/LocalDBBackendConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/LocalDBBackendConfiguration.xml
@@ -537,13 +537,17 @@
       restarted. It is recommended that you also change this property
       when you set db-evictor-lru-only to false. This setting controls
       the number of Btree nodes that are considered, or sampled, each
-      time a node is evicted. A setting of 100 often produces good
+      time a node is evicted. A setting of 10 often produces good
       results, but this may vary from application to application. The
       larger the nodes per scan, the more accurate the algorithm.
-      However, setting it too high is detrimental; the need to consider
-      larger numbers of nodes for each eviction may delay the completion
-      of a given database operation, which will impact the response time
-      of the application thread.
+      However, don't set it too high. When considering larger numbers of
+      nodes for each eviction, the evictor may delay the completion of a
+      given database operation, which impacts the response time of the
+      application thread. In JE 4.1 and later, setting this value too high
+      in an application that is largely CPU bound can reduce the
+      effectiveness of cache eviction. It's best to start with the default
+      value, and increase it gradually to see if it is beneficial for your
+      application.
     </adm:description>
     <adm:requires-admin-action>
       <adm:component-restart />

--
Gitblit v1.10.0