From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.216.66.137 with SMTP id h9cs24716wed; Fri, 22 Oct 2010 06:54:41 -0700 (PDT) Received: by 10.90.99.12 with SMTP id w12mr2306668agb.118.1287755681214; Fri, 22 Oct 2010 06:54:41 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id h28si7101024yha.0.2010.10.22.06.54.40; Fri, 22 Oct 2010 06:54:41 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 8619D1978487; Fri, 22 Oct 2010 09:54:40 -0400 (EDT) Received: from mail-yw0-f50.google.com (mail-yw0-f50.google.com [209.85.213.50]) by rubyforge.org (Postfix) with ESMTP id 6A78C19783BF for ; Fri, 22 Oct 2010 08:38:21 -0400 (EDT) Received: by ywi4 with SMTP id 4so699064ywi.23 for ; Fri, 22 Oct 2010 05:38:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type:cc :subject:from:to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=XFpsUnblpg7OtID2MaGuJaf/4RTikdp9n7nytqNjsdY=; b=QVyV4JxbMcZUArYDsmmOZ39YZqabv8AARkG2BXSWtFdAb82F6tiv516u8Fkop/be6X dUdsBeeB8WjLLsRuVN6GwoLDQQT0VjAXh5m4ADB818cdgee4EMVAj5L3ujF3vpnuXh1Q pPwJcKAfHAbRDmUSGJQIxOwfoZZ6Ay7UrWl+4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=MMPl2L+8Ee1E9LZtpJfibyH9KrhZXHo14x4XIusHdKX5XKYaWz5Qwv3YPim8Glci+U CYmHGO0PQEClqxz7fiMfsTZWTJ7t6ffduZKnWnTuA6SrKkE9HuXF3oW+r3t0vS4gA8fY ly2YvTW3fw7sdFOHvafS0gqlQIcskpU4qZd/o= Received: by 10.101.69.3 with SMTP id w3mr2109614ank.32.1287751100923; Fri, 22 Oct 2010 05:38:20 -0700 (PDT) Received: from localhost (c-24-128-129-146.hsd1.vt.comcast.net [24.128.129.146]) by mx.google.com with ESMTPS id g18sm3500489anh.38.2010.10.22.05.38.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 22 Oct 2010 05:38:18 -0700 (PDT) From: Mark Alexander To: Shadowfirebird In-reply-to: <1287739347-sup-2987@blake> References: <1287739347-sup-2987@blake> Date: Fri, 22 Oct 2010 08:38:16 -0400 Message-Id: <1287750098-sup-8825@r61> User-Agent: Sup/0.11 Cc: sup-talk Subject: Re: [sup-talk] Slow opening of threads? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Shadowfirebird's message of Fri Oct 22 05:23:42 -0400 2010: > Is it me, or is Sup sometimes very slow at opening a thread? I mean: a couple of minutes to open a thread with two or three messages and no attachments, about one time in three? > > It *could* be because my maildir is on the other side of an NFS mount. Or, not. I have that experience with one of my maildirs that is in an ecryptfs directory. It's not quite a couple of minutes, but sometimes up to 30 seconds opening a very long thread. I've seen slowdowns on ecryptfs doing other things like compiles. So my guess is that the slowdown you're seeing is due to NFS. In my experience NFS is a performance hog and should be avoided at all costs. If at all possible, run sup on a single machine with your maildirs (and your .sup directory) on a local disk. If you need to access your mail from other machines, log into your sup-running machine via ssh. Also (and this is perhaps the most important thing), run sup inside a screen session so you won't lose any of your work if the ssh connection goes down. Screen is useful even if you only access your mail from a single machine, because it will keep your session alive if Gnome/KDE crashes or you have to log out and back in for any other reason. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk