Sizing Scenarios and Architecture - EcoSys - Help - Hexagon PPM

EcoSys Sizing

PPMProduct
EcoSys
PPMCategory_custom
Help
Version_EcoSys
8.6

Table of Architecture and Sizing Scenarios

Use the following table to identify an applicable architecture. Use the preceding sections to compute your implementation’s Data Volume Class (A-E+, from section above) and Concurrent User Load Impact (1-500+, from section above).

Architecture and Hardware

Data Volume Class *

Class A

Class B

Class C

Class D

Class E

Concurrent User Load Impact *

1-25

  • 1 medium app

  • 1 small DB

  • 50 GB disk

  • 1 medium app

  • 1 small DB

  • 50 GB disk

  • 1 medium app

  • 1 medium DB

  • 150 GB DB disk

  • 1 large app

  • 1 large DB

  • 200 GB DB disk

  • 1 large app

  • 1 large DB

  • 250 GB DB disk

25-75

  • 1 large app

  • 1 small DB

  • 50 GB disk

  • 1 large app

  • 1 small DB

  • 50 GB disk

  • 1 large app

  • 1 medium DB

  • 150 GB DB disk

  • 2 large app

  • 1 large DB

  • 200 GB DB disk

  • 2 large app

  • 1 large DB

  • 250 GB DB disk

75-150

  • 1 large app

  • 1 small DB

  • 50 GB DB disk

  • 1 large app

  • 1 medium DB

  • 50 GB DB disk

  • 2 large app

  • 1 large DB

  • 150 GB DB disk

  • 3 large app

  • 1 large DB

  • 200 GB DB disk

  • 4 large app

  • 1 enterprise DB

  • 250 GB DB disk

150-300

  • 2 large app

  • 1 medium DB

  • 50 GB DB disk

  • 2 large app

  • 1 large DB

  • 100 GB DB disk

  • 3 large app

  • 1 large DB

  • 150 GB DB disk

  • 4 large app

  • 1 enterprise DB

  • 200 GB DB disk

  • 4 large app

  • 1 enterprise DB

  • 250 GB DB disk

300-500

  • 2 large app

  • 1 large DB

  • 50 GB DB disk

  • 3 large app

  • 1 large DB

  • 100 GB DB disk

  • 4 large app

  • 1 enterprise DB

  • 150 GB DB disk

  • 4 large app

  • 1 enterprise DB

  • 200 GB DB disk

  • 4+ large app

  • 1 enterprise DB

  • 250 GB DB disk

> 500

Contact EcoSys Support for Sizing Recommendations

* The two input values for this table are derived from previous sections in this document.

Server type keys

Server Type

Description

Medium App

Java application server with 8 GB Java heap and 8 vCPUs*

Large App

Java application server with 16** GB Java heap and 2 CPU (16+ vCPUs*)

Small DB

Database server with 4 GB memory for database and 4 vCPUs*

Medium DB

Database server with 8 GB memory for database and 8 vCPUs*

Large DB

Database server with 16 GB memory for database and 8+ vCPUs*

Enterprise DB

Database server with 32 GB memory for database and 16+ vCPUs*

Combined Role****

Java application server with 4 GB Java heap, 4 GB Database. Total RAM of 10 GB and 8 vCPUs*

* 1 vCPU = 1 virtual processor identifiable by the operating system.

** The heap sizes are total heap on a single server. We recommend that you have multiple JVM instances, each with 8 GB heap. However, this approach requires a load balancer. For more information, see Horizontal Scalability (Scaling Out) and Java Instance Efficiency and Heap Size in Clustering and Horizontal and Vertical Scalability.

*** The heap sizes are total heap on a single server. We recommend that you have multiple JVM instances, each with 16 GB heap. However, this approach requires a load balancer. For more information, see Horizontal Scalability (Scaling Out) and Java Instance Efficiency and Heap Size in Clustering and Horizontal and Vertical Scalability.

**** You can use a Combined role server to deploy both the application and the database server provided performance is not a concern. EcoSys does not recommend a combined role server for Production deployment.

Further recommendations and assumptions

  1. Memory sizes for Java heap do not include RAM needed for underlying operating system, which is typically ~4 GB additional physical memory.

  2. Application servers require at least 50 GB disk free for log files and caches.

  3. All servers should be 64-bit architectures and 64-bit operating systems and applications.

  4. CPUs are sized for modern (last 3 years) clock speed and local cache sizes.

  5. Network hardware requires to support gigabit speeds.

  6. For database-intensive deployments, dedicated storage for the database is recommended. RAID-10 is preferred for performance with latency < 10ms.

  7. This table does not include the integration server sizing. Contact EcoSys support for sizing recommendations of Integration Server.

  8. This table does not include server sizing for any Disaster Recovery environment.