Remote content caching

Squiz Matrix Support
1

I am just about to use the remote content asset, and I have a question.


Is the remote data cached in Matrix, and is it OK to turn this off if it is? I'd presume though that if you are tunneling URLs below the target or using queries that it must not be cached at all.



I want the remote content to always be up to date. I am not worried about the effect of SQUID at this point, as I'll be manually clearing this when the remote content itself is updated. (Or I could clear the Matrix cache too if it is preferred to have the Matrix caching on for the asset.)



Also, from an execution time point of view, what are the best settings for the RC asset. I am generating the remote content on our internal network, so I have complete control. I want the least amount of work done by the asset, for obvious reasons!



cheers

Richard

2

The Remote Content is not cached by Matrix – and for performance, the less work the RC asset has to do, the faster it'll display, so try not to require any transformations.

3

Speed of remote content asset processing depends mostly on how many URLs there are on the page and the size of the page.

4

Thanks guys.


I'll be pre-baking the content so that it fits right into our design so that'll minimise the size. (i.e. no HTML head or footer).



So I'll also now avoid anything that would have required a transformation, and pre-bake the URLs too…





cheers,

Richard

5

[quote]So I’ll also now avoid anything that would have required a transformation, and pre-bake the URLs too…
[right][post=“15218”]<{POST_SNAPBACK}>[/post][/right][/quote]



Matrix has to transform the URLs anyway to maintain the Remote Content connection. Just try to keep the number of URLs as low as possible.

6

There might not be much benefit in over-optimizing the pages for Remote Content Asset (RCA) consumption. The time it takes to fetch the remote page will most likely be the determinant of speed with which RCA can serve content. Rewriting URLs is not much different than providing keyword replacements in other assets and will only be noticeable if there are thousands of URLs. If you're talking tens or hundreds of URLs, then there's no need to optimize the count.

7

[quote]There might not be much benefit in over-optimizing the pages for Remote Content Asset (RCA) consumption. The time it takes to fetch the remote page will most likely be the determinant of speed with which RCA can serve content. Rewriting URLs is not much different than providing keyword replacements in other assets and will only be noticeable if there are thousands of URLs. If you’re talking tens or hundreds of URLs, then there’s no need to optimize the count.
[right][post=“15235”]<{POST_SNAPBACK}>[/post][/right][/quote]



Thanks Andrei. The remote content is coming in over a 1 gig local connection - just a switch and a cat 5 cable. I wish my home broadband was that fast.



I’ll still take any benefits I can though in the RCA though…