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/util/ServerConstants.java | 10 +---------
1 files changed, 1 insertions(+), 9 deletions(-)
diff --git a/opends/src/server/org/opends/server/util/ServerConstants.java b/opends/src/server/org/opends/server/util/ServerConstants.java
index eb68b8f..6c047fb 100644
--- a/opends/src/server/org/opends/server/util/ServerConstants.java
+++ b/opends/src/server/org/opends/server/util/ServerConstants.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.util;
@@ -2770,14 +2770,6 @@
"org.opends.server.UseLastKnownGoodConfiguration";
- /**
- * The name of the system property that can be used to configure the
- * server to report etimes in nanoseconds instead of milliseconds.
- */
- public static final String PROPERTY_ETIME_NANO =
- "org.opends.server.etime.nano";
-
-
/**
* The column at which to wrap long lines of output in the command-line tools.
--
Gitblit v1.10.0