From e4e9b2ebc7d41715fc0c0c8ba07f897fe63a688e Mon Sep 17 00:00:00 2001
From: boli <boli@localhost>
Date: Wed, 16 Jan 2008 23:19:50 +0000
Subject: [PATCH] This fix removes the option to use nanosecond etime resolution as a JVM property. It is now a global configuration attribute. Due to the 10% throughput decrease I saw when using System.nanoTime, the default still uses System.currentTimeMillis to timestamp operations. System.nanoTime will only be used when the ds-cfg-etime-resolution attribute is set to nano-seconds.
---
opends/src/server/org/opends/server/core/CoreConfigManager.java | 12 +++++-------
1 files changed, 5 insertions(+), 7 deletions(-)
diff --git a/opends/src/server/org/opends/server/core/CoreConfigManager.java b/opends/src/server/org/opends/server/core/CoreConfigManager.java
index f9fa411..8d5ca58 100644
--- a/opends/src/server/org/opends/server/core/CoreConfigManager.java
+++ b/opends/src/server/org/opends/server/core/CoreConfigManager.java
@@ -22,7 +22,7 @@
* CDDL HEADER END
*
*
- * Portions Copyright 2006-2007 Sun Microsystems, Inc.
+ * Portions Copyright 2006-2008 Sun Microsystems, Inc.
*/
package org.opends.server.core;
import org.opends.messages.Message;
@@ -42,12 +42,7 @@
import org.opends.server.admin.std.server.RootCfg;
import org.opends.server.admin.server.ServerManagementContext;
import org.opends.server.config.ConfigException;
-import org.opends.server.types.AcceptRejectWarn;
-import org.opends.server.types.ConfigChangeResult;
-import org.opends.server.types.InitializationException;
-import org.opends.server.types.Privilege;
-import org.opends.server.types.ResultCode;
-import org.opends.server.types.WritabilityMode;
+import org.opends.server.types.*;
import static org.opends.messages.ConfigMessages.*;
@@ -357,6 +352,9 @@
{
DirectoryServer.setWorkflowConfigurationMode(newMode);
}
+
+ AbstractOperation.setUseNanoTime(globalConfig.getEtimeResolution() ==
+ GlobalCfgDefn.EtimeResolution.NANO_SECONDS);
}
--
Gitblit v1.10.0