Changes between Version 2 and Version 3 of Doc/compiler/problems


Ignore:
Timestamp:
Mar 7, 2007, 2:19:15 PM (19 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Charles Loomis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/compiler/problems

    v2 v3  
    22[[TracNav]]
    33
    4 == Memory ==
     4== Memory Problems ==
    55
    66=== Java Heap Space ===
    77
     8If you see messages that refer to "Java Heap Space" while running the compiler, then the java virtual machine does not have enough memory to compile the given templates.  You must increase the amount of memory allocated to the java virtual machine when you start the compiler.  See the section [Doc/compiler/running Running the Compiler] for how to specify the VM memory.
    89
     10=== Slow Compilation ===
     11
     12If the compilation appears to be slow, check that the compiler is not thrashing because of a limited amount of memory.  With the verbose option set, successful compilations will produce a summary like:
     13{{{
     1448 templates
     15517/0/517 compiled, 48/48 built
     160/0 obj, 48/48 xml, 48/48 dep
     170 errors, 31289 ms, 86 MB/506 MB heap, 11 MB/112 MB nonheap
     18}}}
     19The last line with gives the maximum amount of heap memory used and the maximum available (the value marked "heap").  If the maximum used is more than about 80% of the maximum, then you should consider increasing the memory allocated to the java virtual machine.  See the section [Doc/compiler/running Running the Compiler] for how to specify the VM memory.
     20