<oXygen/> XML Editor User Guide

Performance problems

Large documents

By default the maximum memory available to <oXygen/> is set to 180 MB. If <oXygen/> is used on large documents (more than 10 MB) and you see that performance slows down considerably after some time then a possible cause is that it needs more memory in order to run properly. You can increase the maximum amount of memory available to <oXygen/> by modifying a parameter in a configuration file specific to the platform that runs the application as specified below.

[Warning]Warning

The maximum amount of memory should not be equal to the physical amount of memory available on the machine because in that case the operating system and other applications will have no memory available.

[Note]Note

The amount of memory allocated for the FOP operations is controlled by a different setting available in <oXygen/> Preferences: Memory available to the built-in FOP.

On the Windows platform the total amount of memory is specified by the value of the Xmx parameter on the line Virtual Machine Parameters in the file oxygen6.1.ini found in the installation directory.

On the Mac OS X platform to change the total amount of memory you have to right-click on the <oXygen/> application icon, in the popup menu select Show Package Contents, then in the Contents directory you edit the file Info.plist: in the key VMOptions modify the Xmx parameter.

On the Linux platform the total amount of memory is specified by the value of the Xmx parameter on the line lax.nl.java.option.additional from the file Oxygen.lax located in the installation directory.

If you use the All platforms distribution you can modify the total amount of memory by modifying the Xmx parameter of the java command line in the file oxygen.bat on Windows, oxygenMac.sh on Mac OS X and oxygen.sh on Linux. This file is located in the <oXygen/> installation directory.

When installed on a multi-user environment such as Windows Terminal Server or Unix/Linux, to each instance of <oXygen/> will be allocated the amount stipulated in the memory value. To avoid depreciating the general performance of the host system, please ensure that the amount of memory available is optimally apportioned for each of the expected instances.

Example 2.1. Example of java command line in startup script (Windows)

java -Xmx256m -cp %CP% ro.sync.exml.Oxygen $1 $2 $3 $4 $5 $6 $7 $8 $9

Modifying the value from 256 to 512 changes the memory available from 256 to 512.

Display problems on Linux/Solaris

Display problems like screen freeze or momentary menu pop-ups during mouse movements over screen on Linux or Solaris can be solved by specifying the parameter

-Dsun.java2d.pmoffscreen=false

for the Java virtual machine. This parameter disables offscreen pixmap support and must be added to the line lax.nl.java.option.additional from the file Oxygen.lax located in the installation directory.