# CPU Sizing CPU sizing is a key factor when planning the capacity of a ONEWEB deployment.\ The following guidelines provide a **rough estimation** to help determine the number of CPU cores required based on expected user load. *** ### **Baseline Guidelines** * **1 CPU core**\ Supports up to **200 active users**\ However, performance may be slightly slower because all application workers and background jobs run on the same core. * **2 CPU cores (Recommended minimum)**\ Supports up to **400 active users**\ This configuration provides better responsiveness and allows background processes to run more efficiently. *** **Estimation Formula (Rule of Thumb)** A simple estimation for CPU sizing can be calculated as: ``` Number of CPU cores ≈ Number of active users ÷ 200 ``` Always **round up** to the nearest whole number. **Example:** ``` 500 active users ÷ 200 = 2.5 → Round up to 3 CPU cores ``` *** ### **Important Considerations** This estimation provides a baseline only. For more accurate sizing, additional factors should be considered, including: * Application complexity * Number and type of transactions * Background jobs and scheduled processes * Integration with external systems Systems with complex workflows or heavy integrations may require more CPU resources than the baseline estimation. *** ### **Assumption Used in This Estimation** The CPU sizing guideline is based on the following assumption: > **Each active user generates approximately 2 requests or transactions per minute.** If your application workload deviates significantly from this assumption (for example, higher transaction frequency or heavier processing per request), CPU capacity should be adjusted accordingly. *** ### **Architectural Context** CPU sizing decisions should always be aligned with: * Selected architecture (Standalone, High Availability, or Cloud) * Active‑Active vs Standalone deployment models * Peak load and burst traffic scenarios This ensures that the platform can maintain acceptable performance under both normal and peak conditions. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.onewebstack.com/oneweb-platform-th/getting-started/installation-guide/plan-your-oneweb-installation/sizing-consideration/cpu-sizing.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.