Cron Trigger Frequency Matrix
*/5 * * * * looks innocent. That fires 8,640 times a month. Your rate limiter caps at 1,000/min and your monthly quota is 50,000. Do this math before the cron job does — capacity planning starts with knowing how often your schedules actually fire.
⏲️ Cron Schedule Parameters
Set runs per hour, active hours per day. The engine multiplies across day/week/month/year time horizons. Use this before your CI pipeline's cron schedule accidentally DDOSes your own API.
Cron Frequency: 60 Runs/Hour × 24 Hours = 43,200 Executions/Month
Cron is the quintessential Unix job scheduler, powering recurring automation across every Linux server, Kubernetes CronJob, and cloud scheduler service. A single cron expression like * * * * * — firing every minute, 24 hours a day, 7 days a week — triggers 43,200 executions per month on a 30-day calendar. Understanding this raw execution volume is the first step toward capacity planning for cron-driven architectures.
How Cron Scheduling Works
The classic cron expression consists of five fields: minute hour day-of-month month day-of-week. Each * wildcard means "every" for that field. The expression * * * * * therefore fires once per minute, every minute, every hour, every day — producing 1,440 executions per day (60 minutes × 24 hours). Other common patterns and their monthly volumes:
| Cron Expression | Meaning | Runs/Minute | Runs/Month (30d) |
|---|---|---|---|
* * * * * | Every minute | 1 | 43,200 |
*/5 * * * * | Every 5 minutes | 0.2 | 8,640 |
0 * * * * | Every hour at :00 | 0.0167 | 720 |
*/30 * * * * | Every 30 minutes | 0.0333 | 1,440 |
0 0 * * * | Once per day at midnight | 0.000694 | 30 |
Capacity Planning for Cron Workloads
When cron-triggered jobs interact with databases, APIs, or message queues, the aggregate execution frequency directly impacts infrastructure sizing. A fleet of 200 microservices each running a per-minute cron health check generates 8.64 million executions per month. Each execution may spawn a database connection, allocate memory buffers, and write log entries — compound this across a distributed system and the resource footprint becomes non-trivial. Use this calculator to model your total scheduled execution volume and right-size your supporting infrastructure.
Rate Limiting and Cascading Failures
Cron jobs that fire simultaneously across many instances — known as the thundering herd problem — can saturate downstream services instantaneously. Injecting a random jitter (sleep interval) into each cron execution, or staggering schedules across instances, is a standard mitigation. Understanding your raw execution matrix is the prerequisite for designing these safeguards and setting appropriate rate limits on upstream APIs and database connection pools.