How to Fix a Slow Laravel Queue: 3 Common Performance Killers
Is your Laravel queue job taking too long? Discover the top three reasons for high latency—worker starvation, oversized Eloquent payloads, and excessive failed job retries—and how to fix them for good.
Setting up queues in Laravel is easy. Optimizing them for actual production traffic is where the real work begins. If your jobs are taking too long, don't blame the queue driver first - check these three critical areas instead. 1. Check for Worker Starvation On shared hosting or basic VPS setups, a forgotten cron entry is the #1 cause of queue latency. If your workers aren't running, jobs just pile up silently. Make sure your php artisan queue:work command is running 24/7 (or use Supervisor/Horizon for robust uptime). 2. Cut Down your Job Payloads The most frequent mistake I fix is passing entire Eloquent models into jobs. When you push a job to Redis or the database, it serializes the whole object - including all its eager-loaded relationships. Pro-Tip: Pass just the model id, and fetch the data inside the handle() method instead. This shrinks your payload by 95%, drastically speeding up your queues. 3. Stop the Failed Job Retry Loop Regularly check your failed_jobs table. A 40% retry rate usually means your job is hitting an external API that is flaky or your database is timing out. The solution isn't a higher tries limit - it's splitting the job. De-couple external API calls into their own dedicated micro-job. If one fails, the entire workflow doesn't stall. Need a second opinion on your Laravel architecture? Check out my software engineering projects or reach out below.