You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stop retaining transport messages after serialization (#122981)
We should not retain messages after serialization. We currently, have no
0-copy logic in place outside of some special cases that are handled
separately. As a result of not doing zero-copy logic, there is no need
to retain messages until they have been flushed to the wire in full.
This change reduces the lifetime of things like `SearchHit`
significantly, reducing the data-node side impact of fetching large
documents/large aggregations/top-hits to name a few.
The fact that this change technically passes released request + response
instances to the `messageListener` seems irrelevant since the listeners
are only used in tests anyway. If anything, we should look to refactor
this logic to avoid holding on to the request/response objects
needlessly.
0 commit comments