store sqlite suggestion

[pfelt-Urct4Ww6//Pz1n+]

alex,
i've added the following to my store.db in hopes it'll speed up delivery
a bit (it's running now, but i'm not sure i'll really be able to tell a
difference). i found that there is no index on the subject line in
conversation.

create index conversation_subject on conversation(subject);

my db has 351,701 conversations in the conversation table. i doubt it'll
make a *huge* difference under normal loads, but i bet it'll help a bit.

[Alex Hudson]

Hey Pat,

Post by pfelt-Urct4Ww6//Pz1n+
i've added the following to my store.db in hopes it'll speed up delivery
a bit (it's running now, but i'm not sure i'll really be able to tell a
difference). i found that there is no index on the subject line in
conversation.
create index conversation_subject on conversation(subject);
my db has 351,701 conversations in the conversation table. i doubt it'll
make a *huge* difference under normal loads, but i bet it'll help a bit.

I'd be interested to know if it makes any difference at all to be honest
- I suppose it would potentially make a difference looking up existing
conversations for incoming mail. The opportunity cost is going to be the
size of the index, but I suppose that might not add much overhead.

I'm wondering if maybe we should look at adding some kind of high-level
stats system into the store as well as looking at callgrind/etc...

Thanks

Alex.


--
This message was scanned by Better Hosted and is believed to be clean.
http://www.betterhosted.com