The Now Platform® Washington DC release is live. Watch now!
In my last blog post 5 Ways to Troubleshoot your Instance Performance I have shared a few tips which enable administrators to diagnose performance issues. As a performance expert, homepage performance is one of the most commonly diagnosed problem areas we assist customers with. Heavy home pages can lead to overall instance performance degradation.
Inefficient homepages lead to poor end user experiences e.g:
- Slower logins
- Poorer instance performance at peak login times
- Poor performance on form submission (where redirect to home.do occurs)
- Homepage auto-refresh functionality (https://docs.servicenow.com/use/homepages/reference/r_RefreshTheHomepage.html) can compound the problem where inefficient home pages are concerned
While designing home pages, ask yourself which information do you need to rendered as a part of home page loading and which one is not?
Hefty home pages can result in slow load times, which may lead you to think there's something wrong with your overall instance. Administrators can review the transaction logs and look for URL starts with "/home.do" and check through the response times. Sort the response times z > a and look for the usernames with highest response time.
This will help to pinpoint the users with heavy home pages. If the response times of multiple "home.do" transactions is high ( > 8-10 seconds), that could be impacting the overall instance and causing a load on the database as well.
A dashboard should be designed with gauges that show focussed and pertinent items of data that should invite a user to drill down further if needed.
2. As an admin user, make use of debug options by enabling "Debug home page rendering."
3. Avoid frequent homepage refresh.
4. Make use of multi threaded homepage rendering, see Parallel Homepage Rendering Explained for more details.
5. Design and set a default system homepage preference so that users who haven't selected a specific home page will land on a lightweight default homepage.
6. Always report on current (active=1) data - gauges that show trending on historical or inactive data should be moved to "Reports" wherever possible
7. Think carefully about allowing non-admin users to create their own custom home pages - if this is allowed ensure users have a good understanding on how to design good home pages
8. Do not put slow gauges on the same page as fast gauges - defeats advantage of multi-threading which the platform supports
For additional information on homepage performance see:
Change the parameter for parallel homepage rendering
Configure homepage cache properties
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.