[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] Re: Tla working slower than cvs, how to speedup?
From: |
Alexander Litvinov |
Subject: |
[Gnu-arch-users] Re: Tla working slower than cvs, how to speedup? |
Date: |
Wed, 9 Mar 2005 10:04:25 +0600 |
User-agent: |
KMail/1.6.2 |
> You could try to upgrade. There have been some performance
> improvements since that.
I have installed 1.3 tla:
> tla -V
tla address@hidden/dists--tla--1.3--version-0
(configs/gnu/This-release) from regexps.com
Tla changes still takes 11 seconds.
> Second thing to do, if not already done: Use a revision library.
I have setuped greedy revision library as Anand Kumria describe. First tla get
operation take huge amount of time (16min), but next tla get takes 32 sec.
This is great news. Tla changes takes 12 sec - this make me think some files
are in disk cache. Will try to run this later when other files will be placed
in it.
By the way. ls -laR takes less than 1 second. It is possible to scan working
tree, scan pristine tree (or revision's library tree) and then filter files
with changes mtime and then comprate content of these files. This should
takes less than 2 seconds in my case. Does tla looking for changed files by
comparing content of files ?
> Another optimization: use "tla get --link". Be warned: This is a
> dangerous optimization. Make sure you've read all the docs before
> using it on important projects.
I have thinking about this, just need to check if our development tools will
hadle hard links properly. After testing I have found this greatly speedup
tla get operation, but tla changes time stay the same.
> And a few things you should know: tla does most of the work on the
> client. If you compare tla and CVS, CVS may beat tla on the client,
> but the server load and the bandwidth consumption are ridiculously
> small in the case of tla.
I have seen this then test remote tla repository via sftp. During tla get all
server have to do is to give 10-20 files to me. This is great because now our
cvs server become slower and slower.
CONCLUSION:
Revision library greatly reduce tla get time, but tla changes time stay the
same. Any way, in real development tla get will be rare operation and it is
acceptable to wait even 1 minute for this. Tla changes almost the same as cvs
update and this is good. Tla commit with version 1.3 takes 15-18 seconds,
this is about 2 times (or 10 sec) slower than cvs. This time is still
acceptable.
- [Gnu-arch-users] Tla working slower than cvs, how to speedup?, Alexander Litvinov, 2005/03/04
- [Gnu-arch-users] Re: Tla working slower than cvs, how to speedup?, Matthieu Moy, 2005/03/05
- [Gnu-arch-users] Re: Tla working slower than cvs, how to speedup?,
Alexander Litvinov <=
- Re: [Gnu-arch-users] Tla working slower than cvs, how to speedup?, Jonathan Geisler, 2005/03/05
- [Gnu-arch-users] Re: Tla working slower than cvs, how to speedup?, Anand Kumria, 2005/03/05