Hi,
I think I may have found something.
After importing a very large calendar I ran the calendar server from
the terminal (not detached) and noticed 1000s of similar entires:
2009-02-17 13:46:05+0100 [-] [caldav-8009] [-]
[twistedcaldav.directory.appleopendirectory.OpenDirectoryService#info]
Unable to find any record with email *...@ripe.net
Could it be that every single event with users attached to it a look
up is done and fails? This would explain why large calendars cause
problems. It would not however, explain why 1000 entries (no
attendees) made in the iCal client results in an non-viewable calendar
(others attempting to view it timeout).
On Feb 17, 2009, at 11:30, Sean McAvoy wrote:
On Feb 13, 2009, at 21:17, Cyrus Daboo wrote:
Hi Sean,
--On February 13, 2009 11:49:13 AM +0100 Sean McAvoy <smca...@ripe.net
> wrote:
I have tried this and found the same basic problem, other users
cannot
access calendars with lots of events (tested 900-9500 event
calendars).
Do you have any other suggestions on how to narrow down the problem?
Calendars of several thousand ought to be OK. A lot will depend on
disk performance though - are you always using a local disk?
Yes, I am always using local disk RAID 5 on 3 73GB SAS drives.
During the peak times I've run both top and iostat, top reports
python processes at 100%, iostat reports little activity.
I have also created 1000 entries via the iCal client and experienced
the same problem, after removing 900 of the entires (using the
command line) the problem disappeared.
--
Cyrus Daboo
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
