Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 65C5C6DE1585 for ; Sat, 11 Apr 2015 11:21:13 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.98 X-Spam-Level: X-Spam-Status: No, score=0.98 tagged_above=-999 required=5 tests=[AWL=0.980] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18lIUDALymHz for ; Sat, 11 Apr 2015 11:21:10 -0700 (PDT) X-Greylist: delayed 583 seconds by postgrey-1.35 at arlo; Sat, 11 Apr 2015 11:21:10 PDT Received: from sip.bubblegen.co.uk (bubblegen.plus.com [80.229.236.194]) by arlo.cworth.org (Postfix) with ESMTPS id AEB366DE1583 for ; Sat, 11 Apr 2015 11:21:10 -0700 (PDT) Message-ID: <55296360.1040208@bubblegen.co.uk> Date: Sat, 11 Apr 2015 19:09:36 +0100 From: Matthew Lear MIME-Version: 1.0 To: David Bremner Subject: Re: emacs / vim - time taken to open threads References: <5511DE10.80107@bubblegen.co.uk> <87384u6lgb.fsf@maritornes.cs.unb.ca> <49796ef89d505ab1039478982568a0b9.squirrel@webmail.plus.net> <87pp7o4hjc.fsf@maritornes.cs.unb.ca> In-Reply-To: <87pp7o4hjc.fsf@maritornes.cs.unb.ca> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Apr 2015 18:21:13 -0000 On 01/04/15 05:08, David Bremner wrote: > Matthew Lear writes: > >> Here's two attachments obtained using the in-built profiler in emacs 24 - >> one for memory profiling and one for cpu. This particular thread took > 30 >> secs to load and emacs was locked up the entire time. I'm no lisp expert, >> but perhaps somebody could interpret this and possible suggest what could >> be going on..? W.r.t. both cpu and memory usage, quite a lot of time seems >> to be spent in indent-rigidly and notmuch-show-insert-thread. >> > > That's consistent with what I've seen with very large text attachements. > Can you try the patch > > id:1427540939-10055-1-git-send-email-markwalters1009@gmail.com [1] > > [1] http://mid.gmane.org/1427540939-10055-1-git-send-email-markwalters1009@gmail.com > Sorry for the late reply. That has definitely made an improvement. Opening a large thread takes much less time with the patch applied. -- Matt