Mining Execution Pattern For System Performance Diagnostics

• US 20130173777A1
• Filed: 12/28/2011
• Published: 07/04/2013
• Est. Priority Date: 12/28/2011
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Fu, Qiang, Lou, Jianguang, Lin, Qingwei, Zhang, Dongmei, Ding, Rui
• Application Number:
  US13/338,530
• Publication Number:
  US 20130173777A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3452 Performance evaluation by statistical analysis
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

This application describes a system and method for diagnosing performance problems on a computing device or a network of computing devices. The application describes identifying common execution patterns between a plurality of execution paths being executed by a computing device or by a plurality of computing device over a network. The common execution pattern being based in part on common operations being performed by the execution paths, the commonality being independent of timing of the operations or the sequencing of the operations and individual executions paths can belong to one or more common execution patterns. Using lattice graph theory, relationships between the common execution patterns can be identified and used to diagnose performance problems on the computing device(s).

Claims

1. A system comprising:

a processor that executes a plurality of execution paths comprised of a plurality of operations;

a memory that stores the execution paths; and

a common path component stored in memory that assigns execution paths to one or more common execution nodes based in part on a type of operations that are common between the execution paths.

2. The system of claim 1, wherein the execution paths comprise requests or transactions being executed on a plurality of modules on the system or a network that is in communication with the system.

3. The system of claim 2, wherein two or more of the execution paths are assigned to two or more common execution nodes.

4. The system of claim 1, further comprising:

a grouping component stored in memory that defines a plurality of relationships between the common execution nodes based in part on the type of operations common between the common execution nodes.

5. The system of claim 4, wherein the plurality of relationships is defined on a hierarchy in which a common execution node with the largest amount of execution paths is at the top of the hierarchy and one or more common execution nodes with the least amount of execution paths are at the bottom of the hierarchy.

6. The system of claim 4, wherein the plurality of relationships is defined on a hierarchy in which a common execution node with the least amount of common operations is at the top of the hierarchy and one or more common execution nodes with the greatest amount of common operations are at the bottom of the hierarchy.

7. The system of claim 6, wherein the grouping component defines one or more common execution nodes to be connected to the top common execution node in the hierarchy based in part on the one or more common execution nodes sharing a plurality of common operations and one operation that is not associated with the top common execution node.

8. The system of claim 6, wherein the grouping component defines one or more common execution nodes to be connected to the top common execution node in the hierarchy based in part on the one or more common execution nodes sharing a plurality of common operations and two operations that are not associated with the top common execution node.

9. A method comprising:

receiving a plurality of execution patterns at a computing device and storing the execution patterns in memory, the execution patterns comprising a sequence of operations that have been performed by modules on the computing device or other devices on a network;

grouping the execution patterns into one or more common execution nodes based in part the execution patterns that include a common string of operations

forming a lattice graph that comprises common execution nodes being linked to each other based in part on an amount of operations within the common execution nodes that are common to each other.

10. The method of claim 9, wherein the forming of the lattice graph further comprises:

selecting a top common execution node from the common execution nodes based in part on one of the common execution nodes comprising the least amount of operations;

linking one or more common execution nodes to the top node based on the common execution nodes having a minimum amount of difference an amount of operations or types of operations in the top node and the common execution nodes, the linking of the one or more common execution nodes being a first plurality of nodes; and

linking one or more nodes of the common execution nodes to the one or more nodes of the first plurality of nodes based in part on the common execution nodes having a minimum amount of difference in an amount of operations or types of operations between the one or more first plurality of nodes and the common execution nodes, the nodes being linked to the first plurality of nodes being a second plurality of nodes.

11. The method of claim 10, further comprising:

linking another common execution node to one or more of the first plurality of common execution nodes or the one or more of the second plurality of common execution nodes based in part on the other common execution node comprising a plurality of operations that are similar to the operations in the first or second plurality of nodes.

12. The method of claim 9, wherein the receiving of execution patterns comprises extracting request level event traces from the computing device or the devices on the network.

13. The method of claim 9, wherein the receiving of execution patterns comprises extracting transaction level event traces from the computing device or the devices on the network.

14. The method of claim 9, further comprising evaluating one or more execution patterns to determine a ranking of how much the one or more execution patterns impact the computing device or the network.

15. The method of claim 9, wherein the sequence of operations are determined based in part on a non-temporal characteristic.

16. A method comprising:

determining a number of code paths performed in a network or a computing device that fail to be performed as intended, each code path comprising a plurality of operations being performed on the network or a computing device;

determining a number of code paths performed on the network that are performed as intended;

determining a number of those failed code paths that are classified as a common execution pattern;

determining a number of those failed code paths that are not classified as the common execution pattern; and

calculating a ranking of the share execution pattern, using a processor, based in part on;

the number of code paths performed in the network that fail to be performed as intended;

the number of code paths performed in the network that are performed as intended;

the number of those failed code paths that are classified as the common execution pattern; and

the number of those code paths that were performed as intended and that are not classified as the common execution pattern.

17. The method of claim 16, further comprising:

determining a number of those failed code paths that are classified as another common execution pattern;

determining a number of those failed code paths that are not classified as the other common execution pattern; and

calculate a ranking of the other share execution pattern, using a processor, based in part on;

the number of code paths performed in a network that fail to be performed as intended;

the number of code paths performed in a network that are performed as intended;

the number of those failed code paths that are classified as the other common execution pattern; and

the number of those failed code paths that were performed as intended and that are not classified as the other common execution pattern.

18. The method of claim 16, wherein the calculating the ranking is determined by the following equation:

19. The method of claim 16, wherein the common execution pattern is based in part on types of operations that are common between the execution paths.

20. The method of claim 19, wherein the common execution pattern if further based on non-temporal characteristics of the operations.