Projects - Optimizing Arch

This page provides a list of resources where more about Arch-related topics may be explored.

[ Top: Arch Tutorial ]
[ Previous is Part 4: Arch Resources ]
[ This is Part 5: Optimizing Arch ]

Computing changes quickly

If you use Arch in a branch that has many commits, you might notice that it takes a while to compute changes that you have made when you run tla changes. The best solution to this problem is to use a revision library.

The following example shows how to set one up. You can use any path you like to store the library instead of ~/arch-revlib. This makes the library automatically store any new revisions, but not use too much disk space. If you are not worried about disk space, remove the --sparse argument from the third line.

mkdir ~/arch-revlib
tla my-revision-library ~/arch-revlib
tla library-config --greedy --sparse ~/arch-revlib
# For each archive you use frequently and its branches
tla library-add <archive>/<branch>--patch-<latest>

Downloading updates quickly

If you have commit access to an Arch archive, you can make life easier for new users of your archive by creating cached revisions. It is good practice to do this after every 30-50 commits.

The following example shows how to do this. Replace the given Arch branch with the one that you use. If you are currently in a directory that contains a checkout of your branch, you may call tla cacherev without any arguments to accomplish this.

tla cacherev my@archive.org--2006/my-project--main--0

If you have a mirror for this branch, you will have to call tla cacherev a second time, as follows.

tla cacherev my@archive.org--2006-MIRROR/my-project--main--0

[ Previous is Part 4: Arch Resources ]
[ This is Part 5: Optimizing Arch ]

Arch Tutorial

---

[ Front | Projects | Index | Source ] Last updated Oct. 28, 2006