<div><br></div>memcached would certainly be fast, but what sort of authentication rate are you talking about here. My bet is that you've got other bits of system, such as the authentication validation with the target IMAP server, that will be more of a dominant term when it comes to the performance of your system.<div>
<br></div><div>I deployed an nginix proxy to assist in my migration to Cyrus (once all my users were on Cyrus, murder took over) -- just had it do lookups against our LDAP directory to determine which IMAP provider to redirect to, it worked perfectly fine.</div>
<div><br></div><div>-rob<br><br><div class="gmail_quote">On Wed, Mar 17, 2010 at 10:35 PM, Robert Mueller <span dir="ltr"><<a href="mailto:robm@fastmail.fm">robm@fastmail.fm</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> But I thought a memcache lookup will be much more inexpenisve than<br>
> connecting to a mysql db to do lookup for every cyrus connection<br>
<br>
</div>Probably slightly. But what happens if the value isn't in memcached?<br>
Where do you get the value from?<br>
<br>
Anyway, it's still WAY better than doing:<br>
<div class="im"><br>
> > > $user['user1'] = 10.1.1.1;<br>
> > > $user['user2'] = 10.1.1.2;<br>
> > > ----<br>
> > > $user[user15000]=10.1.1.1;<br>
<br>
</div>For every lookup.<br>
<br>
Rob<br>
<div><div></div><div class="h5">----<br>
Cyrus Home Page: <a href="http://cyrusimap.web.cmu.edu/" target="_blank">http://cyrusimap.web.cmu.edu/</a><br>
Cyrus Wiki/FAQ: <a href="http://cyrusimap.web.cmu.edu/twiki" target="_blank">http://cyrusimap.web.cmu.edu/twiki</a><br>
List Archives/Info: <a href="http://asg.web.cmu.edu/cyrus/mailing-list.html" target="_blank">http://asg.web.cmu.edu/cyrus/mailing-list.html</a><br>
</div></div></blockquote></div><br></div>