Merge lp:~jelmer/launchpad/reduce-svn-revision-limit into lp:launchpad

Proposed by Jelmer Vernooij
Status: Merged
Approved by: Graham Binns
Approved revision: no longer in the source branch.
Merged at revision: 14410
Proposed branch: lp:~jelmer/launchpad/reduce-svn-revision-limit
Merge into: lp:launchpad
Diff against target: 12 lines (+1/-1)
1 file modified
lib/canonical/config/schema-lazr.conf (+1/-1)
To merge this branch: bzr merge lp:~jelmer/launchpad/reduce-svn-revision-limit
Reviewer Review Type Date Requested Status
Graham Binns (community) code Approve
Review via email: mp+83697@code.launchpad.net

Commit message

Reduce the import size of SVN code imports to 500 revisions.

Description of the change

Reduce the batch size of SVN code imports to 500 revisions.

Whenever importing a single revision that is part of a code import batch fails, the entire batch is cancelled and discarded. Some hosting sites have unreliable SVN servers that cause occasional connection resets. The larger the batch size, the likelier it is to be interrupted by one of these connection resets.

Reducing the batch size from 5000 to 500 should reduce the impact of these connection resets when they occur.

There is some overhead to each batch (fetching the import base branch, and pushing the branch back after the import), so decreasing the batch size means that large branches will slightly some more time. That should be insignificant compared to the overall run time though.

There is more that we can do to improve this situation - such as preserving the revisions that have already been imported when the server hangs up - but I'll leave that for another MP.

To post a comment you must log in.
Revision history for this message
Graham Binns (gmb) wrote :

Hi Jelmer,

Is this something we can test, or is that just wild optimism on my part?

review: Needs Information
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Am 29/11/11 11:53, schrieb Graham Binns:
> Review: Needs Information
>
> Hi Jelmer,
>
> Is this something we can test, or is that just wild optimism on my part?
It's tweaking of the parameters based on the real-life erratic behaviour
of SourceForge. I don't think there's much we can test here, unless we
want to add a handful of svn import runs against the actual SourceForge
server to the testsuite. ;-)

Cheers,

Jelmer

Revision history for this message
Graham Binns (gmb) wrote :

Hmm. Well, as tempting as that is, I think we can live without :).

review: Approve (code)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'lib/canonical/config/schema-lazr.conf'
2--- lib/canonical/config/schema-lazr.conf 2011-11-28 08:30:05 +0000
3+++ lib/canonical/config/schema-lazr.conf 2011-11-28 21:50:24 +0000
4@@ -496,7 +496,7 @@
5 git_revisions_import_limit: 30000
6
7 # Import only this many revisions from svn (via bzr-svn) at once.
8-svn_revisions_import_limit: 5000
9+svn_revisions_import_limit: 500
10
11 # Import only this many revisions from hg at once.
12 hg_revisions_import_limit: 5000