# Processing Units Processing Units (PUs) measure system usage across Ellipsis Drive. They are used to track and control compute and data processing activity across the system. *** #### What generates PUs? PUs are consumed when users interact with data in Ellipsis Drive, including: * running API requests * querying spatial data * uploading or processing datasets * exporting or downloading data * running scripts or automated workflows *** #### Why PUs exist PUs help ensure fair and stable system performance across all users. They are used to: * distribute compute resources fairly * prevent excessive load from individual users * maintain consistent performance across the system #### Throttling and control PUs are also used as a control mechanism. Administrators can define usage limits to: * manage bandwidth allocation across each endpoint * prevent system overload * ensure balanced usage across teams or organisations {% embed url="" %} {% hint style="success" %} ### Important note * All interactions with Ellipsis Drive that involve data processing contribute to Processing Unit consumption. * **Processing Units are allocated as part of your data storage plan and are designed to cover normal usage, and you will not run into limits under typical workloads.** {% endhint %} --- # 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.ellipsis-drive.com/advanced-usage/processing-units.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.