Ben Collins-Sussman wrote:
> Vladimir Prus <ghost@cs.msu.su> writes:
> > I've looked at ethereal log for the case of localhost. Unless I've missed
> > some packets the situation is: client and server talk for a couple of
> > seconds, then wait for a long time, and then server closes connection.
> > What can be the problem?
> [snip]
> In the ra_local case, all conversation is happening in memory: the
> initial report and response, as well as file fetching. Berkeley DB is
> being used directly by the client to suck files from the repository
> into the temporary area.
>
> In the ra_dav case, we're talking about multiple network turnarounds.
> *Two* http GETs for each file that has changed.
>
> In your comparison, you're testing file:/// vs. http://localhost. I
> would still expect the http version to be slower, although maybe
> you're right -- maybe it's too slow. Do you have reason to believe
> that apache is 'hanging' or something? Do you see the GET requests in
> ethereal? Where does the 'delay' happen?
Okay, I've looked thought the log more carefully. This is what I see.
(The log is at
http://zigzag.cs.msu.su:7813/~ghost/svn_diff.cap
http://zigzag.cs.msu.su:7813/~ghost/svn_diff.txt
in case you'd like to look at it
)
REPORT request is at 1.816335
response comes at 3.018566
Then, almost instantly client does PROPFIND for /whale/trunk/src/codegen.cpp
(the only changed file).
Then, I see GET at 3.062126 (for revision 42)
Server starts responding at 3.516448
Then, there's another GET at 3.517878 (for revision 43)
After that I'm at loss -- I see some "FIN" packets and finally, at
20.074125 the server returns revision 43.
So, getting the second revision takes a lot of time, and there's nothing
special about that revision.
- Volodya
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 24 15:24:13 2002