Project

General

Profile

Actions

Patch #7528

open

Fetch small initial set of repository changesets

Added by Andy Bolstridge over 13 years ago. Updated about 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
2011-02-03
Due date:
% Done:

30%

Estimated time:

Description

In my company we have a subversion repository with 315,000 revisions in it. I think this isnot too unusual for a lot of corporate users. Now we love Redmine, but we have a problem when adding a new project as the first thing it does is reads every revision from the repo in chunks of 200, and this takes a very long time.

So, I've made a few changes to Redmine-1.1, this patch only reads the latest 200 revisions (as most people don't care for a project's history from years ago) and stores that. Project creation is now much faster. I've also added a link on the repository page that will fetch the next previous 200 revisions if and when they are required.

This is my first time with redmine, and ruby and rails, so I think the patch needs some peer review, but it's not that complicated given what it does.


Files

fetch_more.patch (6.09 KB) fetch_more.patch Andy Bolstridge, 2011-02-03 12:10
fetch_more.patch (6.25 KB) fetch_more.patch Andy Bolstridge, 2011-02-07 11:40

Related issues

Related to Redmine - Feature #7719: SVN Start RevisionNew2011-02-25

Actions
Related to Redmine - Defect #7699: Subversion: 500 Internal Server Error when browsing a repositoryReopened2011-02-23

Actions
Related to Redmine - Patch #6159: Subversion: latest changesets performance improvement.New2010-08-17

Actions
Actions #1

Updated by Andy Bolstridge over 13 years ago

new patch, updated for RM 1.1.1

Actions #2

Updated by Toshi MARUYAMA over 13 years ago

Git revision is not number. It is string of hash value.

Actions #3

Updated by Toshi MARUYAMA over 13 years ago

  • % Done changed from 100 to 30
Actions #4

Updated by Andy Bolstridge about 9 years ago

Fair enough, but git repos are still read in chunks of 200 - I don't use the rev num, but the number of revisions - ie they are still read from the repo 200 at a time in historical order, this change reads only the first chunk of 200 instead of repeating the process until they are all read, and I moved the code that reads the next chunk into a link so they can be fetched manually if required.

Actions

Also available in: Atom PDF