Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
* [sup-devel] [Heliotrope] What exactly does reordering do? Is it still necessary?
@ 2012-02-22 22:00 Michael Stapelberg
  2012-02-23  6:39 ` William Morgan
  0 siblings, 1 reply; 2+ messages in thread
From: Michael Stapelberg @ 2012-02-22 22:00 UTC (permalink / raw)
  To: sup-devel

Hi,

I just realized that I forgot to import the maildir in which I store my sent
messages. After adding them to heliotrope, do I have to reorder the index? What
exactly does it do and why is that necessary?

I’m a bit confused because commit
https://github.com/wmorgan/heliotrope/commit/f7bfda9dd83db1b9cd2a51ba2599da81fc1b87c1
talks about "reindex without --reorder".

Best regards,
Michael

PS: The real time it takes to reorder my index is about 1 hour and 30 minutes :(
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [sup-devel] [Heliotrope] What exactly does reordering do? Is it still necessary?
  2012-02-22 22:00 [sup-devel] [Heliotrope] What exactly does reordering do? Is it still necessary? Michael Stapelberg
@ 2012-02-23  6:39 ` William Morgan
  0 siblings, 0 replies; 2+ messages in thread
From: William Morgan @ 2012-02-23  6:39 UTC (permalink / raw)
  To: sup-devel

Excerpts from Michael Stapelberg's message of 2012-02-22 14:00:27 -0800:
> I just realized that I forgot to import the maildir in which I store
> my sent messages. After adding them to heliotrope, do I have to
> reorder the index?

Probably yes.

> What exactly does it do and why is that necessary?

Heliotrope only ever returns messages in the order in which they were
indexed. So if you import mail from different sources, one after the
other, unless those sources happen to be in chronological order, you
will have to reorder.

It's a little hard to see that this is happening because Turnsole
reorders the items it displays (for complicated reasons), but you'll
probably start to notice it as you paginate.

> I’m a bit confused because commit
> https://github.com/wmorgan/heliotrope/commit/f7bfda9dd83db1b9cd2a51ba2599da81fc1b87c1
> talks about "reindex without --reorder".

If the index ever becomes corrupted, it's nice to be able to rebuild it.
That's the only real reason to do that. (Or maybe the index format
changes in later releases, etc.)

> PS: The real time it takes to reorder my index is about 1 hour and 30
> minutes :(

Sorry. But the point of indexing is to frontload all the work, so that
import time (which has to only happen once) is slow, but search time is
fast.

-- 
William <wmorgan@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-02-23  6:40 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-02-22 22:00 [sup-devel] [Heliotrope] What exactly does reordering do? Is it still necessary? Michael Stapelberg
2012-02-23  6:39 ` William Morgan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox