--- title: "Deployment considerations" slug: "deployment-considerations-2" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:46:26Z published: 2026-09-07T17:46:26Z canonical: "docs.trellix.com/deployment-considerations-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Deployment considerations Before you deploy **Agent Handlers** in your extended network, consider the health of your existing ePO - On-prem server and database hardware. If this hardware is already overloaded, adding **Agent Handlers** actually decreases ePO - On-prem performance. A fully configured **Agent Handler** has about the same hardware and database requirements as a ePO - On-prem server. When determining how many **Agent Handlers** you need, first examine the database usage. If the database serving your ePO - On-prem server is under a heavy load, adding **Agent Handlers** does not improve your performance. Upgrade your SQL Server hardware to take advantage of multiple **Agent Handlers**. If the database is currently running at a moderate to low load, then additional **Agent Handlers** can help you expand your logical ePO - On-prem infrastructure. Trellix testing shows that adding **Agent Handlers** improves performance until your ePO - On-prem database CPU load exceeds 70 percent. Since each **Agent Handler** adds some overhead, for example database connections and management queries to the database, adding **Agent Handlers** beyond 70 percent database CPU load does not help performance.