Review Center performance baselines

This page acts as a reference to track the general performance of Review Center in RelativityOne.

Because of data and configuration differences, do not use this as a benchmark for what to expect in your own organization's environment. The results may not scale linearly.

Queue size recommendations

For the best user experience, we recommend limiting the queue size as follows. These numbers are based on extensive testing in RelativityOne.

Performance testing definitions

For these tests, the times listed include the time taken to populate the queue, build the model, and load the results into the Review Center dashboard.

The start and end times are measured as:

• Start time—the time the user clicked the button to start the job.
• End time—the time the last document became available in Review Center.

Overall build speed

In a queue with 1 million documents, 10 of which were pre-coded, an initial build took slightly over an hour. It populated data into the queue at a rate of 13.57 gigabytes of data per hour, or 920,000 documents per hour.

The tabulated data is as follows.

Build time variance with document coding and caching

The following tests used a queue that contained 1 million documents, but each test had a different number of pre-coded documents. These documents were randomly coded 50% responsive and 50% non-responsive.

Each test also recorded the time it took to complete a second build. After the initial run, later builds use cached document tokens, which substantially speeds up the process.

Build time variance with more documents

The following tests used a queue that contained 5,027,765 documents. Like previous tests, each test had a different number of pre-coded documents. These documents were randomly coded 50% responsive and 50% non-responsive.

Each test also recorded the time it took to complete a second build. After the initial run, later builds use cached document tokens, which substantially speeds up the process.