Task Prioritization in Queue (Priority Queue)

Task Prioritization in Queue (Priority Queue)

Imagine: 90% of users leave your site if the password reset email doesn't arrive within 5 seconds. But your queue is clogged with 30-minute reports. Result — lost clients and negative feedback. We faced this in a project with 150,000 active users: critical tasks (password reset, SMS codes) were in the same queue as exports. After implementing prioritization, latency for critical tasks dropped from 30 seconds to 2 seconds — 15x faster. Cost savings: setup starts at $500, and clients typically see ROI within a month. Below is how we do it.

With 5+ years of queue work and over 50 projects, from startups to enterprise, our approach is to design a priority model, configure workers, and protect the system from starvation. No unnecessary abstractions, only proven patterns.

Why Queue Prioritization Is Critical for Performance?

Without prioritization, all tasks are processed in FIFO order. This causes unacceptable delays for critical operations. For example, in a high-traffic project, every 100ms of latency reduces conversion by 7%. Our clients see an 80–95% reduction in critical task response time after prioritization. Dedicated workers perform 10x better than soft priority under high load.

Priority Model

Typical three-level split:

The choice of levels depends on your business SLA. For an e-commerce store, you may add a high queue for orders. In production, we maintain critical queue depth below 10, while low queue can grow to 5000 but is processed in background.

How to Set Up Priorities in Laravel?

Laravel supports soft priority: the worker iterates queues in the specified order. Command:

php artisan queue:work --queue=critical,default,low

If there are tasks in critical, the worker does not move to default. Priority is set at dispatch:

SendPasswordResetEmail::dispatch($user)->onQueue('critical');

Or inside the Job via the $queue property. This is simple and fast, but with long tasks in the low queue, critical tasks may wait. Solution — dedicated Horizon workers.

Comparison of Soft Priority and Dedicated Workers

How to Use Dedicated Workers for Critical Tasks?

Horizon allows creating separate worker pools for each queue. Compare: soft priority — critical latency can reach minutes when low queue is loaded. Dedicated workers guarantee < 5 seconds — 10x faster. Example configuration:

// config/horizon.php
'environments' => [
    'production' => [
        'critical-supervisor' => [
            'connection' => 'redis',
            'queue' => ['critical'],
            'balance' => 'simple',
            'minProcesses' => 2,
            'maxProcesses' => 8,
            'timeout' => 30,
        ],
        'default-supervisor' => [
            'connection' => 'redis',
            'queue' => ['default'],
            'balance' => 'auto',
            'minProcesses' => 1,
            'maxProcesses' => 5,
            'timeout' => 60,
        ],
        'low-supervisor' => [
            'connection' => 'redis',
            'queue' => ['low'],
            'balance' => 'simple',
            'processes' => 2,
            'timeout' => 3600,
        ],
    ],
],

Each supervisor works independently: critical is not blocked by low tasks. This is a standard pattern for high-traffic projects.

What Is Starvation and How to Prevent It?

Starvation — low-priority tasks never get processed due to a constant influx of critical ones. This leads to endless accumulation of reports and exports. Two main solutions:

Aging — increase priority over time. Implement via scheduled job:

// Increase priority of tasks waiting more than 30 minutes
Schedule::call(function () {
    Job::where('queue', 'low')
        ->where('created_at', '<', now()->subMinutes(30))
        ->update(['queue' => 'default']);
})->everyFifteenMinutes();

Dedicated worker for low — one process guarantees that low tasks will eventually run. Combining both methods gives 100% protection.

Dynamic Priority Based on Data

Priority can be assigned dynamically based on the user. For example, enterprise clients get critical priority, ordinary users get default. This is more flexible than a static scheme and saves resources.

Priority in BullMQ (Node.js)

BullMQ uses numeric priorities via Redis Sorted Set. This is more precise than Laravel but requires separate infrastructure.

await queue.add('send-password-reset', { userId: 123 }, { priority: 1 });
await queue.add('generate-report', { reportId: 789 }, { priority: 10 });

The lower the number, the higher the priority. In Laravel it's simpler if your stack is already PHP.

Monitoring and Alerting

Queue depth is tracked via Redis: Redis::llen('queues:critical'). Horizon displays this in its dashboard. We set up alerts for queue growth — a sign of insufficient workers. Recommended thresholds: if critical > 50, default > 200, or low > 1000 — immediate notification. This prevents downtime.

What Is Included

1. Audit of current queue architecture
2. Designing priority model with SLA
3. Configuration of workers (Horizon or BullMQ)
4. Starvation prevention (aging + dedicated worker)
5. Monitoring and documentation of the setup
6. Access to monitoring dashboards
7. Team training (2-hour session)
8. 30 days of support

Timeline: basic setup of three queues — 3 to 5 hours. Anti-starvation logic and monitoring — additional 2 to 4 hours. Cost is calculated individually starting from $500 for basic setup.

Get a turnkey solution in 3–5 hours—write to us for a free stack evaluation. Order queue setup and receive a consultation for your stack.

Learn more about Laravel Horizon (official documentation)

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.