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
Fetching normalizers not scalable / slow. #29387
Comments
Unfortunately, Drupal can't update its dependencies until Drupal 9 is released in 2020. |
Well that's too bad but how is this a Symfony issue? You can't fix what's already been fixed (see |
closing here as these changes are already available |
Let's change the question. If there is a PR for a back-port of this for 3.4. Is it going to be committed at any point? |
That wouldn't be a bug fix. So no that wouldn't be happening. |
Ok 😢. For anyone that is interested this is the issue there: https://www.drupal.org/project/drupal/issues/3017291 |
To clarify:
It is what it is. |
Description
Runtime cache on the serailizers / normalizers component system.
Example
We are using symfony/serializer as a dependency in Drupal. There is this module that seems to abuse this piece of code. and is causing very big delays (like 10-20% or request time) just finding the right normalizers.
Furhter details can be seen in Drupal's issue queue for jsonapi module: here
Direction
I've managed to drop overhead like 15-20 times with the following pseudo code.
I know it's not production ready but for you can get the idea:
Symfony\Component\Serializer\Serializer::getNormalizer($data, $format, array $context)
Additional thoughts
The text was updated successfully, but these errors were encountered: