On 7/19/07, Lutz.Dornbusch@fiducia.de <Lutz.Dornbusch@fiducia.de> wrote:
> "Erik Huelsmann" <ehuels@gmail.com> schrieb am 19.07.2007 14:42:43:
>
> > On 7/19/07, Lutz.Dornbusch@fiducia.de <Lutz.Dornbusch@fiducia.de> wrote:
> > > Hello
> > > I just made a large(1200 Files in 600 MB) commit on a solaris 10 4 CPU
> > > machine running svn, version 1.4.3 (r23084), apache, OpenSSL
> > > The commit runs through, I can see the new revision on repo-browser,
> but
> > > the svn commando is running and running and tooks a whole CPU
> > > at 100% . Server and client are on the same machine(in this case).
> There
> > > is nothing else I can see what this thread is doing..
> > >
> > > PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND
> > > 26175 XXXXX 1 0 0 125M 121M cpu/2 54:30 25.00% svn
> > >
> > > This is second time I am encountering this problem..
> > >
> > > What causes this?
> > > What can I do to avoid this?
> > > Can I safely kill this process?
> > >
> > > Greetings,
> > > Lutz
> >
> > Can you attach strace to see if it's actually doing anything?
> >
> > bye,
> >
> > Erik.
> Hello Erik,
> thanx for the fast reply.
> Unfortunately it was a false alarm:
> After 2.5 Hrs the commit returns to commandline, so I think it did
> something useful.
> Maybe the update and copying of all data to .svn folders took so long?
That, and if you committed over file://, that time was also used to
deltify the data and update the repository.
Bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 19 15:13:26 2007