From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: Emacs using too much CPU Date: Tue, 18 May 2004 17:43:41 GMT Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084902605 8696 80.91.224.253 (18 May 2004 17:50:05 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 18 May 2004 17:50:05 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue May 18 19:50:01 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BQ8j3-0000vX-00 for ; Tue, 18 May 2004 19:50:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BQ8ft-0001ra-HS for geh-help-gnu-emacs@m.gmane.org; Tue, 18 May 2004 13:46:45 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!cyclone.bc.net!snoopy.risq.qc.ca!charlie.risq.qc.ca!53ab2750!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 10 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Original-NNTP-Posting-Host: 132.204.24.84 Original-X-Complaints-To: abuse@umontreal.ca Original-X-Trace: charlie.risq.qc.ca 1084902221 132.204.24.84 (Tue, 18 May 2004 13:43:41 EDT) Original-NNTP-Posting-Date: Tue, 18 May 2004 13:43:41 EDT Original-Xref: shelby.stanford.edu gnu.emacs.help:123267 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:18562 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:18562 > I found that the auto-save-timeout was at 30 seconds. So CPU usage was > going up every 30 seconds. Hopefully that takes care of most problems. auto-save shouldn't use much CPU if any (it's run rarely for one, and even when it's run it should be quick, and even if it takes a non-negligible amount of time (say for a very large buffer, most of that time is spent waiting for the disk rather than using the CPU). Stefan