6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
1/7/26
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#12705] Rate limit polling for new mail notifications
*
Your Email Address
*
Spam protection
Enter the letters below:
. .. . .._..___ |__|| \ / | [__ | ||___ \/ _|_[___
Comment
>> In my IMAP account, I have a fair number of folders that need to be >> polled for new messages (about 25) as I use Sieve to sort messages >> upon arrival. This means checking for new messages is a relatively >> expensive operation. > > What does Sieve have to do with this? Sieve is independent of polling. > >> When 'Display notification when new mail arrives?' in the Mail >> preferences is selected, it looks like this check is performed for >> each POST request. This means that if multiple POST requests are send >> more or less simultaneously, this check is run many times in >> parallel. For instance, if in a month view of Kronolith I move to the >> next month, 13 POST requests are fired off within a few milliseconds >> (in my agenda there are six calenders, five address books, one >> tasklist and one holidays). Each of these will run >> >> horde/services/ajax.php/kronolith/listEvents > > That shouldn't happen. For a task such as this in kronolith, we > should really be pooling all of these into a single request. But > that's a separate enhancement ticket... > >> All in all this takes approximately 10 seconds, during which time the >> check for new messages runs 13 times (pretty much in parallel). If I >> disable the new mail notifications, the same action takes less than 2 >> seconds (I made sure these aren't cached results). >> >> It would be nice if there was a preference that would allow to >> prevent polling for new messages if less than 'X' seconds have passed >> since the last poll was started. This would prevent running polls in >> parallel, fighting for attention from Dovecot and which in the end is >> just a waste of resources. > > We should probably just use the "refresh" interval that currently exists. > > This seems a reasonable feature to put into 6.2.
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers