6.0.0-git
2020-07-15

[#12729] Throttle new mail queries
Summary Throttle new mail queries
Queue IMP
Queue Version Git master
Type Enhancement
State Duplicate
Priority 1. Low
Owners
Requester slusarz (at) horde (dot) org
Created 2013-10-01 (2479 days ago)
Due
Updated 2013-11-12 (2437 days ago)
Assigned
Resolved 2013-11-12 (2437 days ago)
Milestone
Patch No

History
2013-11-12 18:55:34 Michael Slusarz Comment #4
State ⇒ Duplicate
Reply to this comment
#12705
2013-10-14 13:49:07 Jan Schneider Summary ⇒ Throttle new mail queries
 
2013-10-14 13:48:53 Jan Schneider Version ⇒ Git master
Queue ⇒ IMP
 
2013-10-14 13:48:36 Jan Schneider Comment #3 Reply to this comment

[Show Quoted Text - 14 lines]
That's exactly the reason why I replaced the single 
Kronolith::listEvents() call from the basic interface with individual 
Kronolith_Driver::listEvents() calls for the dynamic interface.

This issue doesn't have anything to do with listEvents calls anyway, 
this should be cached (or rather skipped) with some sane TTL in 
IMP_Notification_Handler_Decorator_NewmailNotify instead.
2013-10-01 22:10:51 Michael Rubinsky Comment #2
State ⇒ Feedback
Reply to this comment
I disagree with some of this.

Calendars can come from any source; internal to kronolith, 
listTimeObjects, remote calendars, etc... Rolling *all* of these up 
into one listEvents call would prevent the UI from displaying any 
entries until ALL of the results are returned from all of the calendar 
providers. Remote calendars, especially, could slow the process down. 
IMO, it's better to update the UI quicker with the locally stored 
calendars while waiting for any slower calendars to load.

If anything, we might be able to batch all "external", "remote" and 
"internal" providers into separate calls, but not everything into a 
single monster listEvents call.
2013-10-01 18:53:35 Michael Slusarz Comment #1
Type ⇒ Enhancement
State ⇒ New
Priority ⇒ 1. Low
Summary ⇒ Pool multiple requests
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
Reply to this comment
From #12705:

[Show Quoted Text - 10 lines]
These requests should be pooled into a single listEvents (or 
equivalent) action.

Saved Queries