Changeset 13544


Ignore:
Timestamp:
08/28/11 08:39:42 (10 years ago)
Author:
Mark Evenson
Message:

Spellchecking and proofreading.

Location:
public_html
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • public_html/faq-style.css

    r13543 r13544  
    1919}
    2020
     21ol#toc li li {
     22    margin-left: 1em;
     23}
  • public_html/faq.shtml

    r13543 r13544  
    4040  <li><a href="#running">Running</a>
    4141  <ol>
    42     <li><a href="#maxpermgen-errors">Java is running out of memory an error reporting something about "java.lang.OutOfMemoryError: PermGen space".  What can I do?</a></li>
     42    <li><a href="#maxpermgen-errors">Java is running out of memory
     43    with an error reporting something about
     44    "java.lang.OutOfMemoryError: PermGen space".  What can I
     45    do?</a></li>
    4346  </ol>
    4447  </li>
     
    150153<h3>What is the quality of the implementation? How can you tell?</h3>
    151154
    152 <p>The project recognises there are several dimensions to quality:</p>
     155<p>The project recognizes there are several dimensions to quality:</p>
    153156<ol>
    154157<li> The level of compliance to the standard </li>
    155 <li> The level of 'useability': whether (or not) the application is able
     158<li> The level of 'usability': whether (or not) the application is able
    156159  to run existing Lisp code</li>
    157160</ol>
     
    232235
    233236<div class="h3" title="Out of Memory errors" id="maxpermgen-errors">
    234 <h3>Java is running out of memory an error reporting something about "java.lang.OutOfMemoryError: PermGen space".  What can I do?</h3>
     237<h3>Java is running out of memory with an error reporting something
     238about "java.lang.OutOfMemoryError: PermGen space".  What can I
     239do?</h3>
    235240
    236241<p>
    237242  You need to increase the memory which the Java allocates for
    238   permanent generation ("PermGen)" objects by using the appropiate
     243  permanent generation ("PermGen)" objects by using the appropriate
    239244  switch on command line which invokes the JVM hosting ABCL.  When the
    240245  implementation compiles or loads Lisp code, it creates a separate
     
    245250
    246251<p>
    247   The exact manner of configuring this option which unfortunately
    248   varies by implementation.  For the Oracle HotSpot 64bit JVM,
    249   something like <code>"-d64 -Xmx4g -XX:MaxPermSize=1g
    250   -XX:+CMSClassUnloadingEnabled"</code> will not only increse the
     252  The exact manner of configuring this option unfortunately varies by
     253  Java implementation.  For the Oracle HotSpot 64bit JVM, something
     254  like <code>"-d64 -Xmx4g -XX:MaxPermSize=1g
     255  -XX:+CMSClassUnloadingEnabled"</code> will not only increase the
    251256  PermGen space, but will ensure you always invoke the 64bit JVM,
    252   increase the maximum memory space available to the JVM to 4Gib, and
    253   allow the JVM to garbage collect class definitions which its deems
     257  increase the maximum memory space available to the Java to 4GiB, and
     258  allow the garbage collection of class definitions which are deemed
    254259  to be unused.
    255260</p>
     
    258263  If you are compiling ABCL from source, a handy way to have the build
    259264  process incorporate such runtime flags in the JVM invocation would
    260   be to copy the <code>'abcl.properties.in'</code> file to <code>'abcl.properties'</code>, and
    261   then ensure that the <code>'java.options'</code> variable is set to the desired
    262   options.
     265  be to copy the <code>'abcl.properties.in'</code> file to
     266  <code>'abcl.properties'</code>, and then ensure that the
     267  <code>'java.options'</code> variable is set to the desired options.
    263268</p>
    264269</div>
Note: See TracChangeset for help on using the changeset viewer.