top of page

LITIGATION SUPPORT TIP OF THE NIGHT

The views expressed in this blog are those of the owner and do not reflect the views or opinions of the owner’s employer. All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information. This policy is subject to change at any time. The owner is not an attorney, and nothing posted on this site should be construed as legal advice. Litigation Support Tip of the Night does not provide confirmation that any e-discovery technique or conduct is compliant with legal, regulatory, contractual or ethical requirements.

See my post on Running Regex Searches With a Grep Utility on the ILTA litigation support blog.

New tips for paralegals and litigation support profesionals are posted to this site each week. Click on the blog headings for better detail.

See How-To Videos on my YouTube channel.

Relativity and JVM RAM

Sean O'Shea
Apr 2, 2020
1 min read

You can improve the performance of Relativity analytics operations by increasing the amount of RAM available for Java. The Java heap is the amount of memory allocated to the Java Virtual Machine (JVM). The JVM is a program that executes other programs written in Java.

Relativity recommends that servers which are used for indexing and structured analytics allocate about 50% of available RAM to Java. This setting should be increased to 75% if only structured analytics is being performed. Only a third of total RAM should be assigned to the Java heap if a server is used only for indexing.

A server will need an amount of RAM in bytes equal to 6000 times the number of documents involved in an index build. So, a training set of a million documents for an index build will require 6 GB of RAM. The same equation applies for calculating the Java heap size needed for a structured analytics set.

bottom of page