Bazaar

Problems managing big repositories with too many revisions

Asked by Miguel Delgado

Regards,

We currently have a server and a repository on it, to connect different developers in different countries via sftp. Our repository contains many directories and development areas, which are mostly separate and independent. Besides, we've already put about 9,500 revisions on it.

I wonder if it is possible to resolve a couple of issues:

1) Is it possible to easily create repositories to lower levels, without altering the main one? There are several developers working concurrently, and we need to update the entire repository each time we commit. Sometimes one of the developers is commiting into an area that is entirely separate from other that's just been modified. Is there a good solution? I know I can create some new repositories on lower levels, but it means to manage a lot of them.

2) We've got 9500 revisions, and maybe the first 6000 are not really useful for us. Can we eliminate them and stay with the latest? (and how?) We've realised that commiting a single file (20KB) means sometimes to upload about 2MB/3MB of data to the server, and it's highly inefficient!

Thanks in advance!

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Solved by:
Martin Pool
Solved:
Last query:
Last reply:
Revision history for this message
Best Martin Pool (mbp) said : 		#1

Hi Miguel,

First of all, if you have a large repository and a lot of users, I would really recommend you look into using bzr+ssh rather than sftp. It will be able to do more work on the server and it will be substantially faster.

> 1) Is it possible to easily create repositories to lower levels, without altering the main one?

I'm not quite sure what you mean. Do you mean you want to put some of the branches into separate repositories?

> 2) We've got 9500 revisions, and maybe the first 6000 are not really useful for us.

Have a look at bzr-rewrite <http://wiki.bazaar.canonical.com/Rewrite>

> We've realised that commiting a single file (20KB) means sometimes to upload about 2MB/3MB of data to the server, and it's highly inefficient!

This will be much better if you use bzr+ssh.

Revision history for this message
Miguel Delgado (mdelgado-bodaclick) said : 		#2

Hi Martin,

It really goes faster with bzr+ssh and it fixes my main problems quickly. Thanks for your answer! Thanks for your advice with bzr-rewrite too.

Sorry for my English, maybe I didn't explain properly: I've got just one repository (quite big) and many areas of this unique repository are almost separate. I was asking for an easy way to separate jobs between developers: it has no sense that a developer must update another job from another area to commit his own job in his own area. Our problem now is that all areas are under the same repository.

Thanks again for all.

Revision history for this message
Miguel Delgado (mdelgado-bodaclick) said : 		#3

Thanks Martin Pool, that solved my question.