While our Neos projects grow, I am identifying more and more parts of Neos which are difficult to scale with big numbers of nodes.
My current problem is the asset usage calculation done in
AssetUsageInNodePropertiesStrategy - it does a like query searching for asset references in the property fields of all nodes. With about 500K nodes currently, this takes some time. The details view of an asset needs about 6 seconds to render, checking about 10K assets for unused ones about 14 hours.
Are there any solutions out there to get this operation faster?
One solution I can think of, is to add another table besides the nodeData table with asset references to assist a faster lookup of asset usages.
The downside of course is the effort to keep the nodeData and this referencing table in sync which is always a hard task.
Another one is to use elastic for the lookups (having elastic in sync with the node data is already crucial in this projects)
Any thoughts on this would be very welcome.