Data recording; improving runtime performance

Administer > Dynamic caching > Improve marketing performance using caching

Data recording; improving runtime performance

Two options are provided which can improve runtime performance with regard to the recording of user behavior data.

Record user behavior data

An option that stores the data in cache but does not persist that data to the database. This is the default behavior for the recently viewed categories and products, but can be configured for any user behavior data recording.

An option to set the maximum size of user behavior data stored in cache before that data is persisted to the database.

For more information, see Marketing component configuration file (wc-admin-component.xml).

Areas for performance consideration

Area Performance consideration
Activity and behavior rules All information related to the processing of an activity during the storefront are put into the marketing cache including the definition of the behavior rules that need to match against URLs and controller commands.
Record of user data Performed in batch mode. Only once there is an activity is the data related to that activity is recorded. For example, only once a target has a behavior rule that requires a customer to have browsed the Furniture category five times is the customers browsing Furniture recorded. The browsing of other categories is not recorded in this instance.
Optional recording of user data For high amounts of data. For example, for a recently browsed list, the data will not be recorded in the database.
Detecting events For controller commands, the command execution trigger functionality is used. The command execution trigger is only enabled once a rule is set up that is interested in the successful exit of that controller command. For behavior rules, all the rule definitions are in the marketing cache.
Access user data A customer's online behavior user data will be in a user data cache. While a customer is browsing the site, any accesses to their user data will be from the cache avoiding any database access.
Customer is in Segment trigger Process time of large dialog activities can be configured to run off peak. Segment evaluation can be expensive and result in many customers being run through a dialog activity.
Aggregate statistics Views, clicks, and customers reach an element are accumulated in memory and are periodically persisted to the database avoiding a database write on every page visit.

Related concepts

Command caching for marketing
Marketing business object cache overview

Related tasks

Set up command caching for marketing
Tune the marketing business object cache
Enable JSP caching

Related reference

Commands and methods for generating a cache key

+
Search Tips | Advanced Search

Area	Performance consideration
Activity and behavior rules	All information related to the processing of an activity during the storefront are put into the marketing cache including the definition of the behavior rules that need to match against URLs and controller commands.
Record of user data	Performed in batch mode. Only once there is an activity is the data related to that activity is recorded. For example, only once a target has a behavior rule that requires a customer to have browsed the Furniture category five times is the customers browsing Furniture recorded. The browsing of other categories is not recorded in this instance.
Optional recording of user data	For high amounts of data. For example, for a recently browsed list, the data will not be recorded in the database.
Detecting events	For controller commands, the command execution trigger functionality is used. The command execution trigger is only enabled once a rule is set up that is interested in the successful exit of that controller command. For behavior rules, all the rule definitions are in the marketing cache.
Access user data	A customer's online behavior user data will be in a user data cache. While a customer is browsing the site, any accesses to their user data will be from the cache avoiding any database access.
Customer is in Segment trigger	Process time of large dialog activities can be configured to run off peak. Segment evaluation can be expensive and result in many customers being run through a dialog activity.
Aggregate statistics	Views, clicks, and customers reach an element are accumulated in memory and are periodically persisted to the database avoiding a database write on every page visit.