Understand scaling for number of users. See Scaling for number of users. |
|
Ensure you're able to quickly scale web servers. See Web servers. |
|
Create separate application pools. See Application pools. |
|
Dedicate a web server to the very large workspace. See Download handlers. |
|
If needed, set up load balancing. See Load balancing. |
|
Create a Terminal server. |
|
Ensure you're able to scale the SQL Server appropriately. See SQL recommendations. |
|
Attend training to understand Relativity best practices. See Training. |
|
Follow best practices for creating fields. See Adding fields. |
|
Understand scaling for document count. See Scaling for document count. |
|
Follow loading best practices. |
|
Follow best practices for creating folders. See Folders. |
|
Follow layout best practices. See Layouts. |
|
If possible, license for SQL Enterprise Edition. See SQL recommendations. |
|
Ensure maintenance plans are set up correctly. See Maintenance plans. |
|
Review the indexes on SQL tables; delete unnecessary ones. See Index strategy. |
|
Understand scaling for database size. See Scaling for database size.
|
|
Understand the tipping point. See Tipping point. |
|
Scale RAM and disk IO comparably to database size. See Web servers. |
|
Manage the Audit record table. See Audit record management. |
|
Follow SQL recommendations for large tables. See SQL recommendations. |
|
Ensure you are not making any mistakes. See Common mistakes. |
|
Ensure SQL data is living on the fastest disks. See Disks. |
|
Ensure disk latency is tested and monitored on servers running Relativity. See SQL Latency. |
|
Understand workflow investigation of searching and subsequent load. See Workflow and searching. |
|
Follow searching best practices. See Keyword search (full-text index). |
|
Follow Analytics best practices. See Analytics
. |
|