Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Shadowfirebird <shadowfirebird@gmail.com>
To: Mark Alexander <marka@pobox.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Slow opening of threads?
Date: Fri, 22 Oct 2010 14:03:15 +0100	[thread overview]
Message-ID: <1287752134-sup-9563@blake> (raw)
In-Reply-To: <1287750098-sup-8825@r61>


[-- Attachment #1.1: Type: text/plain, Size: 1648 bytes --]

Excerpts from Mark Alexander's message of Fri Oct 22 13:38:16 +0100 2010:
> Excerpts from Shadowfirebird's message of Fri Oct 22 05:23:42 -0400 2010:
> 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.

Interesting that you should mention that, because I have an encrypted $HOME (bad choice at Ubuntu install time -- ::shrug:: ).  I suppose it might apply the other way around, too.

> 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.

I think I'll plan to run something like offlineIMAP (or just rsync) to sync my maildir to a local folder when I rework my machine in the near future.  Also, I'm moving the whole house to gigabit ethernet, so maybe that will help.

> 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.

Not a problem here; there's no ssh involved.  The maildir is on the server downstairs, and I've got my home directory there mounted here via NFS.

-- 
If you will practice being fictional for a while, you will understand that
fictional characters are sometimes more real than people with bodies and
heartbeats.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2010-10-22 13:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  9:23 Shadowfirebird
2010-10-22 10:40 ` Amadeusz Żołnowski
2010-10-22 11:48   ` Shadowfirebird
2010-10-22 13:09     ` Moritz Wilhelmy
2010-10-22 18:02       ` Shadowfirebird
2010-10-22 23:32         ` Moritz Wilhelmy
2010-10-22 11:04 ` Gaute Hope
2010-10-22 11:16 ` Philipp Überbacher
2010-10-22 12:21   ` Ben Walton
2010-10-22 12:38 ` Mark Alexander
2010-10-22 13:03   ` Shadowfirebird [this message]
2010-10-22 16:28     ` Mark Alexander
2010-10-22 17:19 ` Sascha Silbe
2010-10-22 19:56   ` Shadowfirebird
2010-10-23  8:28     ` Sascha Silbe
2010-10-23 10:42       ` Shadowfirebird

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1287752134-sup-9563@blake \
    --to=shadowfirebird@gmail.com \
    --cc=marka@pobox.com \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox