Aaron Stone wrote:
Paul J Stevens <[EMAIL PROTECTED]> said:


Aaron Stone wrote:

I think it's a really interesting idea, and makes a lot of sense once
we have the headers parsed out as there'd be no reason to search the
messageblks, and indeed no reason to look at them at all unless it's
the message you want.

Uhm, howabout imap searches on the messagebodies. They will always require looking at the messageblks. I would prefer defering the actual search to the databaseengine, instead of retrieving and searching each message one by one, as is currently the case.


Very good point, I did forget about that -- or might have had some idea in the
back of my head like using a search engine to maintain a more highly
searchable body cache.

I wonder what kind of indexes this would produce for a large dbmail installation :-) ?

MySQL with InnoDB tables no longer supports fulltext
indices :-(

The current limitations of the databaseengine shouldn't lead us into loosing sight of dbmail's core design. Dbmail imo should offer a clean and consistent interface on the email storage in the database, and be very good at that. My guess is that searching on unindexed blobs will still be faster than retrieving-parsing-searching each message one by one in dbmail inself. That is, unless we move from a one-message-at-a-time approach, to handling whole groups of messages at once when it comes to retrieval. Only than, in combination with a really fast parser, might we beat the database. Just guessing though, based on IO bottlenecks I detect.

A similar objection goes for the whole caching thread. If we start checking/updating the cache each time a message is retrieved, we'll be up shit creek without a paddle. IO performance will simply drop dead unless we're very careful about it. Some kind of async process to handle caching updates would indeed make sense here.

--
  ________________________________________________________________
  Paul Stevens                                         [EMAIL PROTECTED]
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands_______________________________________www.nfg.nl

Reply via email to