cubxxw
commented
10 months ago Hi @caesar168,
Thank you for bringing this up. It is a good idea to set the parameters of the components under K8S as quasi-standard as the standard configuration of the production environment. This will help users to provide the best parameters to the greatest extent.
To implement this, we can define a standard configuration for the production environment and document it in the OpenIMSDK documentation. We can also provide examples of how to set the parameters for the components under K8S based on this standard configuration. This will prevent OpenIM from looking like a toy and provide medium to high availability rather than minimal availability.
Let me know if you have any questions or concerns.
Checklist
Is this feature request related to a problem?
None
Problem Description
It is recommended that the project team try to set the parameters of the components under K8S as quasi-standard as the standard configuration of the production environment. For example, according to the average daily online 100,000, the throughput is 10 million, and the storage is 2T per day. This prevents the openim from looking like a toy. This approach is used in other large software, such as CEPH, which provides medium to high availability rather than minimal availability.
Solution Description
For example, according to the average daily online 100,000, the throughput is 10 million, and the storage is 2T per day. This prevents the openim from looking like a toy. This approach is used in other large software, such as CEPH, which provides medium to high availability rather than minimal availability.
Benefits
It can help users to provide the best parameters to the greatest extent.
Potential Drawbacks
No response
Additional Information
No response