The following applies to Meridian 64-bit editions when run on a Windows 64-bit operating system only.
Because the 64-bit platform provides a vastly larger memory address space and server computers with large amounts (16 GB or more) of physical memory are readily available and affordable, Meridian performance and scalability can be improved with an optimal configuration called HyperCache. HyperCache is the default configuration for the Meridian Enterprise 64-bit platform.
In the HyperCache configuration, vaults are loaded entirely into memory. This maximizes the performance of these vaults, which typically serve larger numbers of users and higher quantities of documents. The contents of the HyperCache are saved in Hypertrieve databases between service shutdowns and startups for the fastest possible loading. The vault contents are replicated to repositories hosted by SQL Server or Oracle where they can be accessed with the Meridian Explorer client or standard reporting tools such as SQL Reporting Server and Crystal Reports. For more information about this replication, see Data Library.
Performance tests in simulated customer environments have shown that HyperCache can improve performance significantly. Stress tests have shown that Meridian Enterprise 64-bit with HyperCache can manage 1.5 million documents (not counting revisions) and over 200 concurrent users while still providing good performance.
Earlier versions of Meridian Enterprise have been used mostly with up to 0.5 million documents (not counting revisions) and up to 100 concurrent users.
While these tests have been executed on hardware and software configurations that resemble typical customer environments, they are not representative of any particular customer environment. Therefore, in cases of more than 0.5 million documents (not counting revisions) and/or more than 100 concurrent users, we strongly recommend having the hardware and software configuration reviewed by Accruent or your Accruent Partner.
We recommend HyperCache configuration for all customers, but particularly for those with the following scenarios:
-
Existing systems with performance or scalability problems.
-
Customers planning to significantly expand their number of users or documents in the near future.
Implementing HyperCache requires:
-
64-bit CPU server computer
-
Adequate physical memory (greater than the sum of the sizes of all vaults stored in Hypertrieve)
-
Microsoft Windows Server 2008, 2012, 2016, or 2019 (partial support: no full-text search is available)
-
Additional requirements as listed in Meridian Application Server Requirements
-
Meridian Enterprise 2018 or higher
-
No new system administration tasks
To calculate the amount of physical memory required for existing Hypertrieve vaults, add the size of all vault database files together and round up to the next largest memory configuration available for the server computer. To calculate this amount for existing SQL Server or Oracle vaults, add half the size of all vault database files and round up.
| Memory Pool | Size (MB) |
|---|---|
| Windows Server operating system | 2000 |
| Meridian services | 200 |
| Meridian user sessions (25 MB/user * 50 users) | 1250 |
|
Work In Progress vault |
266 |
|
As-Built vault |
789 |
|
Archive vault |
1584 |
|
Min. Server Memory |
6089 |
Assuming the closest available memory configurations for the server are 6 GB and 8 GB, select the 8 GB configuration at a minimum.
| Memory Pool | Size (MB) |
|---|---|
| Windows Server operating system | 2000 |
| Meridian services | 200 |
| Meridian user sessions (25 MB/user * 100 users) | 2500 |
|
Work In Progress vault |
1902/2=951 |
|
As-Built vault |
3048/2=1524 |
|
Archive vault |
6692/2=3346 |
|
Min. Server Memory |
10521 |
Assuming the closest available memory configurations for the server are 8 GB and 12 GB, select the 12 GB configuration at a minimum.
Configuring HyperCache is described in the following topic.
