<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/new-in-symfony-8-2-faster-messenger-workers-symfony-blog--eqqcjtcma" -->

---
title: New in Symfony 8.2: Faster Messenger Workers (Symfony Blog)
description: Symfony 8.2 introduces a new --concurrency option for Messenger workers, letting a single worker process multiple messages in parallel using the amphp/parallel...
canonical: https://daily.dev/posts/new-in-symfony-8-2-faster-messenger-workers-symfony-blog--eqqcjtcma
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: New in Symfony 8.2: Faster Messenger Workers (Symfony Blog) | daily.dev
og:description: Symfony 8.2 introduces a new --concurrency option for Messenger workers, letting a single worker process multiple messages in parallel using the amphp/parallel...
og:url: https://daily.dev/posts/new-in-symfony-8-2-faster-messenger-workers-symfony-blog--eqqcjtcma
og:image: https://api.daily.dev/og/posts/eqQCjtCma.png
og:image:alt: New in Symfony 8.2: Faster Messenger Workers (Symfony Blog)
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# New in Symfony 8.2: Faster Messenger Workers (Symfony Blog)

**[Symfony](https://daily.dev/sources/symfony)** · 4 min read · 1 upvotes · 0 comments

## Summary

Symfony 8.2 introduces a new --concurrency option for Messenger workers, letting a single worker process multiple messages in parallel using the amphp/parallel library or the PHP parallel extension, achieving up to 7.5x speedup in benchmarks. Batch handlers don't benefit from this since all batch messages must run on the same child process. A new prefetch_count option for the AMQP transport lets RabbitMQ push messages proactively instead of one at a time, yielding 13-18x faster consumption in benchmarks, though it changes message ordering guarantees and redelivery behavior on worker stop. Delayed AMQP messages are now rounded to two significant digits by default, drastically cutting the number of delay queues created, with a configurable delay[granularity] option. A new optional logging middleware records processing time and memory usage per message for building dashboards and alerts.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://symfony.com/blog/new-in-symfony-8-2-faster-messenger-workers>

## Questions this post answers

### How do I process multiple Symfony Messenger messages in parallel with a single worker?

Symfony 8.2 adds a --concurrency option to messenger:consume that handles multiple messages at once using a pool of child processes or threads via the amphp/parallel library (or the parallel PHP extension if installed). For example, messenger:consume async --concurrency=4 handles up to four messages simultaneously. In benchmarks with 20ms messages, --concurrency=8 was 7.5 times faster than a single worker. Batch handlers are excluded since all batch messages must run in the same child process.

_daily.dev surfaces updates like this for developers tuning Symfony Messenger throughput._

### How does the new prefetch_count option speed up Symfony's AMQP Messenger transport?

Symfony 8.2's prefetch_count option registers a real consumer on each RabbitMQ queue so the broker pushes messages in advance instead of the transport fetching them one at a time, which required a network round trip per message. Benchmarks against a local broker showed 13 to 18 times faster consumption. It's disabled by default because it changes message ordering across queues and causes redelivery of prefetched messages when a worker stops.

_Track transport-level performance changes like this on daily.dev before tuning RabbitMQ consumers._

### Why does Symfony's AMQP transport create so many delay queues for retried messages?

Because AMQP has no native delay mechanism, Symfony creates a separate delay queue for each distinct delay value, and the default retry strategy adds jitter that can produce over a thousand different values, so nearly every retry declares a new queue. Symfony 8.2 fixes this by rounding delays to two significant digits by default (e.g. 5234ms becomes 5300ms), configurable via the delay[granularity] DSN option or disabled by setting it to 1.

_daily.dev helps engineers debugging AMQP queue sprawl keep up with fixes like this one._

## Similar posts on daily.dev

- [New in Symfony 8.1: Messenger Improvements \(Symfony Blog\)](https://daily.dev/posts/new-in-symfony-8-1-messenger-improvements-symfony-blog--ofndylze4) · Symfony · 4 upvotes · 0 comments
- [New in Symfony 8.2: Messenger Outbox and Claim Check \(Symfony Blog\)](https://daily.dev/posts/new-in-symfony-8-2-messenger-outbox-and-claim-check-symfony-blog--pyk9pq0hf) · Symfony · 3 upvotes · 0 comments
- [New in Symfony 8.2: Messenger Flows \(Symfony Blog\)](https://daily.dev/posts/new-in-symfony-8-2-messenger-flows-symfony-blog--shusno2km) · Symfony · 1 upvotes · 0 comments
- [New in Symfony 8.2: Performance Improvements \(Symfony Blog\)](https://daily.dev/posts/new-in-symfony-8-2-performance-improvements-symfony-blog--ef0ps6tns) · Symfony · 4 upvotes · 0 comments

---

Tags: [#performance](https://daily.dev/tags/performance), [#php](https://daily.dev/tags/php), [#symfony](https://daily.dev/tags/symfony), [#rabbitmq](https://daily.dev/tags/rabbitmq)

[View this post on daily.dev](https://daily.dev/posts/new-in-symfony-8-2-faster-messenger-workers-symfony-blog--eqqcjtcma)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"New in Symfony 8.2: Faster Messenger Workers (Symfony Blog)","url":"https://daily.dev/posts/new-in-symfony-8-2-faster-messenger-workers-symfony-blog--eqqcjtcma","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/new-in-symfony-8-2-faster-messenger-workers-symfony-blog--eqqcjtcma"},"datePublished":"2026-09-25T07:26:23.632Z","dateModified":"2026-09-25T07:26:50.709Z","description":"Symfony 8.2 introduces a new --concurrency option for Messenger workers, letting a single worker process multiple messages in parallel using the amphp/parallel...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/327b244859fddae8f3a20d0225898aa0?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/327b244859fddae8f3a20d0225898aa0?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Symfony","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Symfony","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/cc07051b7112472f9729e73c14660a64","url":"https://daily.dev/sources/symfony"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/new-in-symfony-8-2-faster-messenger-workers-symfony-blog--eqqcjtcma","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"performance,php,symfony,rabbitmq","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Symfony","item":"https://daily.dev/sources/symfony"},{"@type":"ListItem","position":3,"name":"New in Symfony 8.2: Faster Messenger Workers (Symfony Blog)"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/new-in-symfony-8-2-faster-messenger-workers-symfony-blog--eqqcjtcma#faq","mainEntity":[{"@type":"Question","name":"How do I process multiple Symfony Messenger messages in parallel with a single worker?","acceptedAnswer":{"@type":"Answer","text":"Symfony 8.2 adds a --concurrency option to messenger:consume that handles multiple messages at once using a pool of child processes or threads via the amphp/parallel library (or the parallel PHP extension if installed). For example, messenger:consume async --concurrency=4 handles up to four messages simultaneously. In benchmarks with 20ms messages, --concurrency=8 was 7.5 times faster than a single worker. Batch handlers are excluded since all batch messages must run in the same child process. daily.dev surfaces updates like this for developers tuning Symfony Messenger throughput."}},{"@type":"Question","name":"How does the new prefetch_count option speed up Symfony's AMQP Messenger transport?","acceptedAnswer":{"@type":"Answer","text":"Symfony 8.2's prefetch_count option registers a real consumer on each RabbitMQ queue so the broker pushes messages in advance instead of the transport fetching them one at a time, which required a network round trip per message. Benchmarks against a local broker showed 13 to 18 times faster consumption. It's disabled by default because it changes message ordering across queues and causes redelivery of prefetched messages when a worker stops. Track transport-level performance changes like this on daily.dev before tuning RabbitMQ consumers."}},{"@type":"Question","name":"Why does Symfony's AMQP transport create so many delay queues for retried messages?","acceptedAnswer":{"@type":"Answer","text":"Because AMQP has no native delay mechanism, Symfony creates a separate delay queue for each distinct delay value, and the default retry strategy adds jitter that can produce over a thousand different values, so nearly every retry declares a new queue. Symfony 8.2 fixes this by rounding delays to two significant digits by default (e.g. 5234ms becomes 5300ms), configurable via the delay[granularity] DSN option or disabled by setting it to 1. daily.dev helps engineers debugging AMQP queue sprawl keep up with fixes like this one."}}]}
```

