Enormously slow and unefficiend handling of external ICS calendars embedded in Team Calendars

Paweł K. October 17, 2012

We are considering purchasing Team Calendars to visualize leaves of our teams that are currently managed JIRA (each leave is a separate task of a special type). As Team Calendars can't import multi-day events from JIRA, we created a script that extracts leaves from JIRA and serves them as events in the ICAL format.

Now, we'd like to subscribe to that ICAL with Team Calendars and present such a leave calendar in Confluence.

The huge problem we faced is the inefficiency of the Team Calendars. It's fast with small .ics files; for 20 events the page renders in about 100 miliseconds. When an .ics file contains 100 events then Team Calendars renders one month-view page in approx. 2 seconds - not so good, but let's call it acceptable. But rendering the calendar view from an .ics of 1000 events takes 40-60 seconds per one page! This means it's not usable... Moreover the processors goes red during this loading time.

To make sure it's not just a problem of our .ics file, we tested this with many public ICAL resources (including some from Google Calendar) and the problem is similar no matter the source.

Do you think we can do something with it? Have you noticed this problem before? Any solutions?

Thank you

1 answer

1 accepted

0 votes
Answer accepted
hsuhailah
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 23, 2012

This issue has been resolved. Customer moved the Confluence installation to a faster server and the page view loading time changed to approx. 2 secs for an approx. 1000-item ICS.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events