Re: cvs update times

[Eric Siegerman]

On Fri, Nov 14, 2003 at 12:27:01PM -0800, Richard Pfeiffer wrote:
> However, we have one project in this repository that now takes
> 1:58 to checkout and 1:29 to update.  It used to update much
> faster; these 'slow' update times just started occuring.

Two stabs in the dark:
  - Are you on a branch, with large files and/or many revisions
    between head of branch and head of trunk?  Many operations in
    CVS take longer under such circumstances, because of the way
    revisions are stored in the ,v file (trunk as reverse deltas
    from the head; branches as forward deltas from the branch
    point.  See rcsfile(5)).

  - Does your slow project have a much larger directory:file
    ratio than your other projects?  If so, it could be that
    locking overhead is dominating the total update time in that
    project, whereas in your other projects it's the useful work
    of updating revisions that dominates.  CVS's locking overhead
    is proportional to the number of directories (not files)
    being operated on.

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
        - Patrick Lenneau