Application performance pages

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Application performance pages

    Application performance pages provide ServiceNow customers with detailed insights into the efficiency and resource usage of specific applications. These pages enable you to evaluate performance metrics, identify bottlenecks, and make informed decisions to optimize application behavior and enhance user experience.

    Show full answer Show less

    Key Features

    • Timeframe Selection: Analyze application data within a defined period, up to the current date and time, with a maximum span of 7 days.
    • Device — Installed Application Performance: Monitor key metrics including memory usage (in MB) and CPU usage (in percentage) for the top 10 applications, helping to pinpoint resource-intensive apps.
    • Application Performance Tab: Examine CPU and memory usage percentages along with I/O read and write operations to identify performance constraints. High CPU or memory usage may lead to degraded application responsiveness and potential crashes, while excessive I/O operations can cause latency and slow system responses.
    • Crash Trends: Track application crash occurrences over the last 2 hours to detect reliability issues and proactively improve stability.
    • Device — Web Application Performance: Assess web-specific metrics such as response time (in milliseconds), DNS lookup duration, page load time, failed web requests, and service availability percentage. These metrics help diagnose issues affecting user access, browsing experience, and overall service uptime.

    Practical Benefits for ServiceNow Customers

    • Quickly evaluate and compare resource consumption by applications to prioritize optimization efforts.
    • Identify and address performance bottlenecks related to CPU, memory, and I/O operations.
    • Monitor application stability through crash trends to maintain high reliability and user satisfaction.
    • Improve web application responsiveness by tracking response times, DNS resolution, and page load metrics.
    • Troubleshoot failed web requests to detect and resolve server errors or network problems affecting end users.
    • Ensure high service availability to maintain consistent access and operational continuity.

    Access performance and usage data for a specific application to evaluate its efficiency, identify bottlenecks, and make informed optimization decisions.

    Device — Installed application performance

    Field Description
    Start date Start date and time within 7 days from current date and time.
    End date End date and time that can’t exceed the current date and time.
    Top memory and CPU usage tab
    Memory usage Amount of memory or RAM (Random Access Memory) consumed by the top 10 applications in MB.
    CPU usage Amount of processing power consumed by the top 10 applications in percentage.
    App performance tab
    CPU usage
    Amount of processing power consumed by an application in percentage.
    Note:
    High CPU usage can result in degraded application performance, slower response times, and decreased user satisfaction. Therefore, identify performance bottlenecks and take proactive steps to optimize application performance.
    Memory usage
    Amount of memory or RAM (Random Access Memory) consumed by an application in percentage.
    Note:
    High memory usage can result in degraded application performance, slower response times, and potentially lead to crashes or system instability. Therefore, monitor memory usage to optimize resource allocation and capacity planning, verifying that applications have sufficient resources to meet user demands.
    I/O read Process of reading data from storage devices, such as hard drives or solid-state drives, within a computer system.
    Note:
    Excessive I/O read operations can lead to performance bottlenecks, increased latency, and result in slower system response times. Therefore, monitor I/O read activities to verify that the data retrieval processes aren't a limiting factor for application performance.
    I/O write Process of storing or writing data to storage devices like hard drives or solid-state drives, within a computer system.
    Note:
    Excessive I/O write operations can also lead to performance bottlenecks, increased latency, and potentially result in slower system response times. Therefore, monitor I/O write activities to verify that data storage processes don't hinder application performance.
    Number of crashes Trend of the application's crashes on the device over the last 2 hours.
    Note:
    Analyzing this graph enables you to identify potential issues, pinpoint trends, and take proactive measures to enhance the application's reliability and user experience.

    To return to the application metrics main page, see Users — Application Performance.

    Device — Web application performance

    Field Description
    Response time Time it takes for the application to respond to a user request in milliseconds.
    Note:
    A slow response time can result in frustrated users, decreased engagement, and lower productivity, while a fast response time can lead to improved user satisfaction and increased engagement. Therefore, it's essential to track response time as a key application metric and continuously monitor and optimize it to promote optimal user experience.
    DNS lookup

    (Only Web applications have this field.)
    Time (in milliseconds) it takes for a user's device to resolve a domain name into an IP address.
    Note:
    If DNS lookup identifies an error in the mapping of DNS entries on the user's system, the user can’t access the internet or the intended website.
    Page load time Time taken for a web page to display its content fully and get interactive on a user's request.
    Failed web requests Instances where requested web content or resources couldn't be successfully retrieved or loaded by the server.
    Note:
    The failed web requests result provides insights into potential issues affecting web performance. It helps in identifying problems such as server errors, broken links, or network issues that could hinder user experience. Identifying the frequency, type, and reasons behind failed requests helps in troubleshooting, optimizing web infrastructure, and promoting a smoother browsing experience for users.
    Availability Percentage of time that a service is operational and accessible to users.