Perspectium How to Fix Slow ServiceNow Instances

1
PERSPECTIUM

• How to Fix Slow ServiceNow Instances

2

• Slow ServiceNow instances prevent users from
  working efficiently with the product, and limit
  the data and insight that can be gained from the
  platform.
• Organizations working with ServiceNow are
  encouraged to take steps to prevent performance
  degradation, and tackle it when it arises.
• Since ServiceNow is a platform that serves a
  range of business functions, the effects of a
  slow ServiceNow instance can be and often are
  felt organization-wide.

3
Performance Degradation Spotting the Signs

• A slow ServiceNow instance is a symptom of
  performance degradation on the platform. 
• Generally, when ServiceNow users experience
  performance issues or interrupted access across
  applications, they witness a few common symptoms
• Transactions take longer than expected, affecting
  tasks such as extracting data and creating
  reports.
• Slow and/or unresponsive dashboards
• Unable to connect to an instance. 
• Low or out-of-memory notifications appear.
• Some Java applications drain significant memory
  compared to native applications.
• An application/code consumes increasing system
  memory while running.
• Stats and threads remain accessible, but the user
  interface is not.
• An instance becomes unresponsive to keyboard or
  mouse commands.
• Operations run slower than they did before.
• Slow performance across all or specific
  applications in the instance.
• Slow response time when entering data into
  applications.
• The graphical user interface (GUI) takes longer
  to refresh

4
Slow ServiceNow Instances are Quick to Generate
Technical Debt 

• Since ServiceNow supports a range of business
  functions, a slow ServiceNow instance causes
  problems across the organization. Problems such
  as limited ServiceNow data availability are
  common, as the employees and systems that require
  regular data input face delays in receiving
  ServiceNow data.
• Organizations managing their own ServiceNow
  integrations expend considerable internal
  resources troubleshooting and then addressing the
  issues.
• However, such teams are often already under
  significant pressure and time constraints, making
  them more likely to introduce rushed and
  inefficient solutions that add to technical
  debt over time.