CAPACITY PLANNING BY TRANSACTION TYPE
First Claim
1. A computer implemented method for monitoring a transaction, comprising:
- performing a plurality of transactions by an application using one or more resources;
determining a first usage of each of the one or more resources by each of the plurality of transactions; and
associating a second usage of each of the one or more resources with one or more of the plurality of transactions, the second usage associated with a non-transaction specific usage of the resource.
2 Assignments
0 Petitions
Accused Products
Abstract
Capacity planning is performed based on expected transaction load and the resource utilization for each expected transaction. Resource usage is determined for one or more transactions or URLs based on transaction specific and non-transaction specific resource usage. Once the resource usage for each transaction is known, the expected resource usage may be determined for an expected quantity of each transaction. The actual resources needed to meet the expected resource usage are then determined. Resources may include hardware or software, such as a central processing unit, memory, hard disk bandwidth, network bandwidth, and other computing system components. The expected resource usage for a transaction may based on the usage directly related to the transaction and usage not directly related to the transaction but part of a process associated with the performed transactions.
75 Citations
40 Claims
-
1. A computer implemented method for monitoring a transaction, comprising:
-
performing a plurality of transactions by an application using one or more resources; determining a first usage of each of the one or more resources by each of the plurality of transactions; and associating a second usage of each of the one or more resources with one or more of the plurality of transactions, the second usage associated with a non-transaction specific usage of the resource. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors to perform a method comprising:
-
receiving a request to perform a transaction; associating the request with a thread; performing the transaction by the thread, wherein performance of the transaction utilizes one or more computer components; and determining the utilization of each of the one or more computer components by the thread while performing the transaction, wherein the utilization includes computer component usage directly resulting from the transaction and computer component usage that is not a direct result of the transaction. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
-
25. A computer implemented method for monitoring a transaction, comprising:
-
performing a transaction by a system using one or more resources; receiving application runtime data regarding the one or more resources; determining an amount of each of the one or more resources used to perform the transaction using the application runtime data, wherein the amount of each resource is determined from transaction-specific application runtime data and non-transaction specific data; and determining the number of resources needed to meet an expected capacity based on the amount of each of the one or more resources used to perform the transaction. - View Dependent Claims (26, 27, 28, 29, 30)
-
-
31. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors to perform a method comprising:
-
receiving requests to perform two or more transactions; performing the transactions in response to the requests using one or more resources; and determining a first usage level of each of the one or more resources for a first transaction of the two or more transactions; and determining a second usage level for the one or more resources to attribute to the first transaction, the second usage level not directly associated with the first transaction. - View Dependent Claims (32, 33, 34, 35, 36, 37)
-
-
38. An apparatus for processing data, comprising:
-
a communication interface; a storage device; a hard disk; and one or more processors in communication with said storage device, hard disk and said communication interface, said one or more processors perform transactions and determine a usage level of each of the storage device, hard disk and one or more processors for each of the transactions, the usage level incorporating transaction specific and non-transaction specific resource usage. - View Dependent Claims (39, 40)
-
Specification