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
This is a bit of a followup to #2076
While that one turned out to not really be an issue with the current beta, I still realized that the indexing on the database is less than ideal, which definitely could lead to performance degradation in larger setups
Some cases I could find rather quickly, that were not indexed at all:
Recipe.name and created_at, these are pretty surely the fields that are most commonly ordered by
A lot of foreign keys that do get used for joins, e.g. everything on the recipe_to_* tables or recipe_ingredient.recipe_id
Proposed/Possible Solution(s)?
I'm not super aware of all the inner workings to know which other places they should be added, but i guess it should at least be those two recipe fields and all foreign keys (i dont really see much of a reason to not ever have them there)
I can do the work on that, but i'd rather wait for feedback on #2070 so i dont have to do it twice
The text was updated successfully, but these errors were encountered:
What is the problem this task addresses?
This is a bit of a followup to #2076
While that one turned out to not really be an issue with the current beta, I still realized that the indexing on the database is less than ideal, which definitely could lead to performance degradation in larger setups
Some cases I could find rather quickly, that were not indexed at all:
Proposed/Possible Solution(s)?
I'm not super aware of all the inner workings to know which other places they should be added, but i guess it should at least be those two recipe fields and all foreign keys (i dont really see much of a reason to not ever have them there)
I can do the work on that, but i'd rather wait for feedback on #2070 so i dont have to do it twice
The text was updated successfully, but these errors were encountered: