From owner-freebsd-ports@FreeBSD.ORG  Tue Jul 24 21:00:40 2012
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mandree.no-ip.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 0F6D41065692
	for <freebsd-ports@freebsd.org>; Tue, 24 Jul 2012 21:00:40 +0000 (UTC)
	(envelope-from mandree@FreeBSD.org)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1])
	by apollo.emma.line.org (Postfix) with ESMTP id 1764B23CF2B
	for <freebsd-ports@freebsd.org>; Tue, 24 Jul 2012 23:00:39 +0200 (CEST)
Message-ID: <500F0CF7.4040209@FreeBSD.org>
Date: Tue, 24 Jul 2012 23:00:39 +0200
From: Matthias Andree <mandree@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
References: <20120724171842.GA47545@mech-cluster241.men.bris.ac.uk>
In-Reply-To: <20120724171842.GA47545@mech-cluster241.men.bris.ac.uk>
X-Enigmail-Version: 1.5a1pre
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Subject: Re: mutt 1.5 much slower than mutt 1.4
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 21:00:40 -0000

Am 24.07.2012 19:18, schrieb Anton Shterenlikht:
> mail/mutt is much slower on my amd64 and ia64
> -current boxes after it was updated from 1.4
> to 1.5. Each keystroke takes few seconds to
> act. Below is my mutt 1.5 config:
...

> Anybody else is seeing this behaviour?

Not here™ on amd64 9-stable -- which may have little relevance for
10-current.

> Any advice?

Any chance to figure out what mutt is doing, like with truss or similar?

Is debugging turned on; was mutt built WITH_DEBUG=yes?

Is the lag CPU-bound (near 100% CPU) and if yes, in system or in user
space, or is the lag IO-bound (near 100% wait)?

Can you verify the header cache databases, or move them away just for
the sake of the experiment?

Does it help if you "make clean" before building world?  This has cured
strance effects on occasions in -STABLE (RELENG_[6-9]) branches for me.