In this lesson, you will learn how to optimize the relationship between your RTOS system tick frequency and the resolution of your software timers to keep your CPU utilization efficient.
The Tick Frequency Dilemma
The RTOS system tick acts as the "heartbeat" of your scheduler. Every time this hardware timer fires, the CPU is interrupted, the scheduler runs, and the tick count increments. While a high-frequency tick (e.g., 1000Hz) provides 1ms resolution for your periodic tasks, it imposes significant overhead. Each interrupt forces a context switch check and pushes the CPU out of its idle state or current task, consuming cycles just to manage the passage of time.
Resolution vs. Overhead
If your application requires a 50ms periodic sensor check, a 1ms tick is overkill. If you set your tick frequency to 100Hz (10ms resolution), the system remains idle longer, saving power and CPU bandwidth. However, if you have a task that requires a strict 5ms response, a 100Hz tick will fail to trigger it with the required precision.
To balance this, follow these heuristics:
- Match the Tick to the Greatest Common Divisor (GCD): Choose a tick rate that is the largest interval that divides evenly into all your required task periods.
- Use Hardware Timers for High Precision: If only one task needs microsecond-level timing, do not raise the global system tick. Instead, use a dedicated hardware timer interrupt for that specific task and keep the system tick coarse.
Consider this scenario:
// High overhead: 1ms tick interrupts the CPU 1000 times/sec
#define RTOS_TICK_RATE_HZ 1000
// Optimized overhead: 10ms tick interrupts the CPU 100 times/sec
// All periodic tasks are multiples of 10ms (e.g., 20ms, 50ms, 100ms)
#define RTOS_TICK_RATE_HZ 100
By aligning your system’s heartbeat with the slowest common denominator of your timing requirements, you reclaim CPU cycles that would otherwise be wasted on redundant scheduling overhead. Only "tick up" if the functional requirement for high-resolution timing across multiple tasks strictly demands it.
Key Takeaway: Minimize your RTOS tick frequency to the largest possible interval that satisfies all periodic requirements to significantly reduce CPU context-switching overhead.