From xemacs-m  Thu Mar 20 17:33:09 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id RAA23228
	for <xemacs-beta@xemacs.org>; Thu, 20 Mar 1997 17:33:07 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQchte07091; Thu, 20 Mar 1997 18:33:07 -0500 (EST)
Date: Thu, 20 Mar 1997 18:33:07 -0500 (EST)
Message-Id: <QQchte07091.199703202333@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: 20.1b8 slowness (again)
In-Reply-To: <199703202150.NAA20796@sandman>
References: <199703202150.NAA20796@sandman>
X-Mailer: VM 6.20 under 19.15 XEmacs Lucid (beta101)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Dan Rich writes:
 > The slowness that I'm seeing in XEmacs 20.1 just got worse.  I
 > just watched it take over 5 minutes to decode a base64 message
 > in VM (6.20).  Now, I have to admit, it was a fairly large
 > file (~580KB after decoding), but 5 min. is a *long* time to
 > have your emacs process completely hung (and taking 90+% of
 > the CPU).
 > 
 > Here's what I'm seeing in truss.  Does this look reasonable to those of you
 > who know what it should be doing during the decode process?

There should be no related system calls except to sbrk()/brk() or
equivalent for memory, if you're not using an external decoder.
The internal decoder does no I/O.  The system calls are probably
related to window system chatter.

