RE: Timeout!!!??!

I'm sorry for suggesting things when I cannot give any helping hand in
implementing my own suggestions, but...

- You can begin by adding some logging-statements to the server, and
verifying that your timeout does indeed occur in step 3

- If it does, the code that does step 3 can be profiled to see what it does
that takes so long

- If it's a structural thing that can't be reasonably optimized away, then
some sort of redesign might be considered.
If optimizations are reasonable (and will not just make the problem
invisible for the time being) then optimizations can be implemented.

--Tim

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: donderdag 19 juni 2003 22:40
To: David@workplace-systems.plc.uk
Cc: dev@subversion.tigris.org
Subject: Re: Timeout!!!??!

David@workplace-systems.plc.uk writes:

> c:\dev>svn st -q -u
> svn: RA layer request failed
> svn: REPORT request failed on '/repos'
> svn: REPORT of '/repos': timed out waiting for server
> (https://dev.server.net)
>
> Is this an httpd.conf thing? Can anyone help?

Hmmm.... do you have a really huge, really-mixed-revision working
copy?

As I understand things, here's what happens:

  1. client creates a wc-report in in a tmpfile
  2. tmpfile sent as the body of a REPORT request
  3. mod_dav_svn parses report, builds an fs txn
  4. svn_repos_dir_delta() compares txn with head revision, streaming
     the response back to the client.

So AFAICT, the only potential for neon timeout is in step 3.
I'm not sure what we can do about that.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 19 22:56:53 2003