AdamKatzDev

@IlyaTsoi interesting, worth taking a look @aadant I've analyzed dump for a `-xmx10G` run:  The relative picture haven't changed much, there is `queryToRecordsMap` field with 68% of memory consumed...

Me and my colleague have managed to fix the problem described here. It is actually not a single bug but a whole pile: - Messenger worker is not handling SIGINT...

@lermontex, sure. To anyone that tries to use this crutch, this is a part of the full solution, you need to add UUID to your messages to remove duplicates. The...

@lermontex You have to add UUID to every message to be able to use Redis transport with batch handlers, take a look at @zip-fa's solution for the implementation details. Basically...

While working on this https://github.com/symfony/symfony/pull/49028 PR I've realized that I can't fix the issue fully for batch handlers without fixing this issue first. A solution that could be implemented is...

So, we've build our own transport instead. We've made some opinionated changes there to make it work as we needed, so it is not a perfect replacement for the Symfony...

@dkarlovi >Messenger worker is not handling SIGINT properly, which leaves messages in batch unprocessed. Can be fixed by implementing a pcntl_signal handler. SIGTERM is handled properly in StopWorkerOnSigtermSignalListener. Fixed in...

I could provide the transport implementation in a draft. But I am afraid I won't have time to make the complete PR myself.

There is also another issue that can be confusing for someone who switch from AWS SQS, for example, and described in https://github.com/symfony/symfony/issues/51604 and in https://github.com/symfony/symfony/issues/44400#issuecomment-1096806779. Without unique consumer names with...

I've provided a workaround for this issue [here](https://github.com/symfony/symfony/discussions/46869#discussioncomment-6164399). But as I mentioned this is not something that could be contributed as a PR.