Hi - > Create indexes on _r_de and _f_de tables > to speed up delete operations called by groom() function. > Primary keys of those tables are optimalized to search rows > by buildids so delete by file and mtime attributes > has to scan the whole table. [...]
By the way, another possible approach to this is could be to create those indexes only for the duration of a groom operation: Create at start, drop at end. It'd speed up a set of delete's almost as well, and also save disk space during normal operations. OTOH, the peak disk space requirement would be the same, so if the server's running low on index storage disk, it'll fail either way, so probably not worth doing this. - FChE
