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 2C2806DE19AD for ; Fri, 3 Apr 2015 16:05:00 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.795 X-Spam-Level: X-Spam-Status: No, score=0.795 tagged_above=-999 required=5 tests=[AWL=0.795] 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 40n0yae7YbZR for ; Fri, 3 Apr 2015 16:04:57 -0700 (PDT) Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net [87.98.215.224]) by arlo.cworth.org (Postfix) with ESMTPS id D01A26DE19B7 for ; Fri, 3 Apr 2015 16:04:55 -0700 (PDT) Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim 4.80) (envelope-from ) id 1Yd9xA-0007V1-EF; Wed, 01 Apr 2015 04:08:33 +0000 Received: (nullmailer pid 24553 invoked by uid 1000); Wed, 01 Apr 2015 04:08:23 -0000 From: David Bremner To: Matthew Lear Subject: Re: emacs / vim - time taken to open threads In-Reply-To: <49796ef89d505ab1039478982568a0b9.squirrel@webmail.plus.net> References: <5511DE10.80107@bubblegen.co.uk> <87384u6lgb.fsf@maritornes.cs.unb.ca> <49796ef89d505ab1039478982568a0b9.squirrel@webmail.plus.net> User-Agent: Notmuch/0.19+96~g703c8f9 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Wed, 01 Apr 2015 06:08:23 +0200 Message-ID: <87pp7o4hjc.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain 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: Fri, 03 Apr 2015 23:05:00 -0000 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