Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Slow opening of threads?
Date: Fri, 22 Oct 2010 13:04:34 +0200	[thread overview]
Message-ID: <1287745423-sup-8192@qwerzila> (raw)
In-Reply-To: <1287739347-sup-2987@blake>

Excerpts from Shadowfirebird's message of fr. okt. 22 11:23:42 +0200 2010:
> It *could* be because my maildir is on the other side of an NFS mount.  Or, not.   

I'd test that :) I have no problems - might be that simple seek
operations are really expansive over NFS.

- gaute


  parent reply	other threads:[~2010-10-22 11:04 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 [this message]
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
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=1287745423-sup-8192@qwerzila \
    --to=eg@gaute.vetsj.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