search for: fsync_disable

...them. 2) Dovecot is faster than Cyrus, at least in test. I didn't really expect this either, because with maildir Dovecot has to do extra rename() calls for all flag changes. I'm guessing it's expunges that are slowing Cyrus down the most (that causes it to rewrite its cache file). 3) fsync_disable=yes + mmap_disable=yes almost doubles the performance with 1 client, and over quadruples the performance with 10 clients. Why fsync_disable=yes + mmap_disable=no doesn't give that big of a performance difference? I've no idea. This is anyway such a large performance increment that I'll...

...r a second to get saving to start writing several fields to dovecot.index.cache file. Then ran imaptest for 60 seconds that did nothing but save messages using IMAP APPEND commands. The summary is that multi-dbox is almost 10x as fast as maildir when fsync is disabled and 2,5 faster with fsyncing: fsync_disable=yes: multi-dbox : ~1700 -> ~1500 msgs/sec, 90842 msgs/60 sec single-dbox: ~1700 -> ~1400 msgs/sec, 86149 msgs/60 sec maildir : ~330 -> ~110 msgs/sec, 9789 msgs/60 sec fsync_disable=no: multi-dbox : ~220 -> ~170 msgs/sec, 10113 msgs/60 sec maildir : ~100 -> ~70 msgs/sec,...

I?m experiencing write activity that?s somewhat different from my previous qmail/courier-imap/Maildir setup. This more outspoken in v.1.1.x than v1.0.x (I?m using Maildir). Write activity is about half that of read activity when measuring throughput. But when measuring operations it?s about 5-7 times as high (measured with zpool iostat on ZFS). I think this might be due to the many small updates

...my imaptest catched the bug only in CVS HEAD but not in branch_1_0 even though both had it. Anyway, now the imaptest runs nicely for both, and I'm again optimistic that the bug count is low enough for v1.0 to be released soon :) BTW. My previous benchmarks which showed how mmap_disable=yes and fsync_disable=yes give huge performance benefits are pretty XFS-specific. I did some quick tests with ext3 and the differences were quite small with it. I'll probably do another proper run of tests later. + pop3: Commit the transaction even if client didn't QUIT so cached data gets saved. - Fixed a...

...my imaptest catched the bug only in CVS HEAD but not in branch_1_0 even though both had it. Anyway, now the imaptest runs nicely for both, and I'm again optimistic that the bug count is low enough for v1.0 to be released soon :) BTW. My previous benchmarks which showed how mmap_disable=yes and fsync_disable=yes give huge performance benefits are pretty XFS-specific. I did some quick tests with ext3 and the differences were quite small with it. I'll probably do another proper run of tests later. + pop3: Commit the transaction even if client didn't QUIT so cached data gets saved. - Fixed a...

...ections(default): 2048 mail_max_userip_connections(imap): 2048 mail_max_userip_connections(pop3): 10 mail_max_userip_connections(managesieve): 10 mail_privileged_group: mail mail_uid: vmail mail_gid: mail mail_location: maildir:/var/mail/mailboxes/%d/%n:INDEX=/var/mail/indexes/%d/%n mail_debug: yes fsync_disable(default): yes fsync_disable(imap): yes fsync_disable(pop3): yes fsync_disable(managesieve): no mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr...

...n login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login first_valid_uid: 512 last_valid_uid: 512 first_valid_gid: 512 last_valid_gid: 512 mail_location: maildir:~/ fsync_disable(default): yes fsync_disable(imap): yes fsync_disable(pop3): yes fsync_disable(managesieve): no mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_executable(managesieve): /usr/libexec/dove...

...iserfs log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 110 last_valid_uid: 110 mail_location: maildir:/var/qmail/mailnames/%d/%n/Maildir fsync_disable: yes lda: postmaster_address: postmaster at code-factory.de mail_plugins: sieve mail_plugin_dir: /usr/local/lib/dovecot/lda fsync_disable: no auth default: passdb: driver: passwd-file args: /usr/local/etc/passwd.dovecot userdb: driver: passwd userdb: driver:...

I thought I'd try benchmarking with dbmail (v2.2.4) to see how much slower a SQL backend could actually be. Skip to bottom for the conclusions. Originally I ran the tests with the databases being in XFS filesystem. MySQL's performance was horrible. It went 3-7x faster with ext3. MySQL 5.0.30 backend (innodb): ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0

Hello, I'm new to dovecot and I've been taking my time examining what makes dovecot work. If I have imap and pop3 listed as protocols, dovecot -n outputs: mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 I don't understand why imap is listed twice once as

.../usr/local/libexec/dovecot/managesieve-login login_process_per_connection: no login_process_size: 0 login_processes_count: 64 login_max_processes_count: 2048 login_max_connections: 512 max_mail_processes: 2048 mail_max_userip_connections: 2048 verbose_proctitle: yes mail_location: maildir:~/Maildir fsync_disable(default): yes fsync_disable(imap): yes fsync_disable(pop3): yes fsync_disable(managesieve): no maildir_copy_preserve_filename: yes maildir_very_dirty_syncs: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/doveco...

...till pop up. Since I suspect these errors to be responsible for customers complaining about downloading mails twice, I'd like to fix them. Our setup has multiple servers sharing the same NFS-mounted directory for maildirs and indexes; we have set mmap_disable = yes dotlock_use_excl = yes fsync_disable = no mail_nfs_index = yes lock_method = fcntl As far as I can tell, for at least one of these errors, there was no concurrent access to the mailbox in question. What can I do to solve this problem, or to analyze it further? Ulrich

...FS2 on rhel 6.1. We have a two node cluster sharing two GFS2 filesystem - Index GFS2 filesystem to store users indexes - Mailbox data on a GFS2 filesystem The specific configs for NFS or cluster filesystem we used: mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes fsync_disable=no lock_method = fcntl mail location : mail_location = mdbox:/var/vmail/%d/%3n/%n/mdbox:INDEX=/var/indexes/%d/%3n/%n But this seems not to work for GFS2 even doing user node persistence, maillog is plagged of errors and GFS2 hangs on stress testing with imaptest, many corrupted index for example...

I've just updated from 1.0.14 to 1.1.1 (Maildirs). According to <URL:http://wiki.dovecot.org/Upgrading/1.1>, "dovecot-uidlist file is in a new format. The old format is automatically converted to new one." When I try to delete a message (which moves it to the IMAP Trash folder), I get the following looping sequence of errors until I cancel the delete operation in the mail

...ection: no login_max_processes_count: 1024 max_mail_processes: 1024 mail_max_userip_connections(default): 20 mail_max_userip_connections(imap): 20 mail_max_userip_connections(managesieve): 10 first_valid_gid: 0 mail_privileged_group: mail mail_location: maildir:~/Maildir:INDEX=/var/cache/dovecot/%n fsync_disable: yes maildir_very_dirty_syncs: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota acl imap_acl mail_plugins(imap): quota i...

...ses only one CPU) - CentOS 5 - 15GB qcow2 image on XFS filesystem - Zimbra 5.0 RC2 RHEL5 x86_64 - Dovecot latest hg, dbox format Both Zimbra and Dovecot were tested running on the same kvm image. All data could be cached in memory, so this didn't really test disk I/O. Dovecot was run with fsync_disable=no. Running with =yes would have made its performance even better. Zimbra features/bugs -------------------- Zimbra's SEARCH command doesn't support substring searching as IMAP requires: 1 search text performance * SEARCH 136 183 227 231 232 233 245 1 OK SEARCH completed 2 search text er...

...ovecot/pop3-login -D login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_process_per_connection: no login_processes_count: 4 login_max_processes_count: 64 max_mail_processes: 2048 mail_max_userip_connections: 1024 verbose_proctitle: yes mail_location: maildir:~/Maildir fsync_disable(default): yes fsync_disable(imap): yes fsync_disable(pop3): yes fsync_disable(managesieve): no maildir_copy_preserve_filename: yes maildir_very_dirty_syncs: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/doveco...

...ite a while - since back in the 1.0 days I believe. I'm somewhat new here. Anyway... The Wiki article on NFS states that 1.1 and newer will flush attribute caches if necessary with mail_nfs_storage=yes. We're running 1.2.8 with that set, as well as mail_nfs_index=yes, mmap_disable=yes and fsync_disable=no. We have a pool of POP/IMAP and SMTP machines that are accessing the maildirs, and can't guarantee any sort of user session affinity to a particular host. We also mount our NFS shares with 'noac', which is what I'm writing to ask about. I'd like to stop doing that for perfor...

...t running 8.3-RELEASE-p3 FreeBSD amd64 mailboxes (Maildir), control files and indexes are on NFS (v3,tcp) mail_nfs_storage = yes lock_method = fcntl [didn't touch the following] # Mail index files also exist in NFS. Setting this to yes requires # mmap_disable=yes and fsync_disable=no. mail_nfs_index = yes served by an Isilon s200 node (OneFS 6.5.5.22) procmail delivers in the same location through postfix-2.8.7 The filer shows *a lot* of such messages : 2013-08-02T14:12:29+02:00 <0.5> XXXX-10(id10) /boot/kernel.amd64/kernel: [lkf_delegate.c:2752](pid 46390=...

Hi all, I upgraded to dovecot 1.1.6 to be able to use NFS. Got a little issue: I can't move mail to another IMAP folder (so I can't delete to: moving to .trash does not work. Error message Oct 31 11:07:45 jozua-mailserver dovecot: IMAP(nicolette at kerknet.org): fdatasync_path(/var/mail/kerknet.org/nicolette/Maildir/.Trash/cur) failed: Invalid Argument I tried to use ll