RSS Data Source - caching

Squiz Matrix Support
1

We have a few RSS Data Source assets grabbing news and events from different servers


…but we've had feedback they're hitting those servers pretty hard - 4 times a second!



Can we use the Matrix Cache Manager to slow this down or is there any other way to cache the RSS feeds?



Thanks

2

The RSS Data Source asset should already be using the Cache Manager to cache its results.

3

Thanks Avi.


We don't actually have the Cache Manager switched on so would now like to do so. We're a bit unsure of the settings and what they mean i.e. what is a cache bucket? Should we just go with the defaults?



What does it mean to switch public level, permission level and group level caching on?



Thanks again,

Sarah

4

Yes, use the defaults.

[quote]What does it mean to switch public level, permission level and group level caching on?[/quote]

Public level caching means pages will be cached for users who are not logged in. Permission level is for custom assets and can be ignored. Group level allows logged-in users to get a cache based on what groups they are in.
5

[quote]Yes, use the defaults.
Public level caching means pages will be cached for users who are not logged in. Permission level is for custom assets and can be ignored. Group level allows logged-in users to get a cache based on what groups they are in.[/quote]



Thanks - switched public level caching on and used the defaults and the servers are now happy :slight_smile:

6

Huzzah and Hooray! :D You should now look at Cache Clearing Triggers to keep your authors happier -- now that caching is enabled, it could take up to 24 hours (the default cache timeout) for changes made to assets to appear on the frontend. As an alternative, I sometimes drop the Standard Page cache timeout to something far more acceptable to authors, like 60 minutes. You can do this onthe Cache Manager asset in System Management.
7

[quote]You should now look at Cache Clearing Triggers to keep your authors happier.


As an alternative, I sometimes drop the Standard Page cache timeout to something far more acceptable to authors, like 60 minutes. You can do this onthe Cache Manager asset in System Management.[/quote]



Aha - you read my mind.



The thing is when authors make a change to any page asset they preview immediately, so I don't even think 60min will cut it… and it was only really the RSS Data Source assets we wanted to cache.



I'm not sure which is the best to do:

-create a trigger when an asset is updated to clear the cache (will this still cache RSS?)

OR

-configure page assets in the cache manager to not use the default and switch caching off



Recommendations?

8

Create a trigger that listens for a url condition and that clears the cache for a particular asset (the one fired on). Then create a 'button' in simple edit that allows your authors to fire off the trigger.

9

Hmm... I'm hestitant to introduce an extra step for the authors. Would prefer one of the automated options.
10

If you only have "Public" level caching enabled, logged in users will always see the latest version of the page when Previewing. This doesn't require any modifications to the Cache Manager or any triggers.