You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by ge...@apache.org on 2006/10/06 20:12:33 UTC
svn commit: r453721 - in /incubator/harmony/standard/site:
docs/subcomponents/drlvm/emguide.html xdocs/subcomponents/drlvm/emguide.xml
Author: geirm
Date: Fri Oct 6 11:12:32 2006
New Revision: 453721
URL: http://svn.apache.org/viewvc?view=rev&rev=453721
Log:
HARMONY-1757
EM guide document from our site contains obsolete info
applied and distributed
Modified:
incubator/harmony/standard/site/docs/subcomponents/drlvm/emguide.html
incubator/harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml
Modified: incubator/harmony/standard/site/docs/subcomponents/drlvm/emguide.html
URL: http://svn.apache.org/viewvc/incubator/harmony/standard/site/docs/subcomponents/drlvm/emguide.html?view=diff&rev=453721&r1=453720&r2=453721
==============================================================================
--- incubator/harmony/standard/site/docs/subcomponents/drlvm/emguide.html (original)
+++ incubator/harmony/standard/site/docs/subcomponents/drlvm/emguide.html Fri Oct 6 11:12:32 2006
@@ -263,7 +263,7 @@
<br />
You can use the following command-line option to make EM read its
configuration from the file:<br />
-<code>-Xem <path to configuration file></code>
+<code>-Xem:<path to configuration file></code>
<br />
or <br />
<code>-Dem.properties=<configuration.file.path></code>
@@ -517,35 +517,32 @@
<code>-verbose:em.profiler.PROFILER_NAME</code> dumps only profiler
"<code>PROFILER_NAME</code>" related events.<br />
</p>
- <p>
-<b>Example:</b></p>
- <p>
-For the default EM configuration file, </p>
- <p><code>
+ <p class="example">
+ Example
+ </p>
+ <p class="exampletext">
+For the default EM configuration file,
+<br /><code>
-verbose:em.OPT
-</code> dumps all methods names that are compiled with the
-<code>OPT</code> JIT. According to the configuration details, these methods
+</code><br /> dumps all methods names that are compiled with
+Jitrino.OPT. According to the configuration details, these methods
are hot methods.
</p>
- <p>Alternatively, you can get almost the same information by using
+ <p class="exampletext">Alternatively, you can get almost the same information by using
the following:
-</p>
- <p><code>
+<br /><code>
-verbose:em.profiler.JET_DPGO_PROFILE
-</code> additionally dumps information about hot method profiles.
+</code><br /> additionally dumps information about hot method profiles.
</p>
- <p><b>Examples of output:</b>
-</p>
- <p><code>
+ <p class="example">Examples of output:</p>
+ <br />
+ <code>
C:\tools\decapo>c:\tools\harmony0706\bin\java.exe -verbose:em.OPT -jar dacapo-beta051009.jar xalan<br />
EM: recompile start:[OPT n=1] java/io/ByteArrayOutputStream::write(I)V<br />
EM: recompile done:[OPT n=1] java/io/ByteArrayOutputStream::write(I)V<br />
EM: recompile start:[OPT n=2] java/lang/String::hashCode()I<br />
EM: recompile done:[OPT n=2] java/lang/String::hashCode()I<br />
-...
-</code>
-<br />
-<code>
+...<br />
C:\tools\decapo>c:\tools\harmony0706\bin\java.exe -verbose:em.profiler.JET_DPGO_PROFILE -jar dacapo-beta051009.jar xalan<br />
EM: entry-backedge profiler intialized: JET_DPGO_PROFILE entry threshold:10000 backedge threshold:100000 mode:SYNC<br />
EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/io/ByteArrayOutputStream::write(I)V<br />
@@ -556,9 +553,9 @@
EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/charset/Charset::isDigit(C)Z<br />
EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/Buffer::remaining()I<br />
EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/util/HashMap::getModuloHash(Ljava/lang/Object;)I<br />
-...
+... <br />
</code>
-</p>
+ <br />
</td></tr>
@@ -571,29 +568,93 @@
<tr><td>
<p>
-EM has two more hard-coded configurations: '<code>-Xem opt</code>'
- and '<code>-Xem jet</code>'.<br />
-These configuration are almost identical and rely on the Jitrino
-JIT naming convention: any JIT instance with the <code>JET</code>
-prefix in the name is a Jitrino.JET instance.
-</p>
- <p><b>JET Configuration</b></p>
+ DRLVM has several EM configurations supplied in the following files:
+ <code>client.emconf</code> (the default), <code>opt.emconf</code>, <code>jet.emconf</code>,
+ <code>server.emconf</code> and <code>server_static.emconf</code>.<br />
+ The <code>-Xem:opt</code>, <code>-Xem:jet</code> and <code>-Xem:server_static</code>
+ configurations are almost identical and rely on the Jitrino
+ JIT naming convention. This way, any JIT instance with the <code>JET</code>
+ prefix in the name is a Jitrino.JET instance. <br />
+ Another difference in these configurations are options passed to the JIT compiler.
+ </p>
+ <p><i>These configurations have only one JIT and no profile collection or recompilation.</i></p>
+ <p><b>
+ <code>-Xem:jet</code> - the baseline compiler mode configuration</b></p>
<p><pre>
chains=chain1
chain1.jits=JET
JET.file=<path to dll>
</pre></p>
- <p><b>OPT Configuration</b></p>
+ <p><b>
+ <code>-Xem:opt</code> - the client-static mode configuration</b></p>
<p><pre>
chains=chain1
-chain1.jits=OPT
+chain1.jits=CS_OPT
OPT.file=<path to dll>
</pre></p>
- <p>
-These configurations have only one JIT and no profile collection or recompilation.
-</p>
- <p>
-<b>Note:</b> to run VM in the intereter mode, use the <code>-Xint</code>
+ <p><b>
+ <code>-Xem:server_static</code> - the server-static mode configuration</b></p>
+ <p><pre>
+chains=chain1
+chain1.jits=SS_OPT
+OPT.file=<path to dll>
+</pre></p>
+ <br />
+ <p><i>These configurations use recompilation and collect profiles.</i></p>
+ <p><b>
+ <code>-Xem:client</code> - the default configuration, or client dynamic</b></p>
+ <p><pre>
+chains=chain1,chain2
+chain1.jits=JET_CLINIT
+chain2.jits=JET_DPGO,CD_OPT
+
+
+# JET_CLINIT compiles only <clinit> methods, all other methods compiled with JET_DPGO
+# which does entry/backedge instrumentation
+
+chain1.filter=+::<clinit>
+chain1.filter=-
+
+JET_CLINIT.file=<path to dll>
+JET_DPGO.file=<path to dll>
+CD_OPT.file=<path to dll>
+
+#Confuguration of profile collector and recompilation
+JET_DPGO.genProfile=EB_PROF
+EB_PROF.profilerType=EB_PROFILER
+CD_OPT.useProfile=EB_PROF
+
+
+EB_PROF.mode=SYNC
+EB_PROF.entryThreshold=10000
+EB_PROF.backedgeThreshold=100000
+</pre></p>
+ <p><b>
+ <code>-Xem:server</code> - the server mode configuration, or server dynamic</b></p>
+ <p><pre>
+chains=chain1,chain2
+chain1.jits=JET_CLINIT
+chain2.jits=SD1_OPT,SD2_OPT
+
+chain1.filter=+::<clinit>
+chain1.filter=-
+
+JET_CLINIT.file=<path to dll>
+SD1_OPT.file=<path to dll>
+SD2_OPT.file=<path to dll>
+
+# Edge profiler and recompilation parameters
+EDGE_PROF.profilerType=EDGE_PROFILER
+EDGE_PROF.entryThreshold=40000
+EDGE_PROF.backedgeThreshold=150000
+EDGE_PROF.tbsTimeout=10
+EDGE_PROF.tbsInitialTimeout=0
+
+SD1_OPT.genProfile=EDGE_PROF
+SD2_OPT.useProfile=EDGE_PROF
+</pre></p>
+ <p class="note">Note</p>
+ <p class="notetext">To run VM in the intereter mode, use the <code>-Xint</code>
command-line option to override any other EM settings. Currently, DRLVM does
not support the mixed mode of the JIT compiler plus interpreter.
</p>
Modified: incubator/harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml
URL: http://svn.apache.org/viewvc/incubator/harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml?view=diff&rev=453721&r1=453720&r2=453721
==============================================================================
--- incubator/harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml (original)
+++ incubator/harmony/standard/site/xdocs/subcomponents/drlvm/emguide.xml Fri Oct 6 11:12:32 2006
@@ -35,7 +35,7 @@
<br/>
You can use the following command-line option to make EM read its
configuration from the file:<br/>
-<code>-Xem <path to configuration file></code>
+<code>-Xem:<path to configuration file></code>
<br/>
or <br/>
<code>-Dem.properties=<configuration.file.path></code>
@@ -121,7 +121,7 @@
<br/>
Here is a format of all currently supported method filters.
</p><br/>
-<table border="1">
+<table>
<tr>
<td>
<b>Filter Type</b>
@@ -247,36 +247,33 @@
<code>-verbose:em.profiler.PROFILER_NAME</code> dumps only profiler
"<code>PROFILER_NAME</code>" related events.<br/>
</p>
-<p>
-<b>Example:</b></p>
-<p>
-For the default EM configuration file, </p>
-<p><code>
+ <p class="example">
+ Example
+ </p>
+ <p class="exampletext">
+For the default EM configuration file,
+<br/><code>
-verbose:em.OPT
-</code> dumps all methods names that are compiled with the
-<code>OPT</code> JIT. According to the configuration details, these methods
+</code><br/> dumps all methods names that are compiled with
+Jitrino.OPT. According to the configuration details, these methods
are hot methods.
</p>
-<p>Alternatively, you can get almost the same information by using
+ <p class="exampletext">Alternatively, you can get almost the same information by using
the following:
-</p>
-<p><code>
+<br/><code>
-verbose:em.profiler.JET_DPGO_PROFILE
-</code> additionally dumps information about hot method profiles.
+</code><br/> additionally dumps information about hot method profiles.
</p>
-<p><b>Examples of output:</b>
-</p>
-<p><code>
+ <p class="example">Examples of output:</p>
+<br/>
+<code>
C:\tools\decapo>c:\tools\harmony0706\bin\java.exe -verbose:em.OPT -jar dacapo-beta051009.jar xalan<br/>
EM: recompile start:[OPT n=1] java/io/ByteArrayOutputStream::write(I)V<br/>
EM: recompile done:[OPT n=1] java/io/ByteArrayOutputStream::write(I)V<br/>
EM: recompile start:[OPT n=2] java/lang/String::hashCode()I<br/>
EM: recompile done:[OPT n=2] java/lang/String::hashCode()I<br/>
-...
-</code>
-<br/>
-<code>
+...<br/>
C:\tools\decapo>c:\tools\harmony0706\bin\java.exe -verbose:em.profiler.JET_DPGO_PROFILE -jar dacapo-beta051009.jar xalan<br/>
EM: entry-backedge profiler intialized: JET_DPGO_PROFILE entry threshold:10000 backedge threshold:100000 mode:SYNC<br/>
EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/io/ByteArrayOutputStream::write(I)V<br/>
@@ -287,35 +284,102 @@
EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/charset/Charset::isDigit(C)Z<br/>
EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/nio/Buffer::remaining()I<br/>
EM: profiler[JET_DPGO_PROFILE] profile is ready [e:10000 b:0] java/util/HashMap::getModuloHash(Ljava/lang/Object;)I<br/>
-...
+... <br/>
</code>
-</p>
+<br/>
</subsection>
<subsection name="4. More EM Configuration Samples">
-<p>
-EM has two more hard-coded configurations: '<code>-Xem opt</code>'
- and '<code>-Xem jet</code>'.<br/>
-These configuration are almost identical and rely on the Jitrino
-JIT naming convention: any JIT instance with the <code>JET</code>
-prefix in the name is a Jitrino.JET instance.
-</p>
-<p><b>JET Configuration</b></p>
+ <p>
+ DRLVM has several EM configurations supplied in the following files:
+ <code>client.emconf</code> (the default), <code>opt.emconf</code>, <code>jet.emconf</code>,
+ <code>server.emconf</code> and <code>server_static.emconf</code>.<br/>
+ The <code>-Xem:opt</code>, <code>-Xem:jet</code> and <code>-Xem:server_static</code>
+ configurations are almost identical and rely on the Jitrino
+ JIT naming convention. This way, any JIT instance with the <code>JET</code>
+ prefix in the name is a Jitrino.JET instance. <br/>
+ Another difference in these configurations are options passed to the JIT compiler.
+ </p>
+<p><i>These configurations have only one JIT and no profile collection or recompilation.</i></p>
+<p><b>
+ <code>-Xem:jet</code> - the baseline compiler mode configuration</b></p>
<p><pre>
chains=chain1
chain1.jits=JET
JET.file=<path to dll>
</pre></p>
-<p><b>OPT Configuration</b></p>
+<p><b>
+ <code>-Xem:opt</code> - the client-static mode configuration</b></p>
<p><pre>
chains=chain1
-chain1.jits=OPT
+chain1.jits=CS_OPT
OPT.file=<path to dll>
</pre></p>
-<p>
-These configurations have only one JIT and no profile collection or recompilation.
-</p>
-<p>
-<b>Note:</b> to run VM in the intereter mode, use the <code>-Xint</code>
+<p><b>
+ <code>-Xem:server_static</code> - the server-static mode configuration</b></p>
+<p><pre>
+chains=chain1
+chain1.jits=SS_OPT
+OPT.file=<path to dll>
+</pre></p>
+<br/>
+<p><i>These configurations use recompilation and collect profiles.</i></p>
+
+<p><b>
+ <code>-Xem:client</code> - the default configuration, or client dynamic</b></p>
+<p><pre>
+chains=chain1,chain2
+chain1.jits=JET_CLINIT
+chain2.jits=JET_DPGO,CD_OPT
+
+
+# JET_CLINIT compiles only <clinit> methods, all other methods compiled with JET_DPGO
+# which does entry/backedge instrumentation
+
+chain1.filter=+::<clinit>
+chain1.filter=-
+
+JET_CLINIT.file=<path to dll>
+JET_DPGO.file=<path to dll>
+CD_OPT.file=<path to dll>
+
+#Confuguration of profile collector and recompilation
+JET_DPGO.genProfile=EB_PROF
+EB_PROF.profilerType=EB_PROFILER
+CD_OPT.useProfile=EB_PROF
+
+
+EB_PROF.mode=SYNC
+EB_PROF.entryThreshold=10000
+EB_PROF.backedgeThreshold=100000
+</pre></p>
+
+<p><b>
+ <code>-Xem:server</code> - the server mode configuration, or server dynamic</b></p>
+<p><pre>
+chains=chain1,chain2
+chain1.jits=JET_CLINIT
+chain2.jits=SD1_OPT,SD2_OPT
+
+chain1.filter=+::<clinit>
+chain1.filter=-
+
+JET_CLINIT.file=<path to dll>
+SD1_OPT.file=<path to dll>
+SD2_OPT.file=<path to dll>
+
+# Edge profiler and recompilation parameters
+EDGE_PROF.profilerType=EDGE_PROFILER
+EDGE_PROF.entryThreshold=40000
+EDGE_PROF.backedgeThreshold=150000
+EDGE_PROF.tbsTimeout=10
+EDGE_PROF.tbsInitialTimeout=0
+
+SD1_OPT.genProfile=EDGE_PROF
+SD2_OPT.useProfile=EDGE_PROF
+</pre></p>
+
+<p class="note">Note</p>
+ <p class="notetext">To run VM in the intereter mode, use the <code>-Xint</code>
command-line option to override any other EM settings. Currently, DRLVM does
not support the mixed mode of the JIT compiler plus interpreter.
</p>