On 07 Dec 2009, at 10:33, John Madden wrote: > In a 2.3.15 murder I'm seeing high frontend server cpu usage and I'm > wondering if it's normal or if there's something I can do to reduce > it. > What are the bottlenecks that can lead to proxyd pegging a cpu for > several seconds, particularly during login (using imapproxy to reduce > logins appears to reduce system load) and when not using TLS? At a guess, it sounds like load from LIST. You should be able to see what's causing the load if you have several seconds. For example, enable telemetry and look for long turn around. Or use strace (or equiv). Have you experimented with foolstupidclients? What is your client mix? How many mailboxes do you have? :wes > Frontend's config (trimmed): > > defaultpartition: default > partition-default: /dev/null > duplicatesuppression: 0 > singleinstancestore: 1 > lmtp_downcase_rcpt: yes > allowanonymouslogin: no > popminpoll: 1 > umask: 077 > allowplaintext: yes > sasl_mech_list: PLAIN > sasl_pwcheck_method: saslauthd > mupdate_config: unified > mupdate_authname: murder > mupdate_port: 3905 > lmtpsocket: /var/imap/socket/lmtp > idlesocket: /var/imap/socket/idle > mailnotifier: mailto > notifysocket: /var/imap/socket/notify > sievenotifier: mailto > annotation_db: skiplist > duplicate_db: berkeley-nosync > quota_db: skiplist > subscription_db: skiplist > mboxlist_db: skiplist ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
