Open Bug 506758 Opened 15 years ago Updated 10 years ago

Large numbers of attachments makes checksetup painfully slow

Categories

(Bugzilla :: Attachments & Requests, defect)

3.2.3
x86
Linux
defect
Not set
normal

Tracking

()

People

(Reporter: gregaryh, Unassigned)

Details

Attachments

(1 file)

We are using bigfile attachment support with attachments saved to the filesystem instead of the database. We have over 300,000 attachments representing 85GB of data. Running checksetup can take on the order of half an hour or more since it has to check each of these files separately.

I wonder how necessary it is to do this check each time checksetup is run. Would it be possible to only check the files individually if there is an explicit option passed for this. Is there harm in this approach?
This is a simple method. Just ignore the children of attachments unless explicitly told to update them.
Assignee: attach-and-request → ghendricks
Attachment #390917 - Flags: review?(mkanat)
I disagree with this patch. By default, this means permissions won't be set and everybody is going to wonder why. It should rather be --skip-attachments or something like that, i.e. revert the logic.
Attachment #390917 - Flags: review?(mkanat) → review-
Comment on attachment 390917 [details] [diff] [review]
possible solution

There are two options here:

1) Implement this the way LpSolit described.

2) See if shelling out to the system "chmod -R" (if available) is faster in this particular instance, or if there's a better way to do this permissions change for a directory and all its files with the normal Perl chmod command.
Whiteboard: [es-gnome]
Whiteboard: [es-gnome]
Assignee: gregaryh → attach-and-request
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: