# Choosing the right Tellius cluster size Tellius runs on a high-performance compute engine designed to quickly answer business questions. Because each organization has different data volumes, usage patterns, and peak activity windows, there’s no one-size-fits-all approach to cluster sizing. The following three key factors play a major role in determining the right configuration: ### **How much infrastructure will I use?** Tellius features fully automated scaling, allowing infrastructure resources to increase or decrease based on demand. As you begin loading data and using the platform, you’ll gain insights into your environment’s typical resource consumption throughout the day—tailored to your specific use case. ### **What kind of workload do I have?** * **Search-focused**: Most users rely on Natural Language Search and Vizpad dashboards. Only a few users create Insights. * **Balanced (Search & Insights)**: Your user base is evenly split between those using Natural Language Search and those building Insights. * **Insights-focused**: Most users create their own Insights or machine learning models, with minimal use of Natural Language Search. ### **What is my ETL pattern?** * **Once or twice per day**: You load data during only one or two periods throughout the day. This load usually happens when usage is low. * **Three or more times per day**: You load data during three or more periods throughout the day. This load may happen when usage is high. --- # 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://help.tellius.com/tellius-6.3/getting-started/admin-guide/choosing-the-right-tellius-cluster-size.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.