With a sufficiently large attachment table [15000 attachments totalling 12GB on a rather busy Solaris system], sanitycheck will take a long time to process the corss-check for attachments.submitter_id and apache2 will time out after 300 seconds with no output. I suspect this occurs on this specific field because there is no index on attachments.submitter_id Workaround to increase apache2 timeout to 1200 secs works, but it probably pays to fix this at its source.
Actually, it seems the apache timeout itself is not the only issue.
Severity: normal → major
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.20
Created attachment 174140 [details] [diff] [review] Patch - index submitter_id OK, adding an index on submitter_id makes almost no difference in DB size but speeds sanitycheck up to seconds. Justdave's inactive account check also speeds up dramatically.
don't suppose we'd be able to sneak an index on bugs_activity.who in here for the same reason, could we? :) That was the other "lack of index" that was slowing down my inactive account check script. It'll also speed up searches on who changed what, I would imagine.
Created attachment 174141 [details] [diff] [review] v2 -- handle bugs_activity.who at the same time OK
Attachment #174141 - Flags: review?(justdave) → review+
Flags: blocking2.20? → approval+
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.