You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Andrew Webber <al...@gmail.com> on 2006/03/22 15:33:23 UTC
Apache cpu usage on large commit
Forgive me if this has already gone around on the mailing list, but I didn't
see anything about it.
I'm trying to perform a very large commit (~4 Gb) into my repository and
it's not working. The commit begins and starts tranferring the data. After
a while, no more dots appear showing me that the transfer is proceeding.
The svn client hangs there indefinitely without spitting out an error. On
the server, I can see an apache process running at around 98% cpu usage. It
looks like there is still some memory free on the server, so I don't think
it's thrashing. There is plenty of hard drive space available both on the
client and the server. Once things get this way I need to kill the client
and restart apache. I didn't see anything useful in my apache access or
error logs. I can see a transaction in the repository using 'svnadmin
lstxns /path/to/repos'. The transaction folder weighs in at 2.1 Gb. Here
are some stats about my server:
RHEL 4.2
Apache 2.0.52-22
Subversion 1.3.0 (built from source)
Repository on ext3 filesystem
Have I reached a commit size limit in apache? ra_dav?
I have sucessfully done commits around 1.5 Gb and I can split the big one up
to get around the problem. Does anyone have any advice on how to fix the
larger problem?
Thanks!
Andy Webber
Re: Apache cpu usage on large commit
Posted by Andrew Webber <al...@gmail.com>.
Wow, thanks for the quick responses.
I figured that it was probably a known problem, but I wanted to make sure.
We don't explicitly *need* commits this big, so I think we'll just wait for
the next release.
Is subversion 1.3.1 (the next release I'm guessing) going to have the
updated Apr 1.2.x?
On 3/22/06, Ryan Schmidt <su...@ryandesign.com> wrote:
>
> On Mar 22, 2006, at 16:33, Andrew Webber wrote:
>
> > Forgive me if this has already gone around on the mailing list, but
> > I didn't see anything about it.
> >
> > I'm trying to perform a very large commit (~4 Gb) into my
> > repository and it's not working. The commit begins and starts
> > tranferring the data. After a while, no more dots appear showing
> > me that the transfer is proceeding. The svn client hangs there
> > indefinitely without spitting out an error. On the server, I can
> > see an apache process running at around 98% cpu usage. It looks
> > like there is still some memory free on the server, so I don't
> > think it's thrashing. There is plenty of hard drive space
> > available both on the client and the server. Once things get this
> > way I need to kill the client and restart apache. I didn't see
> > anything useful in my apache access or error logs. I can see a
> > transaction in the repository using 'svnadmin lstxns /path/to/
> > repos'. The transaction folder weighs in at 2.1 Gb. Here are some
> > stats about my server:
> >
> > RHEL 4.2
> > Apache 2.0.52-22
> > Subversion 1.3.0 (built from source)
> > Repository on ext3 filesystem
> >
> > Have I reached a commit size limit in apache? ra_dav?
>
> You have reached the 2-GB file size limit of APR 0.9.x. APR 1.2.x,
> available with Apache 2.2, does not have this limitation.
>
> There still remains this > 2GB-commit problem on Linux servers with
> FSFS repositories, which will be resolved when the next version of
> APR 1.2.x is released:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=2453
>
>
>
Re: Apache cpu usage on large commit
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Mar 22, 2006, at 16:33, Andrew Webber wrote:
> Forgive me if this has already gone around on the mailing list, but
> I didn't see anything about it.
>
> I'm trying to perform a very large commit (~4 Gb) into my
> repository and it's not working. The commit begins and starts
> tranferring the data. After a while, no more dots appear showing
> me that the transfer is proceeding. The svn client hangs there
> indefinitely without spitting out an error. On the server, I can
> see an apache process running at around 98% cpu usage. It looks
> like there is still some memory free on the server, so I don't
> think it's thrashing. There is plenty of hard drive space
> available both on the client and the server. Once things get this
> way I need to kill the client and restart apache. I didn't see
> anything useful in my apache access or error logs. I can see a
> transaction in the repository using 'svnadmin lstxns /path/to/
> repos'. The transaction folder weighs in at 2.1 Gb. Here are some
> stats about my server:
>
> RHEL 4.2
> Apache 2.0.52-22
> Subversion 1.3.0 (built from source)
> Repository on ext3 filesystem
>
> Have I reached a commit size limit in apache? ra_dav?
You have reached the 2-GB file size limit of APR 0.9.x. APR 1.2.x,
available with Apache 2.2, does not have this limitation.
There still remains this > 2GB-commit problem on Linux servers with
FSFS repositories, which will be resolved when the next version of
APR 1.2.x is released:
http://subversion.tigris.org/issues/show_bug.cgi?id=2453
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org