Relativity - System Requirements - v9 - System... · Relativity|SystemRequirements-2...

System RequirementsFebruary 4, 2019 - Version 9.2

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

For the most recent version of this document, visit our documentation website.

http://help.relativity.com/9.2

Relativity | System Requirements - 2

Table of Contents1 System requirements 3

2 Infrastructure overview 4

3 Scalability 6

3.1 Tier level definitions 6

4 Recommended configurations for new deployments 8

4.1 Tier 1 - Hardware requirements (25-50 named users) 8

4.2 Tier 1 - Hardware requirements (100 or more named users) 8

4.3 Tier 2 - Hardware requirements (300 or more named users) 9

4.4 Storage 9

5 Infrastructure configuration 11

5.1 Guides for infrastructure management 11

6 Software requirements 12

6.1 System (servers or virtual machines) 12

6.2 Workstations (end-user PCs) 14

6.3 Relativity Desktop Client 14

6.4 Licensing Microsoft products 15

7 Relativity compatibility matrix 16

7.1 Relativity system requirements matrix 16

7.2 Internet Explorer with Compatibility View 17

7.3 Chrome, Firefox, and Safari support 17

7.4 Analytics release matrix 18

7.5 Invariant (worker manager server) release matrix 18

8 Processing system requirements 19

8.1 Processing worker hardware specifications 19

8.2 Tier hardware requirements 19


1 System requirementsThese system requirements contain detailed information about the software and hardware you use to hostRelativity in your environment and in the cloud. These requirements also provide variousrecommendations for configuring a new deployment of Relativity, as well as scaling your environment asthe number of users and the amount of data continue to grow.


2 Infrastructure overviewRelativity is designed with a scalable infrastructure that you can tailor to the requirements of yourenvironment. It is developed on the .NET framework with a Microsoft SQL Server back-end. As illustratedin the following diagram, all areas of the platform are scalable providing support for any hardware vendor,hypervisor, and storage protocol.

Web ServerThe Web Server is the gateway for all users to access Relativity. It authenticates the user with the system,contains APIs for searching and third-party applications, transfers documents to the end user in theRelativity Viewer, and is responsible for communications during imports and exports in workspaces. Thereare different methods of authentication into the system including forms, active directory, and RSA support.User sessions can be load balanced with the included Relativity User Load Balancer or via availablehardware load balancing solutions.

Agent Server (Core)Agents in Relativity are responsible for running all background processing tasks. When a user submits ajob, such as a Production or OCR job, the associated agent(s) will pick up the job and complete the work.The agents run under a Windows Service and often require various levels of CPU, RAM and I/O,depending on the job type. The agents can be scaled vertically and horizontally to accommodateorganizational needs.

Agent Server (dtSearch)


In Relativity 8 and above, the searches are multi-threaded and spawn as many threads as there are sub-indexes or cores—whichever number is lowest will be the constraint. One dtSearch search agent may beable to utilize all available processor cores on a server. Therefore, each Relativity agent server that isdesignated to be a dtSearch search agent server should only have one dtSearch search agent andnothing else.

SQL Server (Workspaces)This SQL server is where the structured text and metadata resides for the documents. Each Relativityworkspace is represented by its own SQL Server database. Environments may have one or more SQLServers. In addition to workspace databases there are Relativity system databases present on eachserver that contain tables for system configurations, agent job queues, user/groups, etc.

SQL Server (Invariant/Worker Manager Server)Relativity processing has individual store databases that correspond to each Relativity workspacedatabase with processing enabled. Total memory and processor requirements for this role are not asdemanding as the SQL Servers that house workspace databases. This server is also used for nativeimaging and viewer conversion request management across various queue and configuration tables.

WorkerThe ‘Worker’ role is responsible for handling enhanced native imaging, processing, and viewer conversionjobs. We have placed a hard cap on the amount of threads that each Worker server is allowed to spawn,the hard cap is 16 threads. Each processor core and 2GBRAM will create two threads. Therefore, it issuggested that 8 logical cores and 16GBRAM be allocated to each worker server to get the mostthroughput. One worker server should be dedicated to viewer conversion for every 100 concurrent users.

AnalyticsThe analytics server is responsible for building and storing the conceptual indexes in the environment.Once an index is built, the server is also used to run the conceptual features such as categorization andclustering. In addition to conceptual indexing, structured analytics sets are run on this server for textualanalysis features such as email threading or language identification. The indexes and structured analyticssets are stored on disk in a configurable location.

File ServerThis server may not be required depending on the available storage. We don't install any software on a fileserver for Relativity. Relativity just needs to know where the Files (Natives/Images) live and the webservers need to be able to access those locations. The same applies to dtSearch, Analytics index, andviewer cache location(s).


3 ScalabilityYou can scale Relativity installations to handle the performance, storage, and other environmental factorsnecessary to support the addition of new users, continual growth of data, and increased demands forsearching capabilities.

3.1 Tier level definitionsWe have identified tier levels that support varying numbers of users and sizes of active data. You can usethese tier level definitions to determine the cores, RAM, and other equipment required to support the rapidgrowth of your Relativity installation. Key terms used in the following table include:

n Enabled User Accounts – amount of enabled Relativity User accounts.

n Simultaneous Users - average amount of simultaneous users logged into Relativity.

n Active SQL Data (TB) - total amount of disk space consumed by SQL databases (mdf) and full text(ndf) indexes.

n Active Record Count (MM) – total amount of records (documents) included across all activeRelativity workspaces.

n Active File Size (TB) - total amount of disk space consumed by native and image files.

This table identifies the combination of users, data, and file sizes associated with each tier.

Tier 1 - Entry LevelEnvironment

Tier 2 - Mid LevelEnvironment

Tier 3 - Large ScaleEnvironment

Enabled UserAccounts

< 300 300 - 1000 1000+

Simultaneous Users < 100 100 - 500 500+Active SQL Data(TB)

< 1 1 - 10 10+

Active RecordCount (MM)

< 20 20 - 100 100+

Active File Size (TB) < 5 5 - 30 30+The equipment used to support environments at each tier is described in the following table.

Tier 1 - EntryLevelEnvironment

Tier 2 - MidLevelEnvironment

Tier 3 - Large Scale Environment

Total Cores for Non-SQL < 48 48 - 192 192+Total Memory (GB) for Non-SQL

< 96 96 - 384 384+

Total Cores for SQL Server < 16 16 - 96 96+Total Memory (GB) for SQLServer

< 128 128 - 1024 1024+

Total SQL Storage I/O (Gbps) 4 - 8 8+ SQLServer Fast Track (http://www.-microsoft.com/fasttrack)

SQL Tempdb Storage Separate SSD or flash SSD or flash


Tier 1 - EntryLevelEnvironment

Tier 2 - MidLevelEnvironment

Tier 3 - Large Scale Environment

spindles

Note: Microsoft SQL Server Fast Track combines preconfigured servers, storage, and networking withSQL Server 2012 R2 Enterprise for a scalable enterprise data warehouse platform. You can chooseindustry-standard hardware from Dell, HP, Cisco, IBM, EMC, and other leading vendors.


4 Recommended configurations for newdeploymentsContact Relativity Client Services for assistance with designing your Relativity infrastructure.

Note: The following Tier 1 example environments provide information for different user and datacounts. Most new deployments adhere to one of these Tier 1 examples.

4.1 Tier 1 - Hardware requirements (25-50 named users)We support the installation of all Relativity components on a single device for 25-50 named useragreements. We also require that a hypervisor is installed to this device so each Relativity role has its ownvirtual machine.

Hardware Minimum RequirementsMemory 144GB RAMProcessor 40 logical cores (2GHz)Storage This server can be attached to a storage device (SAN, DAS, NAS).The following table provides virtual machine specifications for the single server setup.

Tier 1 (25-50 named users) - Single Server Deployment Quantity Memory (GB) CPUWeb 2 4 4Agent 2 4 4Analytics 1 32 4Worker 1 16 8SQL (Workspace Databases) 1 64 8SQL (Invariant/Worker Manager Server) 1 16 4

4.2 Tier 1 - Hardware requirements (100 or more named users)While Relativity supports the use of virtual machines, differing configurations are recommendeddepending on the tier level of your environment. The number of SQL Servers is influenced by HighAvailability and Disaster Recovery requirements as described in Infrastructure configuration. You candistribute Relativity workspace databases across multiple SQL instances.

This table lists the recommendations for environments at Tier 1.

Tier 1 (100+ named users) - Entry Level Environment Quantity Memory (GB) CPUWeb 2 8 8Agent 3 4 4Analytics 1 32 8Worker (Processing, Imaging) 2 16 8Worker (Conversion) 1 16 8SQL (Workspace Databases) 1 64 8SQL (Invariant/Worker Manager Server) 1 16 4


4.3 Tier 2 - Hardware requirements (300 or more named users)For Tier 2 environments, additional virtual machines are recommended as well as increased RAM andCPUs as illustrated in the following table. Additionally, it is suggested that SQL (Workspace Databases)instances are not virtualized when supporting larger datasets.

Tier 2 (300+ named users) - Mid Level Environment Quantity Memory (GB) CPUWeb 4 8 8Agent 4 8 8Analytics (Structured Analytics) 1 32 8Analytics (Analytics Indexing) 1 32 4Worker (Processing, Imaging) 4 16 8Worker (Conversion) 3 16 8SQL (Workspace Databases) 2 256 16SQL (Invariant/Worker Manager Server) 1 32 4Please take the following into consideration for any sized environment:

Note: For the File (Document) role, the type of storage system used will determine if you need to installthe Windows operating system.

File (Docu-ment)

n Processor: 4 cores (2GHz)

n Memory: 4GB RAM

n Network: Gigabit Ethernet

n Storage: See Storage.SMTP (Noti-fication)

Relativity requires an active SMTP server on your network. It interfaceswith this server tosend notifications andmonthly billing statistics. The hardware requirements for this roleareminimal. You can leverage an existing SMTP server in the network or merge thisserver with the agent server role.

4.4 StorageFor each type of data, the amount of recommended space depends on the number of records imported,as well as the type and length of the expected reviews. Each server or VM needs space for the OS, pagefile and less than 1GB for Relativity installation files. For the Relativity Processing SQL Server, all the sameSQL data is required with the exception of SQL Full Text Indexes. Throughput, especially when multipleSQL Servers are virtualized on a single host, should be put through a regiment of rigorous random andsequential read/write IO testing before installation of Relativity is completed.

Recommended space by data type:

Data Type 25-50 NamedUsers

100+ NamedUsers

Disk I/O

SQLDatabases 500GB 750GB HighThe databases can live acrossmultiple stor-age volumes and SQL instances.


Data Type 25-50 NamedUsers

100+ NamedUsers

Disk I/O

SQL Full Text Indexes 150GB 250GB ModerateIndex size depends on the number of fieldsand records indexed.

SQLDatabase Logs 150GB 250GB HighRegular transaction log backups keep thesevalues small and provide point in time recov-ery.

SQL Tempdb 80GB 80GB HighWe recommend eight 10GB Tempdb datafiles for new deployments. SSDs recom-mended.

SQL Backups 500GB 1000GB Low-HighWe recommend having a backup strategy.This volume is not required. Larger data sizesmay require higher I/O throughput.

dtSearch Indexes 150GB 250GB ModerateThe dtSearch index share is typically storedin the same location as the files.

Analytics Indexes 150GB 250GB HighThe Analytics index volume ismounted to theAnalytics virtual machine with speed and con-nectivity similar to that of SQL Server.

Files (Natives/Images) 1500GB 3000GB Low-HighThe filesmay not require aWindows install-ation depending on the storage. Multiple Pro-cessingWorkers online will require more filestorage I/O.

Viewer Cache 500GB 1000GB HighTemporarily store natives, images, pro-ductions, and other file types the viewer uses.It is recommended that the cache be storedon tier-one storage (SSDs) in environmentswith hundreds of concurrent users. Recom-mended 1TB viewer cache space availablefor every 100 concurrent users.

Worker (NativeImaging/Processing)

250GB 250GB HighThis is theWindows temp directory used bynative applications during imaging and pro-cessing. This temp location never exceeds250GB for eachWorker server.


5 Infrastructure configurationRelativity supports the following technologies as part of its infrastructure configuration:

n VirtualizationWe suggest virtualizing all Relativity roles with the exception of SQL (workspace databases). Anyhypervisor is supported.

Note: Virtualizing SQL may simplify meeting HA and DR requirements. However, it can introduceadditional layers of complexity when properly configuring and troubleshooting performance andstability related issues.

The worker servers are CPU intensive and do not store any critical data, consider not virtualizingthis role to possibly reduce licensing costs, assuming there is more than one worker serveravailable.

We're not opposed to virtualizing SQL (native imaging/processing). This server demands lesshardware resources, and any performance issues would impact only these Relativity features.

n High Availability (HA)Relativity supports SQL Server Failover and File Server Clustering along with available hypervisorsolutions.

n Disaster Recovery (DR)Relativity supports Microsoft SQL Server mirroring, log shipping, and SAN replication technologies.These approaches typically require manual failover and increased downtime.

n Web Server Load BalancingRelativity supports only single affinity in Windows Network Load Balancing (NLB). The RelativityUser Load Balancer (RULB) provides the ability to distribute the user load evenly.

n Perimeter Networking (DMZ)Relativity requires certain ports to remain open for proper server communication. For more details,download the Relativity Infrastructure Ports Diagram from the Relativity Community. Note that youmust have a valid username and password to download this content.

5.1 Guides for infrastructure managementReview the following guides to become familiar with best practices for managing the Relativityinfrastructure:

n Pre-Installation Guide

n Environment Optimization Guide

n Infrastructure Planning Recommendations

n Performance metrics and recommendations

https://community.relativity.com/sfc/servlet.shepherd/document/download/06950000001aoJo?operationContext=S1


6 Software requirementsRelativity has specific software requirements for servers or virtual machines, user workstations, and theRelativity Desktop Client. The requirements for servers differ by the role assigned to them in your systemconfiguration.

Note: Make sure that you install the latest service packs for Windows, .NET, and SQL Server on yourmachines.

6.1 System (servers or virtual machines)

Note: Relativity is compatible with local settings Only for webservice servers.

The general software requirements for servers and virtual machines include Microsoft Windows Serverand .NET technologies. Microsoft Office and other applications are required for worker manager servers.

The following table provides software requirements by server role.

Server Role Software RequirementsWeb n Windows Server 2012 R2 or Windows Server 2008 R2

n .NET Version 4.5.1

n .NET Version 3.5

n IIS 7.5, 8.0, or 8.5Agent n Windows Server 2012 R2 or Windows Server 2008 R2


n .NET Version 3.5Analytics n Windows Server 2012 R2 or Windows Server 2008 R2SQL n Windows Server 2012 R2 or Windows Server 2008 R2

n SQL Server 2014, SQL Server 2012, or SQL Server2008 R2


n .NET Version 3.5

Fix for Microsoft KB3138319, KB 3151109 and KB3120595:

n Cumulative Update 11 for SQL Server 2012 SP 2

n Cumulative Update 2 for SQL Server 2012 SP 2

n Cumulative Update 5 for SQL Server 2014 SP1

n Cumulative Update 13 for SQL Server 2014


Server Role Software RequirementsWorker n Windows Server 2012, Windows Server 2012 R2, or

Windows Server 2008 R2

n .NET Version 3.5

n .NET Version 4.5.1 (starting in Relativity 9.2.271.9)

n Desktop Experience (Windows Server feature)

n Microsoft Office 2010 Professional SP2 (32-bit) -o Microsoft 2010 includes OneNote and Publisher,

which are also required applications.

o The Courier New and Arial Unicode MS fontsmust be installed on your machine. These fontsare installed by default when you install MicrosoftOffice 2010, in which case you must ensure thatyou don't remove them.

o If you upgrade to a version of Microsoft Officehigher than 2010, you won't be able to use pro-cessing in your environment.

n Microsoft Visio 2010 Professional or Standard SP2 (32-bit)

n Microsoft Project 2010 Professional or Standard SP2(32-bit)

n Lotus Notes v8.5.2 with Fix Pack 4 or Lotus Notesv8.5.3 with Fix Pack 6

o Beginning in Relativity 9.2.271.9, Lotus Notes9.0X is supported but not required. It's recom-mended that you install Lotus Notes 9 or higheron your workers, as Lotus Notes version 8.5.xcan’t read certain Lotus 9 databases. Note thatsome Lotus 9 databases can't be opened in 8.5.xand will generate an error during processing.

n Adobe Reader 4.0 or higher

n SolidWorks eDrawings Viewer 2015 (64-bit) with theoption to view 3D XML and PRO/E files.

o Beginning in Relativity Version, the SolidworkseDrawings Viewer 2015 is no longer a pre-requisite for processing. Solidworks is onlyrequired for performing native imaging and textextraction on any supported CAD files in yourdata sources Thus, you should install it only onthe worker designated to perform these types ofjobs. If you attempt to process a CAD file without

https://www.solidworks.com/sw/support/edrawings/e2_downloadcheck.htm


Server Role Software Requirements

the Solidworks viewer installed, you receive asimple document-level error prompting you toinstall it. Once you install the Solidworks viewer,you can retry that error and proceed with yourprocessing job.

n JungUm Global Viewer v9.0 or higher

6.2 Workstations (end-user PCs)In Relativity, end users perform their reviews on workstations. Each workstation should be configured witha browser in which to use the Relativity web application, an operating system on which to run the RelativityDesktop Client, and the currently supported version of .NET.

Supported browsers for

Relativity web applicationSupported operating systems for RelativityDesktop Client

Supported .NETversion

n Microsoft InternetExplorer 11.x

n Microsoft InternetExplorer 10.x

n Google Chrome 42+ (onboth PC and Mac)

n Apple Safari 7.1+ (MacOSX 10.9)

n Apple Safari 8.0+ (MacOSX 10.10)

n Firefox 37+ (on both PCand Mac)

n Windows 8 Desktop Mode (PC)

n Windows 8 Pro Desktop Mode (SurfacePro)

n Windows 7

n Windows Vista

n Windows Server 2012 R2

4.5

6.3 Relativity Desktop ClientThe Relativity Desktop Client (RDC) is a utility used for importing and exporting documents, images,natives, and productions. This utility requires the following software:

n Microsoft .NET 4.5 (Full Framework)

n Microsoft Visual C++ 2005 SP1 Redistributable x86 or x64

Note: Visual C++ 2005 SP1 Redistributable x86 is supported on 32-bit and 64-bit OS, but x64 issupported on 64-bit OS only.

For detailed installation instructions, see the Desktop Client Guide.


6.4 Licensing Microsoft productsRelativity requires Microsoft Windows and Microsoft SQL Server, both of which you need to licensethrough Microsoft or one of their resellers. If using Relativity Processing or Native Imaging, you also needto license Microsoft Office, Visio, and Project through Microsoft or one of their resellers.

If Relativity is hosted for external customers, you may need to license Microsoft products throughMicrosoft’s SPLA (Service Provider License Agreement). You can find more information about Microsoft’sSPLA program on Microsoft’s Hosting site.

We recommend contacting Microsoft, or one of their resellers, for guidance on the licensing optionsavailable.

http://www.microsoft.com/hosting/en/us/licensing/default.aspx


7 Relativity compatibility matrix

7.1 Relativity system requirements matrixThe following table breaks down the supported operating systems, framework, IIS versions, browsers,and versions of SQL Server per Relativity version. For additional Chrome, Firefox, and Safari supportedversion details, see Chrome, Firefox, and Safari support on the next page.

Software 8.2 9.0 9.1 9.2Operating systems - Relativity Desktop ClientWindowsServer 2008 R2 (64-bit) ✓ ✓ ✓ ✓WindowsServer 2012 R2 (64-bit) ✓ ✓ ✓ ✓WindowsXP ✓Windows 7 ✓ ✓ ✓ ✓Windows 8 (DesktopMode only) ✓ ✓ ✓ ✓Windows 8.1 ✓Windows 10 ✓

(beginning in version9.2.390.1)

Operating systems - serversWindowsServer 2008 R2 (64-bit) ✓ ✓ ✓ ✓WindowsServer 2012 ✓ ✓ ** ✓ **

WindowsServer 2012 R2 ✓ ✓ ✓ ✓FrameworkMicrosoft .NET Version 3.5 w ServicePack 1

✓

Microsoft .NET Version 4.5 ✓Microsoft .NET Version 4.5.1 ✓ *** ✓ *** ✓IIS versionsIIS 7.5 ✓ ✓ ✓ ✓IIS 8.0 ✓ ✓ ✓IIS 8.5 ✓ ✓ ✓ ✓End user browser and operating system requirementsWe recommend using the latest version of Chrome, Firefox, and Safari with Relativity. For Chrome,Firefox, and Safari web browsers, Relativity supports:

n The three most recent versions of Chrome and Firefox (for Windows and Mac OSX) at the time of agiven Relativity release

n The two most recent versions of Safari included with Mac OSX at the time of a given Relativityrelease


Software 8.2 9.0 9.1 9.2Note: Relativity only supports Firefox in Relativity 9.0.237.3 and higher.IE 8 (32-bit) ✓ *

IE 9 (32-bit) ✓IE 10 (32-bit) ✓ ✓ ✓ ✓IE 11 (32-bit) ✓ ✓ ✓ ✓Chrome (for Windows and Mac OSX) ✓ ✓ ✓Firefox(for Windows and Mac OSX) ✓ ✓ ✓Safari (Mac OSX) ✓ ✓ ✓SQL versionsSQLServer 2008 R2 (64-bit), Standardor Enterprise

✓ ✓ ✓ ✓

SQLServer 2012 ✓ ✓ ✓ ✓SQL Server 2014 (beginning in Relativity9.1.172.5)

✓ ✓

* IE 8 doesn't support Collection, Inventory (in Processing) or the Workspace Security, Admin Security,and Item Security dialogs. However, IE 9, 10, and 11 support these features.

**We strongly recommend running Windows Server 2012 R2 over Windows Server 2012.

***Web, agent, and SQL servers require .NET 4.5.1.

Note: For Relativity 9.2.237.3 worker servers require .NET 4.5.1.

Note: Relativity does not currently support the Linux operating system for any browser.

7.2 Internet Explorer with Compatibility ViewRelativity doesn't support using Internet Explorer with Compatibility View enabled. Disable CompatibilityView in Internet Explorer using the following steps:

1. Press the Alt key.

2. Click Tools >Compatibility View settings.

3. Remove your URL for Relativity from the list ofWebsites you've added to Compatibility View.

4. Deselect the checkbox labeled Display intranet sites in Compatibility View.

5. ClickClose.

7.3 Chrome, Firefox, and Safari supportWe recommend using the latest version of Chrome, Firefox, and Safari with Relativity. See End userbrowser and operating system requirements on the previous page for additional browser compatibilitydetails regarding Chrome, Firefox, and Safari.


The following table provides historical browser support information by Relativity release.

Browser 9.0 9.1 9.2Chrome (for Windows andMacOSX) 35+ 37+ 42+Firefox (for Windows andOSX) 30+ 33+ 37+Safari onMacOS X 10.9 7.1+ 7.1+ 7.1+Safari onMacOS X 10.10 8.0+ 8.0+ 8.0+

Note: Relativity supports Firefox in Relativity 9.0.237.3 and higher.

7.4 Analytics release matrixView Analytics release history for Relativity 9.2The following table lists the version of CAAT released with each Relativity 9.2 release.

Relativity 9.2 release CAAT release Release date9.2.517.2 3.17.3 March 30, 20169.2.271.9 3.17.2 July 29, 20159.2.211.3 3.17.1 May 29, 2015

7.5 Invariant (worker manager server) release matrixView Invariant release history for Relativity 9.2The following table lists the version of Invariant (worker manager server) released with each Relativity 9.2release.

Relativity 9.2release

Invariant release Release date

9.2.600.21 4.2.600.9 December 16, 20169.2.600.19 4.2.600.9 October 4, 20169.2.532.5 4.2.541.1 April 27, 20169.2.517.2 4.2.516.1 March 30, 20169.2.488.8 4.2.476.1 March 2, 20169.2.461.1 4.2.454.1 February 2, 2016N/A 4.2.440.13 January 13, 20169.2.408.3 4.2.408.1 December 18, 2015Version Version December 7, 2015Version Version November 25, 2015Version Version October 28, 2015Version Version September 30, 2015Version Version August 26, 20159.2.271.9 4.2.272.7 July 29, 20159.2.251.5 4.2.252.6 July 10, 20159.2.237.3 4.2.237.7 June 24, 20159.2.219.10 4.2.217.4 June 10, 20159.2.211.3 4.2.210.7 May 29, 2015


8 Processing system requirementsThe following information displays the system requirements for the Processing infrastructure.

8.1 Processing worker hardware specificationsThe following table displays the hardware specifications for Processing workers. These requirements aredetermined by the number of workers needed to achieve a specified range of throughput (# of GB/day).

Worker SpecificationsCPU 8 coreRAM 16GBNetwork 1GbpsStorage Windows TempSSD recommendedServer Physical recommended *Expected throughput 100-150GB/day *** The primary reason for using physical workers is for performance. The overhead from virtualization cancause degradation in performance, particularly during text extraction and other CPU-intensive operations.If you do choose to virtualize your workers, beware of over-committing resources on the host. If you havehyper-threading enabled on the host, you may need to allocate 16 vCPUs to each worker to achieveresults similar to those in the See the Processing performance section in the Performance Baselinesguide.

** Processing source data and system load may impact performance.

8.2 Tier hardware requirementsThe following table displays the supporting infrastructure per number of workers you want to deploy. Referto an applicable tier to locate the necessary hardware components to complete your processinginfrastructure.

Tier 1Entry LevelEnvironment

Tier 2Mid Level Environment

Tier 3Large ScaleEnvironment

# of Workers 1 - 2 3 - 7 8+GB/day (sourcedata)

100 - 300 300 - 800 800+

Invariant (workermanager server)SQL Server

n Processor: 4 cores

n Memory: 16 GB

n Storage I/O (Gbps):4

n Processor: 4 - 8cores

n Memory: 32 GB

n Storage I/O (Gbps):4 - 8

n Processor: 4 - 8cores

n Memory: 64 GB

n Storage I/O(Gbps): 4 - 8+

File Server n Commodity NAS

n 1+ Gbps network

n Dedicated NAS(write-back cacheavailable)

n 4+ Gbps network

n Enterprise classNAS (SSD tieravailable)

n 10+ Gbps network


Note: By default, when you install Relativity, each worker in your environment is designated to do allavailable work (conversion, processing, and imaging). It's recommended that you change thisdesignation so that, for every one hundred simultaneous users in your environment, you have oneworker dedicated to conversion only and another worker dedicated to processing and/or imaging (butnot conversion).


Proprietary RightsThis documentation (“Documentation”) and the software to which it relates (“Software”) belongs toRelativity ODA LLC and/or Relativity’s third party software vendors. Relativity grants written licenseagreements which contain restrictions. All parties accessing the Documentation or Software must: respectproprietary rights of Relativity and third parties; comply with your organization’s license agreement,including but not limited to license restrictions on use, copying, modifications, reverse engineering, andderivative products; and refrain from any misuse or misappropriation of this Documentation or Software inwhole or in part. The Software and Documentation is protected by the Copyright Act of 1976, asamended, and the Software code is protected by the Illinois Trade Secrets Act. Violations can involvesubstantial civil liabilities, exemplary damages, and criminal penalties, including fines and possibleimprisonment.©2019. Relativity ODA LLC. All rights reserved. Relativity® are registered trademarks ofRelativity ODA LLC.

Relativity - System Requirements - v9 - System... · Relativity|SystemRequirements-2...

Documents

Transcript of Relativity - System Requirements - v9 - System... · Relativity|SystemRequirements-2...