Browse Prior Art Database

Tracking and Analyzing Performance by Configuring Performance Limits in debug environment

IP.com Disclosure Number: IPCOM000202414D
Publication Date: 2010-Dec-15
Document File: 3 page(s) / 78K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for tracking, configuring, and managing performance parameters during code development of an application is disclosed. The method facilitates a developer to monitor and set performance measures like memory usage and time consumed at a method level of an application during code development in a debug environment.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

Tracking and Analyzing Performance by Configuring Performance Limits in debug environment

Typically, an application or a product may have certain guidelines. The guidelines describe the correlation between user operations and performance parameters. For example, an application may have a guideline that specifies that certain user operations should not exceed a predefined time limit. For example, operations such as opening a file should not take more than 1000 millisecond (ms) or expanding a tree node should not exceed 500 ms. In the same manner, certain operations may have guidelines with respect to different performance parameters such as, a permissible memory usage limit.

Disclosed is a method and system for tracking, configuring, and managing performance parameters during code development of an application or a product. A performance control view is provided to a developer of the application or the product in a debug environment. In the debug environment, the developer can set the performance measures such as, time and memory at a method level that is allowed by guidelines of the application or the product. As a result, the developer will be able to monitor the memory usage and time consumed by the methods defined by the developer during development. The developer may also tune the implementation during development. In a scenario, where it is not possible to tune the implementation, the developer may inform a performance team beforehand that the implementation may require more resources or time.

Thus, the developer is allowed to configure these permissible values at a critical method level and thereafter perform integration with the debug environment. In scenarios, where the limits are exceeded, customized exceptions can be thrown/caught and logged in the debug environment and subsequently shown to the developer during testing of the methods. As a result, when such an exception arises, the developer can analyze or tune the method. Alternatively, the developer may also raise the limits for that method after discussing the requirement for raising the limits with the performance team of the developer.

An exemplary "performance control view" in a developer environment as described by the method and system is shown in fig. 1. As illustrated in fig. 1, the developer can define one or more "Performance Tracking Points" (PTP) for met...