Odd behaviour for random files

[Jan Olsen]

Hi

Unfortunately we run Mercurial over a cross country network (~30Mbit), so
our commits takes a "tad" longer :).

We used to run Mercurial over a 1GB network and that time we never
experienced any odd behaviour. Now on the 30Mbit we have experienced it
twice.

A few days ago when I had to run the "hg update -r 1336" there was a problem
with locked files in the repository, so I had to shut down five other
computers, before it could finish the update. That was cumbersome but not a
problem since it was during the weekend. During weekdays I'm afraid it wont
be possible at all.

Best regards,
Jan

On Mon, May 16, 2011 at 17:07, Matt Mackall <mpm at selenic.com> wrote:

> On Mon, 2011-05-16 at 08:22 +0200, Jan Olsen wrote:
> > Holas
> >
> > I'm back :)
> >
> > After another "big" commit of 6.700-ish files everything still works. I
> had
> > "hoped" for a big one around the 13.000 so it would've been possible to
> see
> > if maybe the amount of files was the reason.
>
> FYI, this isn't big by Mercurial standards. My first test case before
> Mercurial was a day old was 17000 files and 200M. That took about a
> minute on a circa 2003 laptop.
>
> You earlier wrote:
>
> "Unfortunately I'll have to wait with the 13.000 files commit as I do
> not have the time needed to make another "hg update" if it fails again."
>
> If such a commit takes more than a few minutes, something is wrong with
> your system. The usual culprit is on-access virus scanners.
>
> --
> Mathematics is the supreme nostalgia of our time.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20110517/35adfdf2/attachment.html>