Opened 17 years ago
Last modified 9 years ago
#6807 new enhancement
Option to skip revisions with lots of added files
Reported by: | moisei | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | version control/changeset view | Version: | |
Severity: | normal | Keywords: | performance |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
On the real production systems with several millions LOC, it should be possible to skip the revisions that contain initial import of the sources into svn. Such a revisions could contain thousands of files and to trac it takes a hours to process such a revision, probably because of the indexing or code diff calculation.
The request is to have an option to skip such a revision, i.e. either make them invisible to trac somehow, or make trac know to take the special care of such a cases. Ideally, trac could detect such a revisions by itself and proceed according to some config. The huge revisions could be detected by the size of the revision file, for example.
Attachments (0)
Change History (3)
comment:1 by , 17 years ago
Component: | general → changeset view |
---|---|
Milestone: | → 0.12 |
Owner: | changed from | to
Summary: | Option to skip certain svn revisions → Option to skip revisions with lots of added files |
comment:2 by , 14 years ago
Keywords: | performance added |
---|
comment:3 by , 9 years ago
Owner: | removed |
---|
With Trac 0.11, the TracFineGrainedPermissions (authz_policy style) should allow you to block some specific revisions.
Could you please have a try of this approach?
For the auto-detection part, there's already two settings that you can tweak, see TracIni#changeset-section (max_diff_…).
However, if the expensive changeset consists of only ADDed files, then this won't help. It might be worth adding a
max_added_files
entry, and once the number of added files is above that limit, we only show the parent folders, and not every added files.