Changing memory allocation limits

NEW: jLog V 5.x allows change of the maximum memory allocation value (-Xmx) from the Profile. The value is stored in the files described below.

Mac OS X

The amount of memory allocated for jLog can be increased by editing the Maximum (-Xmx) and Minimum (-<Xms) memory allocation values as follows:

Ctrl-click on jLog in the Applications folder (or wherever you have placed it) and select 'Show Package Contents'. A new Finder window opens. Open (double-click) 'Contents'.

1) If you have the Property List Editor available, you can double-click the 'Info.plist' file. Open 'Root' and then the 'Java' node. Double-click on the value for the 'VMOptions' entry. Set the maximum (-Xmx) to e.g. 384 Mbytes (replace 384 with any number, e.g.: 256, 384, 512, 768, 1024):

-Xmx384m -Xms16m (may be specified as a two-line array)

2) If you do not have the Property List Editor installed, you can edit the file in a text editor (be careful). Locate <key>VMOptions</key> and change the values as follows:

<key>VMOptions</key>
<array>
   <string>-Xms16m</string>
   <string>-Xmx384m</string>
</array>

or
<key>VMOptions</key>
   <string>-Xms16m -Xmx384m</string>

Save the changes.

As a guidance: -Xmx512 may be needed for 50.000 entries, -Xmx1024 for 90.000 entries, etc.

Linux, Windows and Solaris

To go beyond 25 000 - 30 000 entries, the amount of memory allocated for jLog must be increased by editing the Java VM Maximum (and optionally also Minimum) memory allocation values as follows:

jLog V 5

Create a file named 'jlogstart.ini' in the program directory containing the 'jlogstart.jar' file with a line as follows:
app.vm.options=-Xmx192m
(note the minus after the '=' character. Replace 192 with any number like: 256, 384, 512, 1024)

The default values for jLog V 5 (without an ini-file) are: "-Xms16m -Xmx256m"

jLog V 4.6 (or older)

Locate the file 'jlog.lax' in the folder where jLog was installed. Open the file in a text editor (e.g. WordPad on Windows) and carefully add the following lines at the end of the file:

# LAX.NL.JAVA.OPTION.JAVA.HEAP.SIZE.MAX
# -------------------------------------
lax.nl.java.option.java.heap.size.max=128000000

If you get a memory failure, try to increase the numbers to e.g. 192000000 or more (depending on the amount of memory in your computer). You may want to experiment with this figure if jLog appears to have delays. You may try with smaller or bigger numbers and observe the speed changes...

Save the changes and restart jLog.

The same procedure applies for 'min' (increasing it may decrease loading time when logs are large).