Difference between revisions of "Hardware Sizing"

From SmartHCM Wiki
Jump to navigation Jump to search
Line 9: Line 9:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! ID !! Topology !! EC2 instance type !! EC2 instance type (application server) !! EC2 instance type (database server) !! Optimal concurrent users !! Architecture !! Bandwidth !! Hardware equivalence (single server) !! Hardware equivalence (application server) !! Hardware equivalence (database server)
+
! ID !! Topology !! EC2 instance type !! EC2 instance type (app server) !! EC2 instance type (DB server) !! Optimal concurrent users !! Architecture !! Bandwidth !! Hardware equivalence (single server) !! Hardware equivalence (app server) !! Hardware equivalence (DB server)
 
|-
 
|-
| Example || Example || Example || Example || Example || Example || Example || Example || Example || Example || Example
+
| 1. || Single || c3.xlarge || Example || Example || Example || Example || Example || Example || Example || Example
 
|-
 
|-
 
| Example || Example || Example || Example || Example || Example || Example || Example || Example || Example || Example
 
| Example || Example || Example || Example || Example || Example || Example || Example || Example || Example || Example

Revision as of 06:32, 14 September 2021

Introduction

A sizing is an approximation of the hardware resources required to support a specific software implementation, in this case SmartHCM. This document sets main foundations towards sizing the hardware required to run SmartHCM. SmartHCM has experience managing internal product installations on the basic instance types provided by Amazon EC2: m1.small, c1.medium and m1.large. We know the results that these instances can provide us, both in terms of performance and scalability. At the same time SmartHCM embraces experience of our customers running product on physical hardware and also using virtualization. In addition to this SmartHCM does performance tests for particular product usage scenarios. These three inputs has allowed us to write a table comparing the hardware resources needed to support particular number of concurrent users.

Sizing Table

ID Topology EC2 instance type EC2 instance type (app server) EC2 instance type (DB server) Optimal concurrent users Architecture Bandwidth Hardware equivalence (single server) Hardware equivalence (app server) Hardware equivalence (DB server)
1. Single c3.xlarge Example Example Example Example Example Example Example Example
Example Example Example Example Example Example Example Example Example Example Example
Example Example Example Example Example Example Example Example Example Example Example
Example Example Example Example Example Example Example Example Example Example Example

Important Sizing Notes