Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Messenger] Remove message from messenger data collector#28420

Closed
pierredup wants to merge 1 commit intosymfony:masterfrom
pierredup:messenger-profiler
Closed

[Messenger] Remove message from messenger data collector#28420
pierredup wants to merge 1 commit intosymfony:masterfrom
pierredup:messenger-profiler

Conversation

@pierredup
Copy link
Contributor

Q A
Branch? master
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #28350 (comment)
License MIT
Doc PR

The messenger data collector currently stores the full message object, which can cause a big increase in memory usage. Based on @nicolas-grekas feedback in #28350 (comment), we should store less information. This PR starts by removing the message object from the profiler and to open the conversation about what information is required in the profiler or what can be optimized.

Before:
screen shot 2018-09-10 at 09 44 14

After:
screen shot 2018-09-10 at 09 41 17

@ogizanagi
Copy link
Contributor

I'm 👎 for this, as it's nothing comparable to the cache collector.

All these information are valuable, both for dev and tests, and you usually won't have more than a few messages dispatched per request, with really simple payloads. So I won't fear any big memory increase.
#28418 is enough to me. Perhaps we could also consider ignoring messages dispatched from CLI in the TraceableMessageBus.

@sroze
Copy link
Contributor

sroze commented Sep 10, 2018

Same: 👎. It's a really important information. If the message itself is too big, then that's where the issue is :)

Thank you for your time putting a PR together.

@sroze sroze closed this Sep 10, 2018
@pierredup pierredup deleted the messenger-profiler branch September 10, 2018 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants