From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: What's the problem? Date: 10 Dec 2003 13:35:14 +0900 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20031117040607.C6C5D79B72@server2.messagingengine.com> <87ekvpx18d.fsf@emptyhost.emptydomain.de> <4nad6cikxy.fsf@holmes.bwh.harvard.edu> <4nllpt3hr3.fsf@lockgroove.bwh.harvard.edu> <5bad69zd43.fsf@lister.roxen.com> <4noeuon378.fsf@lockgroove.bwh.harvard.edu> <4ny8tsgxy6.fsf@lockgroove.bwh.harvard.edu> <4nhe0ggv0u.fsf@lockgroove.bwh.harvard.edu> <4nk75bwjaf.fsf@lockgroove.bwh.harvard.edu> <4nsmjv8d32.fsf@collins.bwh.harvard.edu> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1071031066 25083 80.91.224.253 (10 Dec 2003 04:37:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 10 Dec 2003 04:37:46 +0000 (UTC) Cc: Juri Linkov , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Dec 10 05:37:37 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 1ATw6T-0004cc-00 for ; Wed, 10 Dec 2003 05:37:37 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ATw6S-0007yQ-00 for ; Wed, 10 Dec 2003 05:37:37 +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 1ATx2y-0002co-06 for emacs-devel@quimby.gnus.org; Wed, 10 Dec 2003 00:38:04 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1ATx2X-0002Ma-WD for emacs-devel@gnu.org; Wed, 10 Dec 2003 00:37:38 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1ATx1v-0001Xj-PV for emacs-devel@gnu.org; Wed, 10 Dec 2003 00:37:30 -0500 Original-Received: from [210.143.35.52] (helo=TYO202.gate.nec.co.jp) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ATx1s-0001Qm-Ge; Wed, 10 Dec 2003 00:36:56 -0500 Original-Received: from mailgate3.nec.co.jp ([10.7.69.162]) by TYO202.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id hBA4ZPM19263; Wed, 10 Dec 2003 13:35:25 +0900 (JST) Original-Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id hBA4ZPl02276; Wed, 10 Dec 2003 13:35:25 +0900 (JST) Original-Received: from edtmg04.lsi.nec.co.jp ([10.26.17.201]) by mailsv.nec.co.jp (8.11.7/3.7W-MAILSV-NEC) with ESMTP id hBA4ZOF26344; Wed, 10 Dec 2003 13:35:24 +0900 (JST) Original-Received: from mcsss2.ucom.lsi.nec.co.jp (localhost [127.0.0.1]) by edtmg04.lsi.nec.co.jp (8.9.3p2+3.2W/3.7W_EDC_Ver.1.0) with ESMTP id NAA13322; Wed, 10 Dec 2003 13:35:24 +0900 (JST) Original-Received: from localhost (mcspd15 [10.30.114.174]) by mcsss2.ucom.lsi.nec.co.jp (8.12.10/8.12.8/EDcg v2.01-mc/1046780839) with ESMTP id hBA4ZF7Q028674; Wed, 10 Dec 2003 13:35:19 +0900 (JST) Original-Received: by localhost (Postfix, from userid 31295) id B7CC110092; Wed, 10 Dec 2003 13:35:14 +0900 (JST) Original-To: Simon Josefsson System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: Original-Lines: 27 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:18603 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18603 Simon Josefsson writes: > If you profile Gnus with ELP, you see that the amount of time spent > waiting for external processes like movemail is not the biggest cause > of the lockups. Most of it is spent evaluating elisp. Even when > getting new mail. It depends on your environment of course -- if you have a slow network connection (or a slow server), it can spend a _lot_ of time waiting for external processes/data. Personally I think making emacs generally multi-threaded is far more trouble than it's worth, but in some cases like gnus, it would be worth it to rewrite (small parts of) _that application_ to execute in the background. In my daily usage the main two places where I end up waiting many minutes for emacs to finish something are (1) fetching my daily mail into gnus via pop3.el, and (2) entering a newsgroup with many unread messages on my home machine, which has a slow modem connection; in both of these cases, the great majority of time is spent waiting for data over the network. Anyway my main point is that I think it's basically an application issue, though emacs might help by adding helper functions. -Miles -- Love is a snowmobile racing across the tundra. Suddenly it flips over, pinning you underneath. At night the ice weasels come. --Nietzsche