On Tue, Jul 9, 2013 at 3:44 PM, Stefan Sperling <s...@elego.de> wrote:
> Michael, does this only happen with ra_serf? Can you please test > with svn://, or svn+ssh://, or file:// access? > Here are the results with 32-bit 1.8.0 using svn+ssh: LANG=$l1 time svn co svn+ssh://... -r244060 C8-32-$l1-svnssh 17.71user 11.13system 1:05.59elapsed 43%CPU (0avgtext+0avgdata 325792maxresident)k 4920inputs+1764088outputs (29major+51815minor)pagefaults 0swaps LANG=$l2 time svn co svn+ssh://... -r244060 C8-32-$l2-svnssh (core dump) 11.71user 10.44system 1:13.20elapsed 30%CPU (0avgtext+0avgdata 3554080maxresident)k 1784inputs+3064200outputs (13major+223537minor)pagefaults 0swaps Note: instead of the error message I got a core dump. That happened before, too. The check-out went about as far as in the other failing cases. So the problem appears to be somewhat independent of the access method. To test file:// access, I need to get the repository to a different machine first. This may take a bit... - Michael
