[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: slow startup of tramp
From: |
Kai Grossjohann |
Subject: |
Re: slow startup of tramp |
Date: |
Sat, 25 Sep 2004 19:08:48 +0200 |
User-agent: |
Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) |
Julien Oster <usenet-20040924@usenet.frodoid.org> writes:
> So why does tramp take such a long time to start up remote
> connections?
Daniel's remarks are right on target. If you set tramp-verbose to 10,
you will see the shell commands sent, and once you recognize their
number, you will know why it takes long...
Daniel has made some of that code a lot faster by sending a chunk of
shell code that does a lot of detecting, then prints the result. I
think that approach can be taken further by grouping more commands
into a single shell command that can be sent to the remote end.
Another approach that people talk about is to cache the results of the
detecting, and to reuse them on the next connection.
But all of this requires hacking the code. I'm happy about all
contributions.
Kai