281787 - Sanitycheck times out with sufficiently large attachment table

Status: RESOLVED FIXED

(Bugzilla :: Bugzilla-General, defect, P2)

Description

[Joel Peshkin]

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.

Comment 1

[Joel Peshkin]

Actually, it seems the apache timeout itself is not the only issue.  

Comment 2

[Joel Peshkin]

Attachment: 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.

Comment 3

[Dave Miller [:justdave]]

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.

Comment 4

[Joel Peshkin]

Attachment: v2 -- handle bugs_activity.who at the same time

OK

Comment 5

[Joel Peshkin]

checked in