> For the complete documentation index, see [llms.txt](https://docs.ellipsis-drive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ellipsis-drive.com/advanced-usage/processing-units.md).

# 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="<https://drive.google.com/file/d/1nb6tykFcAlNoiJebLxE3uAGwQYAo_LrY/view?usp=share_link>" %}

{% hint style="success" %}

### Important note

* All interactions with Ellipsis Drive that involve data processing contribute to Processing Unit consumption.&#x20;
* **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 %}