From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: kai.grossjohann@gmx.net (=?iso-8859-1?q?Kai_Gro=DFjohann?=) Newsgroups: gmane.emacs.devel Subject: Re: Any idea about what makes Emacs slow reading on pipes? Date: Sun, 18 May 2003 17:50:51 +0200 Organization: University of Duisburg, Germany Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <847k8oqmn8.fsf@lucy.is.informatik.uni-duisburg.de> References: <5x1xyye3y4.fsf@kfs2.cua.dk> <5xznllw0wp.fsf@kfs2.cua.dk> <84of20skuq.fsf@lucy.is.informatik.uni-duisburg.de> <84smrc47ga.fsf@lucy.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1053273169 15855 80.91.224.249 (18 May 2003 15:52:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 18 May 2003 15:52:49 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun May 18 17:52:47 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19HQSt-00047Z-00 for ; Sun, 18 May 2003 17:52:47 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19HQcG-0001EZ-00 for ; Sun, 18 May 2003 18:02:28 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19HQTu-000610-03 for emacs-devel@quimby.gnus.org; Sun, 18 May 2003 11:53:50 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 19HQTa-0005zd-00 for emacs-devel@gnu.org; Sun, 18 May 2003 11:53:30 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 19HQSr-0005GD-00 for emacs-devel@gnu.org; Sun, 18 May 2003 11:52:46 -0400 Original-Received: from main.gmane.org ([80.91.224.249]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19HQRB-0004z1-00 for emacs-devel@gnu.org; Sun, 18 May 2003 11:51:02 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19HQPQ-0003ya-00 for ; Sun, 18 May 2003 17:49:12 +0200 Mail-Followup-To: emacs-devel@gnu.org X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19HQPQ-0003yR-00 for ; Sun, 18 May 2003 17:49:12 +0200 Original-Lines: 36 Original-X-Complaints-To: usenet@main.gmane.org Mail-Copies-To: never User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:4gDAXVqWlVYDDO0rzfDj2R4EprY= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:13974 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:13974 David.Kastrup@t-online.de (David Kastrup) writes: > Interestingly enough, I can't reliably reproduce this effect either. > Hilarious. Maybe it has something to do with what xterms I started as > background processes (different nicety?). Oh, if I have a block > cursor blinking in yet another window, this seems to help. Crazy. I tried "emacs -q -no-site-file" for the blinking cursor. No dice. Here's what I did: I start the dd thing, then click on the Emacs to give it focus. The output from dd shortly (for a second or so) slows down, then resumes again at the previous speed (before Emacs was started). I then start the while look which doesn't change the speed, either. I again click on the Emacs window to resume the blinking cursor, which causes a short pause in the dd output, as before. >> I'm running Linux 2.4.20 on a 2GHz Celeron. I think that means I >> don't have Hyperthreading and therefore just one CPU. > > Perhaps your CPU is to fast. Could be. >> I've now looked again on another machine (2GHz Mobile Pentium 4, same >> kernel), and I can see the leading digits couting, and they count at >> the same speed regardless of the while loop. > > Well, having just half the computing power available at least should > not leave you with the same speed, should it? So maybe neither the dd nor the infloop require 100% CPU. Maybe the terminal (KDE program "konsole") is too slow in printing all this stuff? -- This line is not blank.