Notifications

125 views

Description

This document provides information on how to address performance issues where user home pages are on an automatic refresh schedule and impacting performance.

We have identified that the home.do page is constantly refreshed by multiple users and is causing performance issues. This is related to poorly formatted homepages and the root cause should be addressed. For more information, see Customize Homepages in the product documentation.

How to find the issue

The transaction logs show a high quantity and possibly long-running home.do, navpage.do, and navigator.do transactions that appear in intervals of 5, 10, 30 or 60 minutes for the same user or users. This is verified by navigating to user preferences, searching where name = home_refresh, and observing a high number of users that have a value set to anything other than off (for example, 300, 600, 1800, or 3600).

What is the impact?

When the user is logged in and has their homepage in focus, the user preference home_refresh automatically reloads the homepage based on the value set in the drop-down list. This causes the following:

  • The user has a poorly formatted homepage that takes more than XX seconds to load. Every time the system automatically reloads the homepage, it puts additional load on the system resources and causes performance degradation.
  • The user is never logged out by the session timeout because the session is never inactive long enough to trigger the session timeout as long as the home page is loaded in the browser. This can also be a security risk as the session is never timed out and the connection to the instance remains persistent.

Resolution

  • Disable homepage refresh for all users (or those who do not need the refresh).
  • Set all values that are not currently off in the user_preferences to off in order to stop the auto-refresh (for those who do not need the refresh).

Note: The user may have a valid business need for select users to have an auto-refreshed homepage. There are instructions below on how to accomplish this outside of the framed instance.

 

  • If you have a need for some users to have this value, set that user_preference to the desired value for the specific user within the instance.
    1. Set the system property glide.home.refresh_disabled to true. This removes the drop-down menu time selection.
      • /sys_properties_list.do?sysparm_query=nameLIKErefresh_disabled
    2. Set necessary users with home_refresh values to off. Navigate to the URL:
      • /sys_user_preference_list.do?sysparm_query=GOTOname%3Dhome_refresh
    3. Right-click the header bar (colored area next to value) and select Update All.
    4. Click OK.
    5. Set the Value section to off.
    6. Click Update.
    7. Locate the approved user(s) and set the desired home_refresh value. For example, 300, 600, 1800, or 3600.

How to get the homepage refresh outside of frames if needed

Note: This has been tested and verified to work with Chrome. Other browsers may have similar features but were not tested.
  1. Locate the homepage required to refresh often and capture sys_id.
  2. Navigate to /sys_portal_page_list.do.
    If you cannot get to the portal page, go to the homepage and right-click on the Switch to page drop-down menu and select inspect element. Expand out the page_selector and locate the sys_id of the page needed.
    • Example: <option value="776fca35210151005c9a14efc29c0aa5">Change Management Dashboard - Customer Support</option>
  3. Find the homepage required for refresh (for example, "System Diagnostics") right-click the name and select Copy sys_id.
  4. Place the sys_id of the homepage needed into this URL:
    • /home.do?sysparm_userpref_homepage={home_page_sys_id}
  5. Install any browser extension that manages automatic tab refreshing (for example, Easy Auto Refresh for Chrome) and set the time in seconds to refresh the page.

Article Information

Last Updated:2019-09-10 03:57:52
Published:2019-09-10