Hello,
as you may know, there are some performance issues we need to get rid of.
I propose that we integrate the caching strategy directly into Decidim.
This will allow us to define cache keys and test behaviors for particular associations.
We could use one of the tools mentioned in the following article:
https://evilmartians.com/chronicles/fighting-the-hydra-of-n-plus-one-queries
There are two objectives, the first being to improve the display speed of Decidim's content, the second being to improve the speed of writing to the database.
Maybe we could start by defining what to test and when to test?
Hello,
as you may know, there are some performance issues we need to get rid of.
I propose that we integrate the caching strategy directly into Decidim.
This will allow us to define cache keys and test behaviors for particular associations.
We could use one of the tools mentioned in the following article:
https://evilmartians.com/chronicles/fighting-the-hydra-of-n-plus-one-queries
There are two objectives, the first being to improve the display speed of Decidim's content, the second being to improve the speed of writing to the database.
Maybe we could start by defining what to test and when to test?