QoS on Cyrus traffic

[Ken Murchison]

Philip A. Prindeville wrote:
> On 01/08/2010 12:48 PM, Ken Murchison wrote:
>> Philip A. Prindeville wrote:
>>> On 01/08/2010 12:06 PM, Ken Murchison wrote:
>>>> Can we get some opinions on the feature request below:
>>>>
>>>> https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3184
>>>>
>>>> I'm pretty much convinced that such a feature is worth adding, the only question is where should it be configured: imapd.conf or cyrus.conf ?
>>>>
>>> Well, since pop3 and lmtp can probably also benefit from it, I say cyrus.conf... only problem is I'm not as competent at adding options to cyrus (globally) as to imapd.
>> It can also be a per-service option if its in imapd.conf by prepending the option with the service name, e.g.: myimapd_qosmarking
> 
> I'm not sure there's much value-add in allowing POP3 and IMAP to run at different priorities (other than to discourage people from using POP3 by offering truly bad service).
> 
> The granularity of most sites' QoS setting is that all email-related traffic (POP3, IMAP, SMTP, and LMTP) gets dumped in the same bucket.
> 
> Only LDAP, which requires slightly more spritely interactivity for character-by-character address completions, needs to be provisioned at a higher priority.
> 
> Since it's going to be new to most people, I say we allow a single knob, and as people get used to having it, if there's enough clamor for greater fine-tuning, we revisit it.
> 
> That work for you?


Any imapd.conf new option can automatically be global and/or 
per-service.  The underlying infrastructure is already there.

-- 
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University