- Issue created by @steven jones
- Status changed to Needs work
over 1 year ago 4:31pm 20 February 2023 - 🇬🇧United Kingdom steven jones
Here's a patch for point 1, it doesn't add the new event.
I've got fairly simple setup in that I have some smartqueues based on a large-ish taxonomy.
When editing the taxonomy to re-order the terms we see incredibly high memory usage and timeouts.
In the above setup, re-order some terms using the Drupal admin UI.
As far as I can see it's because if a term is updated, then the associated smartqueue is re-saved. This seems kinda wasteful. It sort of looks like the code is only trying to update the label.
I suppose that there could be other code that is triggering off of this update, so it's possible that we should:
* Stop the save
* Introduce another event
* Bump the API version.
Do all the above.
None.
We'd remove an entity update, and add a new event to cover this.
None.
Needs work
1.0
Code
Here's a patch for point 1, it doesn't add the new event.