Interesting, so 0.37.0 through mod_dav_svn still timeouts on commit, but
it also consistently seems to cause httpd to become unresponsive, and
saturate the cpu. These problems don't seem to
happen when accessing the repository locally (file:///...). I seem to recall
reading that it was possible to increase the timeout for neon; haven't tried
that yet but that still wouldn't explain the strange behaviour with Apache.
fwiw, I still need to go through and test with BDB 4.2, but there again it
doesn't seem to be a problem with the DB since it worked correctly for
a direct repository access.
Matt
13:32:42 up 15 days, 17:21, 3 users, load average: 1.00, 1.06, 1.35
65 processes: 61 sleeping, 3 running, 0 zombie, 1 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 99.8% 0.0% 0.1% 0.0% 0.0% 0.0% 0.0%
Mem: 514544k av, 386084k used, 128460k free, 0k shrd, 104064k buff
112792k active, 197448k inactive
Swap: 1050760k av, 6432k used, 1044328k free 165768k cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
4951 root 16 0 6876 6876 6756 S 99.7 1.3 20:38 0 httpd
..................................................................................
..................................................................................
..................................................................................
...............svn: Commit failed (details follow):
svn: PUT of /source/gcc/!svn/wrk/e0c1bf70-14d2-0310-8508-b75a67204952/gcc-3.2-ee-030926/src/gcc/testsuite/g++.old-deja/g++.ns/alias2.C: timed out waiting for server (https://anduril)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 30 05:02:16 2004