| 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 | 2.0 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 |
Data retention
Function call history is retained for 90 days from the call date. After this period, call history data is automatically deleted and cannot be recovered. Back up any important call history before the retention period expires using the Functions API or implement custom logging to store execution data externally.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 thedata 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.