Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Slow opening of threads?
Date: Fri, 22 Oct 2010 08:21:26 -0400	[thread overview]
Message-ID: <1287750034-sup-6402@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1287746050-sup-6114@eris>

Excerpts from Philipp Überbacher's message of Fri Oct 22 07:16:13 -0400 2010:

> That sounds weird. In my experience it's only slow when flushing index,
> which means everything is frozen for a couple of seconds. Opening
> threads is fast enough here. Threads with 50-100 messages take a couple
> of seconds though, but it's acceptable.

I periodically see slow thread loading and I'm also doing Maildir over
NFS.  It's not frequent enough that I've bothered to look into it, but
it does happen from time to time.  I've seen it on threads of various
sizes.

HTH.
-Ben

--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

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

  reply	other threads:[~2010-10-22 13:45 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 [this message]
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=1287750034-sup-6402@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --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