Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Fwd: Re: Crash while in thread-view-mode
Date: Sun, 11 Oct 2009 13:28:48 -0700	[thread overview]
Message-ID: <1255292742-sup-3957@masanjin.net> (raw)
In-Reply-To: <1254955312-sup-7085@ben-laptop>

Reformatted excerpts from Ben Gamari's message of 2009-10-07:
> I understand that designing software around a contingency like this
> might not be the best practice, but the frequency with which I've
> needed to rebuild really does make me think that ruby isn't the best
> language for the indexer.

The indexer isn't in Ruby, it's written in C++ in the case of Xapian and
C in the case of Ferret.

> This is easily the fifth time I've needed to rebuild and each time it
> has taken over 30 minutes for 1.5 GB of mail. That's substantially
> less than 1MB/second for what should be an I/O bound operation. Ouch.

I think this isn't the indexer's fault so much as the mbox parsing,
which is Ruby.

I'm sorry you've had to rebuild the index so many times. The Xapian side
of things is very new, and I think you've had a run of bad luck. But I
am personally not motivated to improve index time performance, because
that's not a common event. At least, it shouldn't be.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2009-10-11 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 22:42 Ben Gamari
2009-10-11 20:28 ` William Morgan [this message]
2009-10-11 21:04   ` Ben Gamari
2009-10-13 20:18   ` Ben Gamari

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=1255292742-sup-3957@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --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