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
The SiteTree extension, when calling 'default records' function, queries the QueuedJobDescriptor table for a ContentReviewJob. However it is doing so using the Implementation column which does not have any index associated.
As the QueuedJobDescsriptor.Implementation column is a varchar(255), it is having to do a full-scan on the table when searching, this takes quite a while to perform and gets exponentially worse with the more records in this table.
E.g. A QueuedJobDescriptor table with 180k records takes over 1 minute to run this single query.
The text was updated successfully, but these errors were encountered:
Thanks for raising this @brettt89! Unfortunately this isn't really an issue with the Content Review module, and it's certainly not solvable by this module (short of applying an extension to the QueuedJobDescriptor model to patch in an index, which definitely feels like the wrong approach.)
Since an issue addressing this has also been raised about this on the Queued Jobs module, I think we'll close this one out in favour of tackling the resolution there.
The SiteTree extension, when calling 'default records' function, queries the QueuedJobDescriptor table for a ContentReviewJob. However it is doing so using the
Implementation
column which does not have any index associated.https://github.com/silverstripe/silverstripe-contentreview/blob/4/src/Extensions/SiteTreeContentReview.php#L666
As the
QueuedJobDescsriptor.Implementation
column is avarchar(255)
, it is having to do a full-scan on the table when searching, this takes quite a while to perform and gets exponentially worse with the more records in this table.E.g. A
QueuedJobDescriptor
table with 180k records takes over 1 minute to run this single query.The text was updated successfully, but these errors were encountered: