Performance Improvement | Personalization & Segmentation calls - slowness | Community
Skip to main content
R
rohitspathak123
New Participant
January 26, 2016
Solved

Performance Improvement | Personalization & Segmentation calls - slowness

  • January 26, 2016
  • 1 reply
  • 727 views

Hi all,

 
This is related to performance testing. We are using AEM teaser / campaigns / segmentation for personalization. 
 
Refer to below AEM JS
/libs/resources/clientlibs/foundation/personalization/kernel.min.js
 
Below method call consumed most of time (and caused slowness)
 
1) CQ_Analytics.ProfileDataMgr.prototype.init=function(){this.persistence=new CQ_Analytics.SessionPersistence({container:"ClientContext"});
 
2) var j=function(){var v=new Array();
if(CQ_Analytics.SegmentMgr){var t=0; for(var r=0; r<b.length; r++){if(!b[r]["segments"]||b[r]["segments"].length==0||CQ_Analytics.SegmentMgr.resolveArray(b[r]["segments"])===true){var o=CQ_Analytics.SegmentMgr.getMaxBoost(b[r]["segments"]); if(o==t){v.push(b[r]) }else{if(o>t){v=new Array(); v.push(b[r]); t=o
 
 
Just wondering if anyone has noticed same behavior (slowness) . If yes what can be possible resolution for same ?

 

Thanks in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Lokesh_Shivalingaiah

So how many segments do you have to resolve ? and what are the conditions that each segments has ?

Mostly, campaigns always will take a little time as it is resolved from the browser (JS) after the page has been rendered.

1 reply

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
New Participant
January 26, 2016

So how many segments do you have to resolve ? and what are the conditions that each segments has ?

Mostly, campaigns always will take a little time as it is resolved from the browser (JS) after the page has been rendered.

Terms & ConditionsAccessibility statement

Loading footer...