From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: MacOS X: Carbon Emacs problem Date: 01 Dec 2003 02:16:14 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1070241452 20342 80.91.224.253 (1 Dec 2003 01:17:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 1 Dec 2003 01:17:32 +0000 (UTC) Cc: =?iso-8859-1?q?Rolf_Marvin_B=F8e_Lindgren?= , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Dec 01 02:17:29 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AQcgr-0006F0-00 for ; Mon, 01 Dec 2003 02:17:29 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AQcgq-00064E-00 for ; Mon, 01 Dec 2003 02:17:28 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AQddy-0001br-0n for emacs-devel@quimby.gnus.org; Sun, 30 Nov 2003 21:18:34 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AQddr-0001bj-K4 for emacs-devel@gnu.org; Sun, 30 Nov 2003 21:18:27 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AQddL-0001Q6-8B for emacs-devel@gnu.org; Sun, 30 Nov 2003 21:18:26 -0500 Original-Received: from [62.226.11.190] (helo=localhost.localdomain) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1AQddJ-0001Pw-06 for emacs-devel@gnu.org; Sun, 30 Nov 2003 21:17:53 -0500 Original-Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id hB11GKe8030356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Dec 2003 02:16:21 +0100 Original-Received: (from dak@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id hB11GFCI030352; Mon, 1 Dec 2003 02:16:15 +0100 Original-To: Martin Fredriksson In-Reply-To: Original-Lines: 67 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18235 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18235 Martin Fredriksson writes: > On 6 nov 2003, at 22.06, Rolf Marvin B=F8e Lindgren wrote: >=20 > > If I call LaTeX from GNU Emacs under Carbon (i.e. the usual way), > > then processing takes ages. if I run Emacs without Carbon, > > i.e. emacs -nw, then LaTeX processing runs at the same speed as > > when called from the shell. > > > > latest cvs build of GNU Emacs (this has been this way for a long > > time now), latest version of auc-tex. >=20 > I experience the same. I think the reason may be that it takes > longer to log the result in the latex output buffer on Emacs/Carbon? Let me guess. You are working on a single processor system. The reason for this may well be something which I already brought up here once which will on _many_ single processor operating systems result in _very_ inefficient operation: when Emacs is listening on a pipe, it will wake up and process a single byte willingly. But while Emacs is processing this single byte (and Emacs usually is rated an interactive application by the scheduler and thus does not get preempted), the application producing the byte does not get any CPU time. So when Emacs has finished processing that single byte and gives back the CPU to the scheduler, the output generating program will again just generate a single byte (or sometimes line) before Emacs gets control of the CPU again. But it is maximally inefficient to have a pipe only be processed with such small units. Try some of the following remedies: M-x customize-variable TeX-command-list RET And then append to the TeXing command you usually use |dd obs=3D8k which should fill the pipe with much larger chunks. Another possibility is to do (defadvice TeX-command-filter (before TeX-pipe-fill) (when (< (length string) 80) (sleep-for 0.05))) This will, in case the filter function receives only a short string, actively yield the CPU for a moment in which the pipe can fill some more. Please report whether this increases throughput on your machine. I am still of the opinion that this problem is so common among operating systems (I have the same problem on Linux) that we should teach Emacs to voluntary yield a bit of CPU when it finds itself processing almost empty pipes all the time. In general, the current behavior makes almost all comint modes awfully slow. I think one should try to read a full pipe's worth of data with small timeout usually. If the pipe does not get full, then we will have had the CPU idle a bit unnecessarily, but that means that the output generating application actually leaves us enough time so that we can afford it. The disadvantage is that if we are talking some protocol with an interactive daemon process, we will always take at least a tick of time to respond. But maybe one can set a flag when sending to some process that will take this sort of CPU throttling off the process for the next received data. --=20 David Kastrup, Kriemhildstr. 15, 44793 Bochum