--- title: "Best practices for using SuperAgent" slug: "best-practices-for-using-superagent" tags: ["Agent", "Product Usage"] updated: 2026-08-26T19:15:25Z published: 2026-08-26T19:15:25Z canonical: "docs.trellix.com/best-practices-for-using-superagent" --- > ## 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. # Best practices for using SuperAgent Traffic between locations can be reduced by ensuring best practices when enabling **SuperAgent** in your network. - Enable **SuperAgent** servers on PCs or virtual systems. Don't enable a **SuperAgent** server on laptops or other mobile devices. - Avoid setting up **SuperAgent** servers on systems with poor network connectivity or are connected using VPN. - Set up at least one **SuperAgent** per subnet to reduce the network load. Each **SuperAgent** can handle 1024 requests concurrently. - If you set up **SuperAgent Hierarchical Update**, make sure that your hierarchy of **SuperAgents** is no more than three levels. - Configure the **Max. disk quota** to be greater than the disk space requirement for all commonly used applications and their updates. For example, if the DAT file size is 150 MB and the average product update size is 100 MB, the purging disk quota should be more than 250 MB. :