Overview
This document briefly provides a basic description of resource usage in different scenarios and can be used as a reference for service deployment. In actual use, there may be differences due to the performance requirements of different services. Administrators need to pay attention to resource usage and make appropriate adjustments.
The production environment supports AI by default.
Standalone Deployment — Demo
Type | Total Visits/Day | Avg. Concurrent Online Visitors | Conversations a day | CPU - 2.5Ghz or Higher | RAM | HDD |
Demo - Without AI | 1 ~ 5,000 | 0 ~ 100 | 0 ~ 500 | 2-core | 8G | 50G |
Demo - With AI | 5,000 ~ 10,000 | 100 ~ 500 | 500 ~ 1000 | 4-core | 16G | 150G |
The following basic requirements also require the server to be able to expand CPU/RAM/HDD.
Application file storage HDD is only a basic requirement, depending on the type of storage service and the size of the files stored.
If the Application file storage does not use local storage and uses a third party for storage (minio, s3, blob), then HDD only keeps one base storage.
Standalone Deployment — Production
When deploying a simple project, the standalone deployment scheme can be used. It has the characteristics of being easy to deploy and manage. However, it also has the disadvantages of low resource utilization and difficulty in expansion.
Total Visits/Day | Avg. Concurrent Online Visitors | Conversation a day | CPU - 2.5Ghz or Higher | RAM | HDD - Basic requirements |
1 ~ 50,000 | 1 ~ 2,000 | 0 ~ 2000 | 16-core | 32G | 250G |
50,000 ~ 250,000 | 2,000 ~ 4,000 | 2000 ~ 5000 | 16-core | 64G | 500G |
Standalone Deployment can support up to 4000 concurrent visitors and 5000 conversations per day.
Distributed Deployment — Production
It is recommended that you perform a distributed deployment in a production environment. Under the same service configuration, a separated deployment can handle a greater number of requests. Separated deployment can also be easily expanded.
Total Visits/Day | Avg. Concurrent Online Visitors | conversations a day | Application Server | Midware Server -DB & Redis |
1 ~ 50,000 | 1 ~ 2,000 | 0 ~ 5000 | CPU: 4-core | CPU: 4-core |
RAM: 32G | RAM: 16G | |||
HDD: 150G | HDD: 250G | |||
50,000 ~ 250,000 | 2,000 ~ 5,000 | 5000 ~ 10000 | CPU: 8-core | CPU: 4-core |
RAM: 32G | RAM: 32G | |||
HDD: 150G | HDD: 500G | |||
250,000 ~ 500,000 | 5,000 ~ 10,000 | 10000 ~ 20000 | CPU: 8-core | CPU: 8-core |
RAM: 32G | RAM: 64G | |||
HDD: 150G | HDD: 1T | |||
500,000 ~ | 10000 ~ | 20000 ~ | CPU: 16-core | CPU: 16-core |
RAM: 64G | RAM: 128G | |||
HDD: 150G | HDD: 1T |
Cluster deployment
At present, we lack an automated deployment script specifically for Cluster deployment. However, when necessary, we are available to assist our partners with remote cluster deployment and installation.