Response time measurement apparatus and method

• US 5,781,449 A
• Filed: 08/10/1995
• Issued: 07/14/1998
• Est. Priority Date: 08/10/1995
• Status: Expired due to Term

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Advanced Systems Technologies, Inc. (Broadcom, Inc.)
• Inventors: Rosborough, James M.
• Primary Examiner(s): BURGESS, GLENTON B
• Application Number:
  US08/513,435
• Time in Patent Office: 1,069 Days
• Field of Search: 364/514 R, 364/551.01, 364/514 B, 364/550, 375/356, 395/500, 395/200.11, 395/183.02, 395/185.07, 380/21, 380/25
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3452 Performance evaluation by statistical analysis
• CPC Class Codes: G06F 11/349 for interfaces, buses
• CPC Class Codes: G06F 2201/87 Monitoring of transactions
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/067 using time frame reporting
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/0864 Round trip delays
• CPC Class Codes: H04L 43/12 Network monitoring probes
• CPC Class Codes: H04L 43/50 Testing arrangements
• CPC Class Codes: H04L 47/283 in response to processing delays, e.g. caused by jitter or round trip time [RTT]

Abstract

The present invention provides a method and apparatus for measuring transaction response times. The method and apparatus can identify service request sequences corresponding to a transaction and the start and stop times for the transaction. The invention can be applied non-intrusively/non-invasively to the service packets communicated between a source and destination node.

Claims

1. A method for identifying one or more occurrences of a transaction included in a plurality of service packets communicated between a first node and one or more second nodes, comprising:

providing a communications data set including information relating to an ordering of a collection of said service packets, wherein said service packets are communicated on a communications line between the first node and the one or more second nodes;

forming a pattern characterization data set using data related to a grousing of at least some of the plurality of service packets corresponding to an occurrence of the transaction; and

comparing said communications data set with the pattern characterization data set to determine whether at least some of the collection of said plurality of service packets correspond to an occurrence of said transaction.

2. The method as claimed in claim 1, wherein said providing step comprises:

detecting with a probe, said service packets from said communications line;

determining, for each of said service packets, a corresponding received time when the service packet is detected by said probe; and

recording an identity of each of said service packets and said corresponding received time.

3. The method as claimed in claim 2, further comprising:

adding to said corresponding received time for a service packet, a transit time corresponding substantially to the time required by a service packet to travel from said probe to at least one of said first node and one of said one or more second nodes.

4. The method as claimed in claim 1, wherein a majority of said service packets each has at least one of a corresponding node address and a corresponding port number and said communications data set includes for each of said service packets, a corresponding received time when the service packet is detected on said communication line, and said providing step comprises:

reading with a probe each of said service packets from said communications line for detecting the service packet;

filtering said service packets, read by said probe, based on at least one of node address and port number to form a selected set of service packets; and

recording for each service packet in said selected set of service packets, said corresponding received time.

5. The method as claimed in claim 1, wherein said service packets correspond to a plurality of threads with each thread corresponding to thread identification information and said comparing step comprises:

sorting said service packets in said communications data set into a plurality of thread data sets wherein the service packets in each thread data set have the same thread identification information.

6. The method as claimed in claim 1, wherein said service packets include service request packets and service results packets, each said service request corresponds to a service request from the first node of one of said one or more second nodes, and said comparing step comprises:

identifying said service request packets in said service packets using contents of said service packets.

7. The method as claimed in claim 1, wherein said service packets of said collection includes service request packets and service results packets and said providing step comprises:

identifying said service request packets in said collection using contents of said service packets in said collection;

correlating, each service results packet of said collection of service results packets, with a corresponding one of said service request packets; and

determining a corresponding start and a corresponding stop time for each of the corresponding service requests, wherein the information relating to an ordering of the collection of service packets comprises at least one of the start time and the stop time for each of the corresponding service requests.

8. The method as claimed in claim 7, further comprising a step of:

computing a response time for said transaction using at least some of said start times and said stop times.

9. The method as claimed in claim 7, wherein the forming step comprises:

comparing the time interval between the stop of a first service request of said plurality of service packets and the start of a second service request of said plurality of service packets with a predetermined value for said time interval to identify a sequence of service requests corresponding to an occurrence of the transaction, wherein said grousing of service packets corresponds to said sequence of service requests.

10. The method as claimed in claim 1, wherein at least some of said service packets in said collection are service request packets for requesting service from the first node to at least one of said one or more second nodes, and, said comparing step comprises:

first matching a first service request packet in said collection with a representation of a service request packet in said pattern characterization data set;

second matching a second service request packet in said collection with another representation of a service request packet in said pattern characterization data set, wherein a time interval between said first and second service request packets is no more than a predetermined value.

11. The method as claimed in claim 1, wherein said service packets of said collection correspond to a plurality of service requests from the first node to one of said one or more second nodes, said service requests correspond to a plurality of thread data sets, and said comparing step comprises:

first matching a first service request corresponding to a first thread with a representation of a service request packet in said pattern characterization data set;

second matching a second service request corresponding to a second thread with another representation of a service request in said pattern characterization data set, wherein a time interval between said first and second service requests is no more than a predetermined value.

12. The method as claimed in claim 1, wherein said collection is substantially identical to said plurality of service packets.

13. The method as claimed in claim 1, wherein said collection includes said grouping of service packets.

14. The method as claimed in claim 1, wherein said grouping and said collection have substantially different service packets of said plurality of service packets.

15. A non-intrusive system for identifying one or more occurrences of a transaction included in a plurality of service packets communicated between a first node and one or more second nodes, comprising:

means for recording a plurality of service packets communicated on a communications line between the first node and the one or more second nodes, said recording means being in communication with said communications line;

means for forming a pattern characterization data set using data related to a grouping of at least some of the plurality of service packets related to an occurrence of the transaction, the forming means being in communication with the recording means; and

means, in communication with said forming means, for identifying the one or more occurrences of the transaction, corresponding to at least a portion of said plurality of service packets, using the pattern characterization data set.

16. The non-intrusive system as claimed in claim 15, wherein said identifying means comprises means for comparing said plurality of service packets and the order in which said service packets are received by said recording means against the pattern characterization data set.

17. The non-intrusive system as claimed in claim 15, wherein said recording means includes a service packet detecting means for detecting said service packets, said detecting means located on a portion of said communications line between said first node and said one or more second nodes.

18. A method for identifying a transaction corresponding to a plurality of service packets communicated between a first node and one or more second nodes, comprising:

providing a communications data set comprising (i) data identifying each service packet of said plurality of service packets corresponding to a plurality of service requests and (ii) the start and stop times for each service request; and

comparing a time interval between the stop time of a first service request and the start time of a second service request with a predetermined value for said time interval to identify a sequence of said service requests included in the transaction.

19. The method as claimed in claim 18, wherein said predetermined value ranges from about 50 to about 500 milliseconds.

20. The method as claimed in claim 18, wherein a portion of said service packets correspond to a thread and at least two service packets correspond to different threads and said service packets comprise:

(a) a plurality of service request packets, wherein each said service request packet corresponds with a distinct one of said service requests, and (b) a plurality of service result packets, wherein for each said service request packet of a majority of said service result packets, the service result packet is a response to a different one of said service request packets, and said comparing step comprises;

identifying each of said service request packets in said plurality of service packets;

correlating each of said service result packets with the corresponding service request packet for forming a service data subset, wherein said service data subset includes the correlated service request packets and the service result packets; and

sorting said service data subsets by thread to form a plurality of thread data sets with the service packets in said thread data set having the same thread addresses.

21. The method as claimed in claim 18, wherein a plurality of sequences of service requests correspond to a plurality of transactions and said comparing step comprises:

recording each of said sequences of service requests and the number of occurrences of each sequence in a pattern characterization data set.

22. The method as claimed in claim 18, further comprising:

selecting a second predetermined value;

comparing said time interval against said second predetermined value to identify a second sequence of said service requests corresponding to a second transaction; and

recording each occurrence of said second sequence of service requests and the number of occurrences of each of said second sequence in a second communications data set.

23. The method as claimed in claim 22, further comprising:

selecting a third predetermined value based on the relationship between (i) the number of occurrences of said sequence of service requests and said predetermined value and (ii) the number of occurrences of said second sequence of service requests and said second predetermined value.

24. The method as claimed in claim 23, further comprising:

comparing said time interval against said third predetermined value for said time interval to identify a third sequence of said service requests corresponding to a third transaction.

25. The method as claimed in claim 24, further comprising:

comparing said third sequence against said communications data set to determine whether at least a portion of said plurality of service packets correspond to said transaction.

26. The method as claimed in claim 25, further comprising:

computing a response time for said transaction.

27. The method as claimed in claim 18, wherein said comparing step produces a pattern characterization data set having a representation of a plurality of sequences of service requests and further comprising:

second comparing said service requests from said comparing step with said pattern characterization data set to determine if said service requests are contained in said pattern characterization data set.

28. The method as claimed in claim 18, wherein said first service request corresponds to a first thread and said second service request corresponds to a second thread.

29. A non-intrusive system for determining transaction level activity between a first node and one or more second nodes, comprising:

means for recording a plurality of service packets communicated on a communications line between the first node and the one or more second nodes, wherein said service packets relate to a number of transactions and said recording means is in communication with said communications line; and

means for determining said number of transactions in communication with said recording means.

30. The non-intrusive system as claimed in claim 29, wherein said determining means comprises means for comparing said plurality of service packets and the order in which said service packets are received by said recording means against a predetermined ordering of service packets relating to said transaction.

31. The non-intrusive system as claimed in claim 29, wherein at least a portion of said plurality of service packets relates to different service request packets, each service request Packet corresponding to a service request, said recording means provides a first data set including (i) said plurality of service packets and (ii) a start time and a stop time for each service request, and said determining means comprises means for comparing the time interval between the stop time of a first service request and the start time of a second service request against a predetermined value for said time interval to identify a sequence of said service requests corresponding to a transaction.