How to Meter Execution DurationMeasuring CPU Hours of containers, pods, and serverless in seconds
Blog post from OpenMeter
Cloud and DevOps companies often charge customers based on execution duration, such as CPU hours. However, metering workloads can be complex due to challenges in detecting start and stop events, handling lost events, long-running workloads, and shifting billing periods. An alternative approach is heartbeat style metering, which involves periodically checking if a workload is running and incrementing a counter associated with the workload. This method reduces the possibility of under or overbilling due to missing lifecycle events and offers more accurate usage tracking. However, it generates a high volume of usage events that may require streaming aggregation for efficient processing.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Real-time | 5 | 1,908 | 482 | 162 | -16% |
| Serverless | 2 | 908 | 137 | 68 | +58% |
| Kubernetes | 1 | 3,288 | 253 | 67 | +116% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.