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
$constraints[] = '(LOWER(NEOSCR_TOSTRING(n.properties)) LIKE :entity' . md5($relatedIdentifier) . ' )';
.
This causes the creation of a new entry for each related entity in the Flow_Persistence_Doctrine cache.
F.e. deleting n assets, creates n entries, which causes performance issues as by default the cache is in the filesystem and accessing the cache slows down with a large number of entries.
In a project I had to delete 100.000s of assets which completely brought various requests in Neos to a crawl due to the cache getting slow with the amount of entries.
Expected Behavior
The query should be parameterised in a way that no large number of cache entries are generated and the existing ones can be reused.
Steps To Reproduce
Delete an asset from the media module and an additional cache entry will be generated in the Flow_Persistence_Doctrine cache.
Environment
- Flow: <= 8.3
- Neos: <= 8.3
- PHP: any
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
When querying nodes by their related entities the
NodeDataRepository
creates a query with dynamic parameter names inneos-development-collection/Neos.ContentRepository/Classes/Domain/Repository/NodeDataRepository.php
Line 1716 in 28baf4c
This causes the creation of a new entry for each related entity in the
Flow_Persistence_Doctrine
cache.F.e. deleting
n
assets, createsn
entries, which causes performance issues as by default the cache is in the filesystem and accessing the cache slows down with a large number of entries.In a project I had to delete 100.000s of assets which completely brought various requests in Neos to a crawl due to the cache getting slow with the amount of entries.
Expected Behavior
The query should be parameterised in a way that no large number of cache entries are generated and the existing ones can be reused.
Steps To Reproduce
Delete an asset from the media module and an additional cache entry will be generated in the
Flow_Persistence_Doctrine
cache.Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: