pageinfo.json is taking time to load | Community
Skip to main content
M
maruthid1
Level 2
October 16, 2015
Solved

pageinfo.json is taking time to load

  • October 16, 2015
  • 13 replies
  • 6756 views

Hi All.

I am facing one issue related to page load when I looked at the network logs it is pageinfo.json which is taking more than 15 sec to load. It is badly impacting page and workflow package load. Is there any way to tackle this issue. I am using AEM 6.0 SP2, oak 1.0.12. Are there any indexes we need to create for this? We have less than 100 groups and users. All are OOTB workflows only two custom workflows.

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 joerghoh

Hi,

I cannot say, what the problem is, the threaddump does not indicate the number of calls to MongoDB. If course latency is an issue (always). Maybe you can check the number of requests in mongodb.

Jörg

13 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 16, 2015

Hi,

can you share the details of such a request as show by the "recent requests" screen in the OSGI console (/system/console/requests)? It will give some more insights, where the problem can originate from.

Thanks,
Jörg

A
Anonymous
October 16, 2015

Hi Jorg,

Here is the paginfo.json request stats

[img]Screen Shot 2015-05-07 at 9.20.08 AM.png[/img]

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 16, 2015

Hi,

so it's not a filter, but the PageInfoServlet. Then there might be a number of things, which can cause the observed behaviour:

  • full replication queues (you should observe it then as well when browsing in the siteadmin, as it's getting really slow)
  • you are working a lot with MSM
  • lot of running workflows or workflow models

Can you do a number of threaddumps, when this request is running, and post only the relevant pieces of the stacktrace?

kind regards,
Jörg

A
Anonymous
October 16, 2015

Thanks Jorg.

You are spot on. We are doing all the 3 activities as you mentioned. I am trying to take threaddumps from /system/console/status-Threads . Is this correct? or Can you please suggest .

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 16, 2015

Hi,

that's one option. The other one is a regular threaddump, see [1] for some recommendations.

kind regards,
Jörg

[1] https://helpx.adobe.com/experience-manager/kb/TakeThreadDump.html

A
Anonymous
October 16, 2015

Hi Jorg,

Threaddumps attached. Please rename it to .zip

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 16, 2015

Hi,

looks like the time is spent on mongodb... I don't know if there are lots of calls or a very slow single call.

kind regards,
Jörg

A
Anonymous
October 16, 2015

Hi Jorg,

Yah I tried with out mongo it seems relatively better. Is it because of the Process time it is taking in Mongo (If this is the case I can try by increasing Mongo specs)? or is it some network issue between mongo and AEM?

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

I cannot say, what the problem is, the threaddump does not indicate the number of calls to MongoDB. If course latency is an issue (always). Maybe you can check the number of requests in mongodb.

Jörg

tc94524330
tc94524330
Level 3
October 9, 2017

Hi,

I know this thread is old. I can reproduce the same issue in 6.2 SP1. Did you got a solution for this? For us it is taking 18sec for the page info request.

Thanks

Show more replies
Terms & ConditionsAccessibility statement

Loading footer...