You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by pjaytycy <pi...@gmail.com> on 2010/12/06 09:27:29 UTC
extreme svn slowdown due to X-forwarding timeouts
Hello,
we recently upgraded svn on our remote build server from 1.5 to 1.6.
This caused a drastic reduction in speed:
user@server:~$ time svn log -l 25 -q https://<repo>
[… snip …]
real 0m22.745s
user 0m0.192s
sys 0m0.048s
After some debugging, we found the cause to be entirely on my windows
pc, not related to the linux server:
=> I log in with putty over SSH and had X-forwarding turned on
=> I did not have an X-server running on my windows pc
The combination of these 2 made command-line svn on the linux server
extremely slow. I think this is due to the gnome/kde keyring
integration which is new in 1.6
So, to solve this: either run xming before starting putty, or turn off
X-forwarding in putty.
Maybe command line client svn could give a warning that it tried to
communicate with an X-server but got no response? That would have
helped us in discovering what caused the performance issue. However,
even when I actually run an X-server, I got no GUI popup, but atleast
SVN was not slow anymore.
Kind regards,
Pieter-Jan
Re: extreme svn slowdown due to X-forwarding timeouts
Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Mon, Dec 6, 2010 at 4:27 AM, pjaytycy <pi...@gmail.com> wrote:
> Hello,
>
>
> we recently upgraded svn on our remote build server from 1.5 to 1.6.
> This caused a drastic reduction in speed:
>
> user@server:~$ time svn log -l 25 -q https://<repo>
> [… snip …]
>
> real 0m22.745s
> user 0m0.192s
> sys 0m0.048s
>
> After some debugging, we found the cause to be entirely on my windows
> pc, not related to the linux server:
>
> => I log in with putty over SSH and had X-forwarding turned on
> => I did not have an X-server running on my windows pc
>
> The combination of these 2 made command-line svn on the linux server
> extremely slow. I think this is due to the gnome/kde keyring
> integration which is new in 1.6
>
> So, to solve this: either run xming before starting putty, or turn off
> X-forwarding in putty.
Or switch to NX, from www.nomachine.com. I'm extremely happy with it
for well-managed X sessions, especially Xterm, optimized for low
bandwidth remote links.