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/messages/LocalDBBackendCfgDefn.properties | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn.properties index 6b22df2..da4fae6 100644 --- a/opends/src/admin/messages/LocalDBBackendCfgDefn.properties +++ b/opends/src/admin/messages/LocalDBBackendCfgDefn.properties @@ -34,7 +34,7 @@ property.db-evictor-max-threads.synopsis=Specifies the maximum number of threads in the eviction thread pool. property.db-evictor-max-threads.description=Specifies the maximum number of threads in the eviction thread pool. These threads help keep memory usage within cache bounds, offloading work from application threads. db-evictor-core-threads, db-evictor-max-threads and db-evictor-keep-alive are used to configure the core, max and keepalive attributes for the eviction thread pool. property.db-evictor-nodes-per-scan.synopsis=Specifies the number of Btree nodes that should be evicted from the cache in a single pass if it is determined that it is necessary to free existing data in order to make room for new information. -property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is 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 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. +property.db-evictor-nodes-per-scan.description=Changes to this property do not take effect until the backend is 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 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, 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. property.db-log-file-max.synopsis=Specifies the maximum size for a database log file. property.db-logging-file-handler-on.synopsis=Indicates whether the database should maintain a je.info file in the same directory as the database log directory. property.db-logging-file-handler-on.description=This file contains information about the internal processing performed by the underlying database. -- Gitblit v1.10.0