Paul J Stevens wrote: > Aaron Stone wrote: >> Paul, if the IDLE support is handled with polling, shouldn't we have the >> polling interval be configurable? (My apologies if this is already the >> case, I haven't had a change to look at the code this past weekend.) > > I'm currently triggering a set of queries every 10 seconds. However, > since these are repeated over and over, the query planner and cache > appear to be able to deal with them very effeciently. But of course, > there is a ceiling here when you're dealing with many changes in the > database and many running idle commands. > > Adding a config_key 'idle_loop_timeout' to the IMAP section, combined > with a config_key for the CAPABILITY string should give admins enough > knobs to tweak performance while running busy servers.
For 2.3, I want to add an other improvement that will make IDLE very cheap. Using triggers we can update the relevant mailbox row when ever a message row is added, updated or deleted. A simple mtime field in the mailboxes table that is updated by triggers will make it very cheap to poll for mailbox changes. That would mean the mysql requirement will be 5.0 or better for 2.3. But I don't think that will be a problem, right? -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
