I want to add a method of caching the built calendars, since drawing them, especially the year calendar, is very resource-intensive.

We need a setting for the length of time to keep the cached values (probably defaulting to one day) and check in hook_form_alter() when a calendar date field is being updated so we can destroy the caches to pick up the new values.

Comments

gpk’s picture

gpk commented

#437432: Slow performance with multiple repeating events marked as duplicate.

karens’s picture

karens commented

There is progress in Views now to make it easier to cache the calendars. Someone needs to come back and see if and how they will work for calendars and whether we need any additional fixes to Calendar to make this work well.

See #468824: Add caching system to Views and maybe also #340701: Incorperating Block Cache.

arlinsandbulte’s picture

arlinsandbulte commented

Just curious, any update?

gpk’s picture

gpk commented

@3: I'm now using Calendar on a live site but have not experimented with Views caching yet. Looks like it should work. Maybe just give it a try?

arlinsandbulte’s picture

arlinsandbulte commented

I just experimented with the views caching a little... unfortunately bad news for the calendar module.
The caching completely breaks the calendar block. It becomes stuck on on the current month and links in the mini-cal don't all work quite properly.
The full calendar seems ok first, but I don't think it is ever updating, event after the cache time limits. So it is pretty much broke as well.

Not sure how treat this issue... bug report? Calendar issue or views issue?

arlinsandbulte’s picture

arlinsandbulte commented
Status: Active » Postponed (maintainer needs more info)

BUMP
Karen or Anyone else still interested in this?

karens’s picture

karens commented
Status: Postponed (maintainer needs more info) » Active

I think this would still be a good thing if anyone can figure out a way to get it to work. I suspect it will be hard. It is mostly needed with PHP4, PHP5.2 does not push things so hard. I'm going to leave it open in case anyone wants to work on it or in case I stumble across a way to get it working.

nowrap’s picture

nowrap commented

Hello,
i am still interested in this issue. We are running some drupal sites with calendar and repeating events. I checked the site rendering with xdebugs profiling. We have additional processing times between 1 and 5s depending on systemload and the number of repeating events.

We are running on php 5.2.x, latest 2.x-dev versions of date and calendar. Views is 2.11 stable.

Regards
.nowrap

michellezeedru’s picture

michellezeedru commented

Subscribing to this issue. I did turn on caching in the view for calendar (set to 6 hours/6 hours), but found that my database began ballooning exponentially, to the point my sysadmin became concerned. We found it was the cache_views_data that was out of control. I had to disable the calendar caching.

Any suggestions would be helpful.

webwriter’s picture

webwriter commented

Huge issues with this as well. Subscribe.

enkara’s picture

enkara commented

Subscribing

Jānis Bebrītis’s picture

Jānis Bebrītis commented

subscribing

developer-x’s picture

developer-x commented

Another approach is to use the boost module - I use it to cache the calendar pages. You can modify the settings to define how long a page is cache. This might actually be preferable considering you can use boost across all pages - not just calendar.

paulgemini’s picture

paulgemini commented

subscribing

cossimo’s picture

cossimo commented

Subscribing

Yorgg’s picture

Yorgg commented

I have hundreds of items and 20 minutes is not enough to open up the monthly view.
I have APC, memcache and varnish running. I can't even warm up the cache.
Any suggestion?

joshbudda’s picture

joshbudda commented
Issue summary: View changes

Subscribing

k_a_l’s picture

k_a_l commented

subscribing

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Closed (outdated)

I am closing this issue, since it's for a Drupal version no longer supported.