Odd behaviour for random files

Jan Olsen janpolsen at gmail.com
Tue May 17 18:19:54 UTC 2011


>
> (replies inline, top-posting is discouraged on this list)
>

Sorry about that :(.

 > Unfortunately we run Mercurial over a cross country network (~30Mbit), so
> our commits takes a "tad" longer :).
> Network speed makes no difference to commits. Commits are local. Unless
> you're running a networked -filesystem- over a cross-country 30Mbit
> network...
> Are you referring to the speed of -pushing- rather than committing?
>

We are talking about commits and not pushes.

We have a server with a network share and the repository is located on that
share as well.
Four developers are located at the other end of that 30Mbit connection and
edits files every now and then. We also have a batch script which on a daily
basis automatically commits changes to specific directories under that
network share (i.e. dump of complete MSSQL database structures). So whenever
one of us have made some changes to a file, then we commit it to the
repository.

We have never pushed or pulled to/from the repository that went bad this
time (and the time before that).

This would indicate to me that you're using a shared working directory on
> some kind of network filesystem. That's probably a bad idea—not because of
> Mercurial, but because of the inherent limitations of network filesystems,
> which DVCSes are designed to avoid.
>

I know it's not encouraged to use Mercurial over network shares, but it is
"unfortunately" the case for us.


> The usual working pattern with Mercurial is for each developer to have
> their own local clone, commit locally, pull changes from each other (or push
> to a central repo), and merge each developer's changes early and often.
>

All our servers (file server, batch servers, MSSQL servers and application
servers) are located in another country of where we are. If we run the
scripts locally from our workstations, then they take about 10 times longer
(because of the 30Mbit line) than if run from the intended batch server.
While it's easy to say, that we should have local clones and commit locally,
then it's unfortunatelly not so easy in our case :(

Best regards,
Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20110517/432939e7/attachment.html>


More information about the Mercurial mailing list