From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/9252 Path: main.gmane.org!not-for-mail From: Jason L Tibbitts III Newsgroups: gmane.emacs.gnus.general Subject: Idea for turbo expiry Date: 24 Dec 1996 11:22:59 -0600 Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035149304 17320 80.91.224.250 (20 Oct 2002 21:28:24 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:28:24 +0000 (UTC) Return-Path: Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.8.4/8.8.4) with SMTP id JAA30113 for ; Tue, 24 Dec 1996 09:41:46 -0800 Original-Received: from sina.hpc.uh.edu (tibbs@Sina.HPC.UH.EDU [129.7.3.5]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Tue, 24 Dec 1996 18:22:58 +0100 Original-Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id LAA08998; Tue, 24 Dec 1996 11:23:03 -0600 (CST) Original-To: ding@ifi.uio.no Original-Lines: 17 X-Mailer: Red Gnus v0.76/Emacs 19.34 Xref: main.gmane.org gmane.emacs.gnus.general:9252 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:9252 I dipped into the expiry code to see why it was taking so much CPU every time I exited an nnml group. It looks to me like it builds a list of all expirable articles and stats each of them in turn to see if they're old enough. My idea is to make the assumption that articles come in chronologically, so that if an article has a lower number, it it older. Thus you can run the list of articles in numerical order and bail after you find one that is too young to expire. I figure (judging from how much mail I save in some of my active folders) that this would cut my expiry time by a factor of 100 or more. Yes, it's easy to fool. Just touch (or edit) a random article and watch it hold up expiry of everything after it. I'm willing to make that sacrifice, at least for some groups. - J<