Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Widget "Relevant for you" is slowing down the performance and loading time of homepage

peter_repan
Tera Guru

Hi all,

after activation of Employee Center Pro plugin and running fix script for Restricted Caller Access, the ec_pro_dashboard page is terrible slow. It takes about 60 second to load the page.

After some investigation, I found that widget "Relevant for you" is the reason why the homepage is loading so slow. 

When I remove the widget, it's super fast to load the page. 

But the widget is out of the box, without any custom changes - and we would like to use the widget. 

Does anybody experienced same behavior and do you have any suggestion how to fix performance of this OOTB widget? 

find_real_file.png

3 REPLIES 3

Community Alums
Not applicable

Hi @peter.repan ,

Auto-refreshing widgets can cause major performance issues. This is usually seen instance-wide in the form of semaphore exhaustion caused by a high number of calls to /sp/rectangle/.

This topic is addressed here: Are your auto-refreshing widgets causing instance slowdowns? Know that there is not really any way to do this without impacting system performance in some way.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

Mark Roethof
Tera Patron
Tera Patron

Hi there,

Haven't experienced this myself. Though if this is a company instance, you could consider opening a Support Case at ServiceNow.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020-2022 ServiceNow Community MVP
2020-2022 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

tomashrobarik
Giga Guru

We had the same issue, but it seems to be fixed within the latest update of employee center (version 25.0.3).