Re: Why would mutt be slow changing mbox when run over ssh?
On Tue, Dec 31, 2019 at 01:12:12PM +, Chris Green wrote: For some reason changing from one mbox to another is slow when I do this, the ssh connection is fast, nothing else slows down and moving around within the mbox is snappy enough, it's just closing one mbox and opening the next that's slow. The usual suspect would be $sleep_time. I can't imagine why it would differ in this case, but still try running :set ?sleep_time in the ssh and local xterm mutt and see if they differ. Next, I would check if $ts_enabled is set in one or the other. This would affect status updates, not just mailbox changes, so it's doubtful this is it. Last, take a good look at all your folder-hooks. See if there is anything crazy hidden in them, like pushing a command that does something which times out over ssh. Again, I can't imagine this is it either, but it's worth checking. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
Re: Why would mutt be slow changing mbox when run over ssh?
El día martes, diciembre 31, 2019 a las 01:12:12p. m. +, Chris Green escribió: > I run mutt via an ssh connection, i.e. I connect from a terminal > window in my laptop (running xubuntu 19.04) to my desktop machine > (running xubuntu 19.10) using ssh and then run mutt. > > For some reason changing from one mbox to another is slow when I do > this, the ssh connection is fast, nothing else slows down and moving > around within the mbox is snappy enough, it's just closing one mbox > and opening the next that's slow. Doing exactly the same thing > directly in a terminal window on my desktop machine doesn't show the > same slowness. By 'slow' I mean a noticeable delay, probably of the > order of a second or two. I do the same often too and see no delay compared a local change or one in a SSH session. I'd run the remote mutt as: strace -o tr -tt mutt and check the file 'tr' (which will have time stamps) for the reason. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
Re: Why would mutt be slow changing mbox when run over ssh?
* Patrick Shanahan [12-31-19 08:47]: > * Chris Green [12-31-19 08:42]: > > I run mutt via an ssh connection, i.e. I connect from a terminal > > window in my laptop (running xubuntu 19.04) to my desktop machine > > (running xubuntu 19.10) using ssh and then run mutt. > > > > For some reason changing from one mbox to another is slow when I do > > this, the ssh connection is fast, nothing else slows down and moving > > around within the mbox is snappy enough, it's just closing one mbox > > and opening the next that's slow. Doing exactly the same thing > > directly in a terminal window on my desktop machine doesn't show the > > same slowness. By 'slow' I mean a noticeable delay, probably of the > > order of a second or two. > > open wireshark and watch your ssh connection. maybe you will get some > clues. fwiw: I never access mutt directly, but run it on my server inside a tmux (similar to screen) session and cannot remember ever experiencing what you describe. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
Re: Why would mutt be slow changing mbox when run over ssh?
* Chris Green [12-31-19 08:42]: > I run mutt via an ssh connection, i.e. I connect from a terminal > window in my laptop (running xubuntu 19.04) to my desktop machine > (running xubuntu 19.10) using ssh and then run mutt. > > For some reason changing from one mbox to another is slow when I do > this, the ssh connection is fast, nothing else slows down and moving > around within the mbox is snappy enough, it's just closing one mbox > and opening the next that's slow. Doing exactly the same thing > directly in a terminal window on my desktop machine doesn't show the > same slowness. By 'slow' I mean a noticeable delay, probably of the > order of a second or two. open wireshark and watch your ssh connection. maybe you will get some clues. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
