Cloud provider limitations
The table outlines technical specifications and limits that are specific to the cloud provider.
| Specification | Azure | AWS | |
|---|---|---|---|
| Functions per CDF project | 100 | 100 | 100 |
| Running calls per CDF project | 250 | 250 | 250 |
| Running calls per function | 100 | 100 | 100 |
| Schedules per project | 1000 | 1000 | 1000 |
| Schedules per function | 100 | 100 | 100 |
| CPU cores per function call | default: 1.0, maximum: 3.0 | 1.0 (not configurable) | 1.0 (not configurable) |
| RAM per function call | default: 1.5 GB, maximum: 5.0 GB | 1.5 GB (not configurable) | 1.5 GB (not configurable) |
| Function call timeout | 9 minutes | 10 minutes | 10 minutes |
| Function call data payload size | 9 MB | 36 kB | 240 kB |
Manage quotas
To manage quotas effectively, consider adopting the following guidelines:
Utilize schedules
Each Cognite Function can manage up to 100 schedules. To run the same function with different configurations, use the data field in the schedule. For example, if calculations vary across multiple sites, include the logic in the function code and trigger the correct version based on configuration. This combines multiple sites into one function, reducing the need for separate ones and optimizing quota use.
Regular audit and clean-up
With time, some Cognite Functions may become obsolete or unused, consuming quota unnecessarily. Audit your deployed functions regularly to ensure only active, relevant ones remain. Remove outdated functions to free up quota for new tasks and improve resource efficiency.
Governance
As the number of Cognite Functions increases, use version control systems (e.g., GitHub, Azure DevOps) to manage code and deployments. The CDF Toolkit simplifies deployment management. Assign owners to functions to ensure accountability during audits and clean-up.