Tuning FishEye


Added by Sarah Maddox, last edited by Sarah Maddox on Oct 03, 2007

Labels:

block-size block-size Delete
environment-variable environment-variable Delete
fisheye_opts fisheye_opts Delete
heap heap Delete
tuning tuning Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
FishEye 1.3 Documentation

Index

Java Heap Size

The heap size of the FishEye Java Virtual Machine is controlled by the FISHEYE_OPTS environment variable. The best heap size to use is dependent on a number of factors including:

  • The source code management (SCM) system being used. Subversion scanning typically uses more memory than CVS, for example.
  • The complexity of operations in the repository. Processing changesets which affect many files will use more memory.
  • The amount of physical RAM in the system. If the Java heap is too large, it may induce swapping which will impact performance.

FishEye will reserve a portion of the available heap for caching of database data. So in general, the more memory you can supply, the better.

If you do run into 'Out of Memory' errors, you will need to increase the heap size and restart FishEye.

For Subversion repositories, it is also possible to reduce FishEye's memory footprint by reducing the BlockSize parameter.