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_zh_TW.properties | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_TW.properties b/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_TW.properties index bfe92a7..2fc3d6c 100644 --- a/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_TW.properties +++ b/opends/src/admin/messages/LocalDBBackendCfgDefn_zh_TW.properties @@ -28,7 +28,7 @@ property.db-evictor-lru-only.synopsis=Indicates whether the database should evict existing data from the cache based on an LRU policy (where the least recently used information will be evicted first). property.db-evictor-lru-only.description=If set to "false", then the eviction keeps internal nodes of the underlying Btree in the cache over leaf notes, even if the leaf nodes have been accessed more recently. This may be a better configuration for databases in which only a very small portion of the data is cached. 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, 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-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