W32 to AIX performance

I'm currently using GNU Emacs 22.0.50.1
(i386-mingw-nt5.1.2600) of 2006-05-02 
on XP.  

I use an up-to-date cygwin ssh to connect to both Solaris
and AIX machines 
without problems using RSA keys.  Under the DOS console and
cygwin's RXVT it 
works as expected.

Starting an `M-x shell' and then invoking ssh within the
comint buffer to a 
Solaris machine works great.  Tramp using the sshx method to
the Solaris box 
works as well.

Doing the same with the AIX box however is problematic. 
Under comint, the 
response is so slow that it is unusable.  For example, more
than a minute to 
`ls' an empty directory and get the next prompt.  The
output does not come 
slowly, but rather all appears at the end of a long wait. 
Tramp using sshx is 
unusable because it times out.  In fact, under Emacs, any
interaction with the 
AIX box exhibits this behavior.  

I would assume that I had done something wrong, except that
the same config 
interacts with Solaris seamlessly.  Google and the list
archives yielded 
little.  Has anyone else experienced this?  Are there
settings on either the 
AIX or W32 side that I can change to impact this?  I'm
willing to debug this 
some but need some hints as to what to do and look for.  

This is becoming important to me since much of my
development for the next six 
months will be on AIX rather than Solaris and vi aint
cuttin' it!  

TIA



_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

Michael Mauger <mmaugyahoo.com> writes:

> I'm currently using GNU Emacs 22.0.50.1
(i386-mingw-nt5.1.2600) of 2006-05-02 
> on XP.  
>
> I use an up-to-date cygwin ssh to connect to both
Solaris and AIX machines 
> without problems using RSA keys.  Under the DOS console
and cygwin's RXVT it 
> works as expected.
>
> Starting an `M-x shell' and then invoking ssh within
the comint buffer to a 
> Solaris machine works great.  Tramp using the sshx
method to the Solaris box 
> works as well.
>
> Doing the same with the AIX box however is problematic.
 Under comint, the 
> response is so slow that it is unusable.  For example,
more than a minute to 
> `ls' an empty directory and get the next prompt.  The
output does not come 
> slowly, but rather all appears at the end of a long
wait.  

Does setting process-adaptive-read-buffering to nil help?

>                                                        
   Tramp using sshx is 
> unusable because it times out.  In fact, under Emacs,
any interaction with the 
> AIX box exhibits this behavior.  

Is Emacs non-responsive when this happens, or using a lot of
CPU?

Can you use a debugger to see what emacs is doing when it is
waiting for
output from the AIX box?

You may have to interrupt the execution several times and
make a backtrace
to see if there is a specific point where emacs is stuck.

-- 
Kim F. Storm <stormcua.dk> http://www.cua.dk



_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel

--- "Kim F. Storm" wrote:

> Michael Mauger writes:
> 
> > I'm currently using GNU Emacs 22.0.50.1
(i386-mingw-nt5.1.2600) of 2006-05-02 
> > on XP.  
> >
> > I use an up-to-date cygwin ssh to connect to both
Solaris and AIX machines 
> > without problems using RSA keys.  Under the DOS
console and cygwin's RXVT it 
> > works as expected.
> >
> > Starting an `M-x shell' and then invoking ssh
within the comint buffer to a 
> > Solaris machine works great.  Tramp using the sshx
method to the Solaris box 
> > works as well.
> >
> > Doing the same with the AIX box however is
problematic.  Under comint, the 
> > response is so slow that it is unusable.  For
example, more than a minute to 
> > `ls' an empty directory and get the next prompt. 
The output does not come 
> > slowly, but rather all appears at the end of a
long wait.  
> 
> Does setting process-adaptive-read-buffering to nil
help?
> 

Nope.  Same behavior

> >                                                   
        Tramp using sshx is 
> > unusable because it times out.  In fact, under
Emacs, any interaction with the 
> > AIX box exhibits this behavior.  
> 
> Is Emacs non-responsive when this happens, or using a
lot of CPU?
> 

No, Emacs is still responsive; cursor is blinking, no CPU
usage.

> Can you use a debugger to see what emacs is doing when
it is waiting for
> output from the AIX box?
> 
> You may have to interrupt the execution several times
and make a backtrace
> to see if there is a specific point where emacs is
stuck.
> 

I'm building a debug version now.  I'll report my findings
once I can test.




_______________________________________________
Emacs-devel mailing list
Emacs-develgnu.org
htt
p://lists.gnu.org/mailman/listinfo/emacs-devel