This page provides an overview of resource requirements, monitoring, and alert configurations for Prophecy deployments.
Resource requirements
We suggest allocating the following resources to a Prophecy deployment that enables Prophecy Automate, Copilot, and Knowledge Graph.
The following are estimated recommended cluster sizes depending on the number of concurrent users:
| Number of users | 25 | 50 | 100 |
|---|---|---|---|
| CPUs | 78 - 96 vCPUs | 126 - 140 vCPUs |
216 - 250 vCPUs |
| Memory | 142 GB |
290 GB |
440 GB |
The recommended resource may vary based on the intensity of the usage of each developer. The numbers presented above are based on the average recorded usage of Prophecy customers.
Resource usage and monitoring
To better understand how Prophecy is using resources, you can find an overview in Settings > Admin > Monitoring. The different components correspond to the microservices that run on the Kubernetes cluster.
When usage levels reach yellow or red zones, you can choose whether to allocate additional resources. In most cases, temporary spikes in CPU and memory usage type do not necessitate action.
| Resource | Usage | Suggested action |
|---|---|---|
| CPU | Red zone persists for more than 1 hour | CPU allocated to the service is under-provisioned. Increase by 10%. |
| Memory | Red zone persists for more than 1 hour | Memory allocated to the service is under-provisioned. Increase by 10%. |
| Storage GBytes | Yellow zone is reached | Increase the storage capacity of the PVC in your Kubernetes deployment that corresponds to the service. |
| Storage File Count | Yellow zone is reached | Increase the storage capacity of the PVC in your Kubernetes deployment that corresponds to the service. |
If you need help increasing resources for a service in your Kubernetes deployment, reach out to Prophecy support.
Resource usage alerts
To set up automated alerts about your resource usage, visit the page on Alerts Configuration.