활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.
활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.
I've been building a CQ page with a few teasers on it and I noticed that there seems to be a dramatic and noticeable slowdown whenever I scroll the page. I then tried it out on Geometrixx and I'm seeing the same thing. Chrome's javascript profiler revealed that scrolling around the page used up to 17% of my CPU is being used to process "CQ_Analytics.SegmentMgr.resolve", which appears to be triggering whenever a teaser is scrolled into view.
This is really heinous, and it is happening on the Geometrixx site so I don't believe it's something I've done. Has anybody figured out how to fix this or optimize around it?
I've restarted Chrome since I suspected there might be a leak that was consuming resources. It did not seem to matter, and on Firefox the problems are even more severe, essentially hanging the webpage for a few seconds as you scroll. Again, it comes to the same calls to CQ_Analytics.SegmentMgr.resolve().
I'm seeing all this in preview mode on AEM 5.6.0.
해결되었습니다! 솔루션으로 이동.
It looks like we just unbound all "mousemove" events from the $CQ copy of jQuery.
조회 수
답글
좋아요 수
This sounds like something we saw in v5.4. There's JS in the segmentation framework that tracks your mouse position for segmentation purposes. I can't remember for sure, but I think we ended up using our own JS to remove the event listener for mouse move that CQ had created.
I have never come across this. Can you file daycare with details
조회 수
답글
좋아요 수
That sounds like what might be happening! Can you think of a good way to find these listeners so I can remove them? I'm not sure how I'd do that.
조회 수
답글
좋아요 수
Sham HC wrote...
I have never come across this. Can you file daycare with details
You can just look at the Geometrixx site to see it happening.
조회 수
답글
좋아요 수
It looks like we just unbound all "mousemove" events from the $CQ copy of jQuery.
조회 수
답글
좋아요 수