Tobias Ringström wrote:
> Tony Butt wrote:
>
>> We have been running the subversion 1.0.x series with Apache 2.0.48,
>> then Apache 2.0.50 on W2000 SP3 for some months, and have recently
>> encountered a major problem.
>>
>> I recently updated our subversion server to 1.1.0 from 1.1.0 rc3
>> At the same time, I updated my client to TortoiseSVN 1.1.0, from the
>> prior RC.
>>
>> My first sympton was that when using the repo-browser with Tortoise,
>> the performance was poor, and sometimes just failed to return. At the
>> same time, the apache process on the W2K repository server would
>> spin, growing in size to 24M or so, and consuming 100% CPU for an
>> extended period of time.
>
>
> Thanks for the report. This is a know problem that was introduced in
> 1.0.8 and 1.1.0-rc4. There will be a 1.0.9 and a 1.1.1 release this
> week to fix that problem.
>
>> I tried a vendor merge of a source tree from the command line, as I
>> have done several times in the past. It ran very slowly, exhibiting
>> the same apache server problem, and at some point failed(!) I have
>> totally reinstalled apache, updating to 2.0.52 from 2.0.50,
>> reinstalled subversion on the server, and this problem persists. I
>> checked the repository with svnadmin, and everything is Ok.
>
>
> I wonder if this is the same problem. Can you show us exactly what you
> did?
>
> /Tobias
>
Thanks for the quick reply.
The short response is that I followed the Vendor branch merge
instructions in the 'Version Control with Subversion' manual, chapter 7
(Advanced Topics)
More generally, we use an RTOS called ECos, which provides updates via
CVS, so:
* Check out latest ecos code from the ecos CVS server to our
internet gateway.
* Check in the ecos tree to the subversion repository, ecos project
(http://svnserver/repos/CEA/ecos/ecos-2.0/vendor/ecos)
* Copy the current ecos vendor tree to a tag
(http://svnserver/repos/CEA/ecos/ecos-2.0/vendor/ecos-yymmdd)
* Merge in the changes to my working directory:
o svn merge
http://svnserver/repos/CEA/ecos/ecos-2.0/vendor/ecos-040817
http://svnserver/repos/CEA/ecos/ecos-2.0/vendor/ecos ecos-2.0
* Resolve any merge conflicts
* Rebuild ECos, test for a week, or so, then check in to the trunk
branch of the ecos project.
Now, the ECos source tree is ~ 600 MB, and the merge process used to
take 5-10 minutes, using apache/dav_svn on a Windows 200 Server (PIII
800MHz)
Currently, the merge process takes over 30 minutes, and fails to
complete, returning this error message:
svn: REPORT request failed on '/repos/cea/!svn/vcc/default'
svn: REPORT of '/repos/cea/!svn/vcc/default': Could not read
response body: An existing connection was forcibly closed by the remote
host. (http://svnserver)
We have switched to the svn: protocol as a workaround, and the problem
has gone away.
Additionally, it runs MUCH faster than the http: protocol ever did - as
does browsing, (and probably checkouts, etc)
Is this a common experience? We would have expected better performance
from the apache based repository server.
Tony Butt
Received on Wed Oct 13 05:43:01 2004