Info |
---|
All the estimates projected are based on tests performed for 24 hours on single namespace/ single cluster concept with multiple concurrent users and a shared RDS for Bahmni Lite 1.0 release. |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Clinic setup - 2 frontdesk users, 2 doctors (4 users)* Smaller clinic setup - 1 frontdesk user, 1 doctor (2 users)* |
Cost Estimation Sheet with Results
Comprehensive approximate estimates are found test results and calculation estimates can be viewed in this document: Bahmni Lite Setup and Cost Estimation
The following below analysis explains the various design factors that were taken into consideration during the estimation above performance test calculation process.
Lesser clinics cluster (approx 40 concurrent users)
Info |
---|
t3.large instance is suggested for Bahmni lite implementation since the number of active pods may vary from “14 to 22” based on the requirement. t3.large supports upto 35 kubernetes pods and enables seamless deployments. |
Hardware
Node (EC2: t3-large)
RAM 8GB
2 vCPU
AWS LINUX x86_64
Max pods supported: 35
Database (AWS RDS service: db.t3.xlarge)
...
2 users clinic setup (maximum*)
1 to 24 clinics
Cost Estimation
Comprehensive approximate estimates are found in this document
Bahmni Lite Setup and Cost Estimation
More clinics cluster (approx 70 concurrent users)
Info |
---|
m5.xlarge instance is suggested for Bahmni lite implementation on this setup since both the CPU and RAM availability is twice than t3.large and supports upto 58 kubernetes pods. |
Hardware
Node (EC2: m5-xlarge)
RAM 16GB
4 vCPU
AWS LINUX x86_64
Max pods supported: 58
Database (AWS RDS service: db.t3.xlarge)
...
2 users clinic setup (maximum*)
25 to 40 clinics
Cost Estimation
Comprehensive approximate estimates are found in this document
...
*- The number of users assumed are based on the number of requests sent by a user on an average to the server and typical clinic setup observed from real time sources.
...