6.0.0-beta1
7/16/25

[#6567] webdav performance problem with big calendars
Summary webdav performance problem with big calendars
Queue Kronolith
Queue Version 2.2-RC2
Type Enhancement
State Rejected
Priority 1. Low
Owners
Requester olivier.lelain (at) xrce (dot) xerox (dot) com
Created 04/04/2008 (6312 days ago)
Due
Updated 04/04/2008 (6312 days ago)
Assigned
Resolved 04/04/2008 (6312 days ago)
Milestone
Patch No

History
04/04/2008 10:31:03 PM Jan Schneider Comment #2
State ⇒ Rejected
Reply to this comment
This is how calendar publishing over WebDAV works, unfortunately. Once 
we have CalDAV support, this should be much better because it supports 
atomic operations on single events.
04/04/2008 03:58:47 PM olivier (dot) lelain (at) xrce (dot) xerox (dot) com Comment #1
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ webdav performance problem with big calendars
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
Reply to this comment
I would like to implement a horde/kronolith solution for allowing my 
Linux users to connect to a calendaring server using sunbird/lightning.

I widely tested it and it works very well, except for users having 
very big calendar (more than 2000 entries) when they just add or 
modify something.

I tried everything to improve performance (using memecache for 
instance) with no success.



When I watch the horde.log , it seems that the whole username.ics is 
"reinjected" in the mysql database, not only what were modified, thus 
having a 30s delay for each modified, deleted or created.event

I don't know if i'm wrong. If not, I don't know if it's feasable to 
enhance it.



Thank you.


Saved Queries