Strange delays when running remotely

[kevin]

David E. Sigeti <sigeti <at> lanl.gov> writes:

> 
> This bug report will be sent to the XEmacs Development Team,
>  not to your local site managers!!
> Please write in English, because the XEmacs maintainers do not have
> translators to read other languages for them.
> 
> Please describe as succinctly as possible:
> 	- What happened.
> 	- What you thought should have happened.
> 	- Precisely what you were doing at the time.
> 
> Please also include any C or lisp back-traces that you may have.
> ================================================================
> Dear Bug Team!
> 
> When running Xemacs version 21 remotely (displaying on my local X
> server) I have found that any multicharacter kills (such as kill-line,
> kill-word, kill-ring-save, etc.) are extremely slow (maybe 15-30
> seconds per kill).  I only see this delay when I am running over a DSL
> connection where the ping times to the remote system are on the order
> of 100 milliseconds or more.  When my local machine is on the same LAN
> as the remote machine (much shorter ping times), I do not notice any
> unusual delay in multicharacter kills.  I also do not see this problem
> when running Xemacs version 20.
> 
> My local X server when using the DSL connection is Exceed 3D running
> under Microsoft Windows 98SE.  When using the LAN, my local X server
> is also Exceed 3D but running under Microsoft Windows 2000.
> 
> Yours,
> David
> ---
> Dr. David E. Sigeti
> Phone:  505-667-9239
> E-mail: sigeti <at> lanl.gov
> Surface mail: MS-F645, Los Alamos National Laboratory,
>               Los Alamos, NM  87545   USA
> 
> ================================================================

I had the exact same problem when running xemacs on a remote machine.  Painfully
slow kill-line function, yet fast yank... I fixed the problem by changing the
auto-save directories to save to /tmp
(this saves network traffic)
TRY:
;;; Auto-save
;;; Load the auto-save.el package, which lets you put all of your autosave
;;; files in one place, instead of scattering them around the file system.
;;; M-x recover-all-files or M-x recover-file to get them back
(defvar temp-directory (concat "/tmp/" (user-login-name)))
(make-directory temp-directory t)
; One of the main issues for me is that my home directory is
; NFS mounted.  By setting all the autosave directories in /tmp,
; things run much quicker
(setq auto-save-directory (concat temp-directory "/autosave")
      auto-save-hash-directory (concat temp-directory "/autosave-hash")
      auto-save-directory-fallback "/tmp/"
      auto-save-list-file-prefix (concat temp-directory "/autosave-")
      auto-save-hash-p nil
      auto-save-timeout 100
      auto-save-interval 300)
(make-directory auto-save-directory t)
(require 'auto-save)
;;; Put backups in another directory.  With the directory-info
;;; variable, you can control which files get backed up where.
(require 'backup-dir)
(setq bkup-backup-directory-info
      `(
        (t ,(concat temp-directory "/backups") ok-create full-path)
        ))
(setq make-backup-files t)
(setq backup-by-copying t)
(setq backup-by-copying-when-mismatch t)
(setq backup-by-copying-when-linked t)
(setq version-control t)
(setq-default delete-old-versions t)
;; -------------------------------------------------