< prev index next >

src/jdk/nashorn/internal/codegen/OptimisticTypesPersistence.java

Print this page
rev 1358 : 8067636: ant javadoc target is broken
Reviewed-by: hannesw, lagergren

@@ -59,11 +59,11 @@
 import jdk.nashorn.internal.runtime.Source;
 import jdk.nashorn.internal.runtime.logging.DebugLogger;
 import jdk.nashorn.internal.runtime.options.Options;
 
 /**
- * Static utility that encapsulates persistence of type information for functions compiled with optimistic
+ * <p>Static utility that encapsulates persistence of type information for functions compiled with optimistic
  * typing. With this feature enabled, when a JavaScript function is recompiled because it gets deoptimized,
  * the type information for deoptimization is stored in a cache file. If the same function is compiled in a
  * subsequent JVM invocation, the type information is used for initial compilation, thus allowing the system
  * to skip a lot of intermediate recompilations and immediately emit a version of the code that has its
  * optimistic types at (or near) the steady state.

@@ -75,10 +75,11 @@
  * cleans up the directory periodically on a separate thread. It is run after some delay after a new file is
  * added to the cache. The default delay is 20 seconds, and can be set using the
  * {@code nashorn.typeInfo.cleanupDelaySeconds} system property. You can also specify the word
  * {@code unlimited} as the value for {@code nashorn.typeInfo.maxFiles} in which case the type info cache is
  * allowed to grow without limits.
+ * </p>
  */
 public final class OptimisticTypesPersistence {
     // Default is 0, for disabling the feature when not specified. A reasonable default when enabled is
     // dependent on the application; setting it to e.g. 20000 is probably good enough for most uses and will
     // usually cap the cache directory to about 80MB presuming a 4kB filesystem allocation unit. There is one
< prev index next >