What is Worker?
A process or thread that picks up and executes jobs from a queue.
Definition
A worker is a process dedicated to executing tasks. In a job queue system, workers pull jobs from the queue one at a time (or in batches) and process them. Workers can run on the same machine as the scheduler or on dedicated servers. The number of available workers determines how many jobs can execute simultaneously. In CronJobPro's architecture, workers are the distributed processes that send HTTP requests to your endpoints at scheduled times.
Simple Analogy
Like employees at a post office counter — each worker handles one customer (job) at a time, and more workers mean more customers can be served simultaneously.
Why It Matters
Worker capacity determines your system's throughput. If you have 1,000 jobs scheduled for the same minute but only 10 workers, 990 jobs will be delayed. CronJobPro scales its worker pool automatically to handle peak loads, ensuring your jobs execute on time even during busy periods.
How to Verify
In self-hosted systems, check the number of worker processes: `ps aux | grep worker`. In CronJobPro, worker scaling is automatic and transparent. Monitor execution latency (time between scheduled time and actual start) — increasing latency indicates insufficient workers.
Common Mistakes
Running too few workers, causing job execution delays during peak times. Running too many workers, wasting memory and CPU resources. Not configuring worker health checks, allowing crashed workers to sit idle.
Best Practices
Right-size your worker pool based on job volume and execution duration. Monitor worker utilization and scale based on queue depth. Use CronJobPro's managed infrastructure to avoid worker management entirely. Set up health checks so dead workers are automatically replaced.
Documentation
Read the full docs
Try it free →Frequently Asked Questions
What is Worker?
A worker is a process dedicated to executing tasks. In a job queue system, workers pull jobs from the queue one at a time (or in batches) and process them. Workers can run on the same machine as the scheduler or on dedicated servers. The number of available workers determines how many jobs can execute simultaneously. In CronJobPro's architecture, workers are the distributed processes that send HTTP requests to your endpoints at scheduled times.
Why does Worker matter for cron jobs?
Worker capacity determines your system's throughput. If you have 1,000 jobs scheduled for the same minute but only 10 workers, 990 jobs will be delayed. CronJobPro scales its worker pool automatically to handle peak loads, ensuring your jobs execute on time even during busy periods.
What are best practices for Worker?
Right-size your worker pool based on job volume and execution duration. Monitor worker utilization and scale based on queue depth. Use CronJobPro's managed infrastructure to avoid worker management entirely. Set up health checks so dead workers are automatically replaced.
Related Terms
Job Queue
An ordered list of pending jobs waiting to be picked up and executed by workers.
Daemon
A background process that runs continuously and performs tasks without direct user interaction.
Execution Latency
The delay between a job's scheduled time and when it actually begins executing.
Horizontal Scaling
Adding more servers to handle increased load, rather than upgrading a single server.