Trigger on asset accessed - costly?

Squiz Matrix Support
1

Hi all,


have seen a few cool things going on on these forums that rely on the "Asset Accessed" trigger - ie run this trigger when an asset is accessed by the user.



I have thought of some useful things that we could do with this functionality, possibly setting up a few of these triggers.



We have a fairly large website with a lot of assets (over 220,000 and climbing) and I am concerned that if I make too many of these it may slow up the time it takes to serve the page ie if the system has to check 5 "Asset Accessed" triggers before serving up the page to the user that might slow things up or put a fair bit of load on the system during peak times.



Any ideas on whether those concerns are valid?



Thanks,



Steve

2

Yes, it is certainly more processing to do each time a page is served. Try not to use Asset Accessed if you can help it, or at least add them one-by-one and give yourself some time to analyze performance to see if it is degrading.

3

Also, when creating your triggers, keep in mind that Matrix evaluates the conditions in order, so you want the most restrictive before the least. This will ensure that Matrix stops processing the trigger as soon as possible.