Ben Collins-Sussman <sussman@collab.net> wrote on 02/18/2005 08:50:16 AM:
>
> On Feb 18, 2005, at 7:21 AM, Marton Fabo wrote:
> >
> > I tried the FSFS backend however, and it actually solved the problem.
> > Now a typical commit executed on the whole file set takes around 10
> > minutes (this is about the time needed to simlply walk the whole tree
> > and check for svn status), regardless of whether a few text files
> > changed or a few thousand binary files. This is definitively bearable.
> >
>
> 10 minutes to commit just a few text files? It should take just a few
> seconds. There is still something horribly wrong with your setup... or
> network... or something. Very mysterious.
Ben,
Isn't he saying that he is at the top of a very large WC and running the
command:
svn ci -m ""
Where the command:
svn st
From the same location would take 10 minutes. If svn st would take that
long, then wouldn't it make sense for commit to take roughly the same
amount of time (assuming the actual commit was small)?
By the way, if svn st takes 10 minutes, I wonder if he has the problem
where his file timestamps do not match the timestamps in the pristine
area? There was a recent problem fixed on trunk where if you had the
setting of "Use Commit Times" turned on, then this would be the case for
every file.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 18 15:07:58 2005