• Resolved wp booster

    (@jlasiter)


    Even limiting to 90 days and a small number of events, the plugin is very slow. It’s not going to be useable waiting this long for a page to generate. Does it fetch all the data every page load?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author room34

    (@room34)

    Hi,

    I’m sorry to hear you’re having performance issues with the plugin. I will say that it does run into issues for calendars that have a very large number of events, especially if they’re a lot of recurring events with no set end date.

    The nature of an ICS feed is that there’s no way to only retrieve part of the feed. That’s the main reason that the plugin caches the feed data (for one hour by default).

    The plugin does limit the scope of the data it parses to events that are within the designated date range, but recurring events definitely slow things down because they’re not passed in the feed as individual events, so the plugin (actually, the ics-parser library) has to do all of the date calculations as it’s parsing the feed.

    In some cases, the source calendar has options to remove events outside of a certain date range from the feed. You may want to investigate whether there are any of those options in your source calendar software.

    Beyond that, the Pro version has a couple of extra options: one to preload the feed using WP-Cron so it’s less likely to have to parse the feed on an actual page view, and another to let you set how long the cache is stored (i.e. storing it for a day instead of just an hour). Bear in mind that changing the cache duration also will delay the plugin picking up any changes to your calendar, such as newly added events.

    Plugin Author room34

    (@room34)

    Follow-up: This inspired me to revisit the idea I’ve had for a while of giving the free version a way to change the duration of the transient cache, and I came up with something. It should be available momentarily in the version 8.5.5 update.

    Previously the reload property was only designed to support a value of true or 1 which would tell the plugin not to cache the parsed data at all.

    I’ve changed that option to support any integer, representing the number of seconds for the cache. This will override the default value of 3600 if it’s used. So for instance, if you wanted the cache to last for 4 hours, you could add reload="14400" to your shortcode.

    Plugin Author room34

    (@room34)

    Just wrapping this one up. I tried loading your calendar shortcode on a test page and it seems to be loading the calendar pretty quickly. But I am guessing from the fact that the shortcode is displaying directly on the page that you’ve deactivated the plugin. Please consider giving it another try and let me know if you are still seeing performance issues. In the meantime, I will mark this ticket as resolved.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Slow Performance’ is closed to new replies.