Skip to content

[Serializer] ensure ChainEncoder/ChainDecoder properly consider the context #43231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from

Conversation

Guite
Copy link
Contributor

@Guite Guite commented Sep 28, 2021

Q A
Branch? 4.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets Fix #38270
License MIT
Doc PR -

This PR removes the "caching" of encoder/decoder instances in a chain so they are re-evaluated for each single call.

The corresponding tests are extended to perform multiple calls with different context arrays. Also they now check not only if encoding/decoding is supported, but also that the responsible encoder/decoder instance is the correct (expected) one.

/cc @xabbuh

@dunglas
Copy link
Member

dunglas commented Sep 29, 2021

We must be very careful when touching this part. Removing such cache can have a dramatic performance impact, as it's on the hot path. We need to profile and to double-check that it doesn't make complex apps very slow. We'll probably have to do something like this: #27105

cc @nicolas-grekas.

@dunglas
Copy link
Member

dunglas commented Sep 29, 2021

I think that we should just replicate the logic introduced for normalizers in #27105. Cache when not dynamic, and don't cache when it is.

@lyrixx
Copy link
Member

lyrixx commented Sep 29, 2021

Another implementation of the chain could be added, it would be simpler IMHO, since it's an edge case

@Guite
Copy link
Contributor Author

Guite commented Oct 1, 2021

Cache when not dynamic, and don't cache when it is.

Dynamic would be a context that is not just an empty array?

@Guite
Copy link
Contributor Author

Guite commented Oct 1, 2021

I readded caching arrays but utilize them only if no dynamic context is given.

@nicolas-grekas
Copy link
Member

I propose checking for ContextAwareEncoreInterface instead, see #47150
WDYT? Can you update the PR accordingly?

@nicolas-grekas
Copy link
Member

Closing in favor of #47304

chalasr added a commit that referenced this pull request Aug 21, 2022
…erface` and `ContextAwareDecoderInterface` (nicolas-grekas)

This PR was merged into the 6.1 branch.

Discussion
----------

[Serializer] Revert deprecation of `ContextAwareEncoderInterface` and `ContextAwareDecoderInterface`

| Q             | A
| ------------- | ---
| Branch?       | 6.1
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | -
| License       | MIT
| Doc PR        | -

While reviewing #43231, I figured out that the correct fix for #38270 was to make `ChainEncoder` properly consider `ContextAwareEncoderInterface` when deciding to cache or not.

Since this interface is useful to discriminate the cache/no-cache situations, we have to undeprecate it (from #43982.)

/cc `@Guite` and `@mtarld` FYI

Commits
-------

9ac7fb1 [Serializer] Revert deprecation of `ContextAwareEncoderInterface` and `ContextAwareDecoderInterface`
chalasr added a commit that referenced this pull request Aug 21, 2022
…n ChainEncoder/ChainDecoder (Guite)

This PR was merged into the 4.4 branch.

Discussion
----------

[Serializer] Fix caching context-aware encoders/decoders in ChainEncoder/ChainDecoder

| Q             | A
| ------------- | ---
| Branch?       | 4.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | Fix #38270
| License       | MIT
| Doc PR        | -

As proposed in #43231 (comment)
Will require #47150 on 6.1 until a proper solution is implemented, hopefully in 6.2.

Commits
-------

5902380 [Serializer] Fix caching context-aware encoders/decoders in ChainEncoder/ChainDecoder
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.

6 participants