Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] header cache
Date: Wed, 16 Jan 2008 12:48:47 -0800	[thread overview]
Message-ID: <1200516410-sup-1963@south> (raw)
In-Reply-To: <1200514969-sup-7541@clarabella.clarabella>

Reformatted excerpts from Giorgio Lando's message of 2008-01-16:
> Anyway I guess that a cache helps only relatively with such a monster
> (or at least also mutt's header cache helps only a bit with 40000
> messages in an IMAP folder), so I will be able to make tests with
> other, much smaller imap folders.

If you look at the log messages, there's one at the emitted at the
beginning of loading the headers, and one at the end, so you can see
exactly how much time adding a cache will save you (minus however long
it takes to load things in from disk).

I'm curious what this number is for 40000 headers. It seems to be about
10 seconds for my 5000-message IMAP folder, so I can imagine it being
quite significant.

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2008-01-16 20:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 12:54 Giorgio Lando
2008-01-16  3:24 ` William Morgan
2008-01-16 20:26   ` Giorgio Lando
2008-01-16 20:48     ` William Morgan [this message]
2008-01-16 22:04       ` Giorgio Lando
2008-01-16 22:58         ` Alec Berryman
2008-01-16 23:36           ` Giorgio Lando
2008-01-17  8:13         ` Nicolas Pouillard
2008-01-17 11:40           ` Giorgio Lando
2008-01-17 14:56             ` Nicolas Pouillard
2008-01-22  2:36               ` William Morgan
2008-01-22  8:40                 ` Nicolas Pouillard
2008-01-23 20:33                   ` Gabriel Sean Farrell
     [not found]                   ` <1201071069-sup-6394@south>
     [not found]                     ` <1201079068-sup-438@ausone.inria.fr>
2008-01-25  3:28                       ` William Morgan
2008-01-25  8:50                         ` Nicolas Pouillard

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=1200516410-sup-1963@south \
    --to=wmorgan-sup@masanjin.net \
    /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