2013/8/10 Sam Varshavchik <mr...@courier-mta.com>
>
>
> - usage of a distributed file system (glusterFS or similar) with support
>> of many active-active nodes
>> --> this is already working (i've tested) but too poor performance
>> --> what about a proxy that split requests between read and write, read
>> requests goes to a geo-replicated node with higer performances and write
>> requests goes to an active-active note with lower performances
>>
>
> 99% of what an IMAP server does is reading mail. The only time an IMAP
> server writes anything of substance, to the mailbox, is when you save a
> draft message, from your mail client, in the drafts folder.
>
Or when you move / create a folder, but basically i agree with the fact
that the 90% of time the server is reading, and this is why i'm suggesting
to support 2 kind of interaction: read only that works on a distributed,
high performance file system, and write that works on a lower performance
file system, but i haven't a deep knowledge of how courier works so i'm
not able to estimate the effort of writing this feature for courier, or
creating a proxy that stays in-front of it and split requests depending on
the protocol payload.
Can you help me to estimate it?
--
/*************/
nik600
http://www.kumbe.it
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
