Method and System for Managing Performance Data

• US 20090157923A1
• Filed: 10/05/2006
• Published: 06/18/2009
• Est. Priority Date: 10/05/2006
• Status: Active Grant

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Puishys, Robert E. JR., Williams, Paul N., Butterworth, Daniel E., Sauer, Wayne C.
• Granted Patent: US 7,962,692 B2
• Time in Patent Office: Days
• US Class Current: 710/104
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3485 for I/O devices
• CPC Class Codes: G06F 12/0802 Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/88 Monitoring involving counting
• CPC Class Codes: G06F 2201/885 Monitoring specific for caches

Abstract

The present invention is directed to a method and system for managing performance data. In accordance with a particular embodiment of the present invention, cache metrics are received. At least one of the cache metrics may be compared with a threshold value. A determination may be made as to whether one or more parameter adjustments are required based upon the comparison.

Claims

1. A method for managing performance data, comprising:

receiving a plurality of cache metrics;

comparing at least one of the plurality of cache metrics with a threshold value; and

determining whether one or more parameter adjustments are required based upon the comparison.

2. The method of claim 1, further comprising:

determining one or more recommended values of the one or more parameter adjustments; and

communicating the one or more recommended values of the one or more parameter adjustments to a user.

3. The method of claim 1, wherein the plurality of cache metrics include a total number of cache attempts metric and further comprising:

determining a cache hit rate percentage using the plurality of cache metrics.

4. The method of claim 1, wherein the plurality of cache metrics include an available cache memory metric and an available system memory metric, and further comprising:

determining a sufficient amount of available system memory using the plurality of cache metrics.

5. The method of claim 1, wherein the plurality of cache metrics include a cache misses metric and further comprising:

determining a plurality of cache misses with a particular request size using the plurality of cache metrics.

6. The method of claim 5, wherein the particular request size is between 33 and 64 disk blocks.

7. The method of claim 5, wherein the particular request size is between 65 and 127 disk blocks.

8. The method of claim 5, wherein the particular request size is between 128 and 255 disk blocks.

9. The method of claim 5, wherein the particular request size is greater than 255 disk blocks.

10. The method of claim 1, wherein the plurality of cache metrics include a cache operational metric and further comprising:

determining whether a cache is enabled using the plurality of cache metrics.

11. A method for managing performance data, comprising:

receiving a plurality of system generation parameters;

comparing at least one of the plurality of system generation parameters with a threshold value; and

determining whether one or more parameter adjustments are required based upon the comparison.

12. The method of claim 11, wherein the plurality of system generation parameters include a system generation parameter for loadable images and further comprising:

determining whether unused memory that was reserved for the use of a plurality of loadable images was released.

13. The method of claim 11, wherein the plurality of system generation parameters include a system generation parameter for threads and further comprising:

determining whether scheduling of a plurality of threads within a plurality of processes running a plurality of multi-threaded applications is hampered by not being allowed to use a plurality of available CPUs.

14. A system for managing performance data, comprising:

a processor;

an interface operable to receive a plurality of cache metrics; and

a storage device embodying a program of instructions operable, when executed on the processor, to;

compare at least one of the plurality of cache metrics with a threshold value; and

determine whether one or more parameter adjustments are required based upon the comparison.

15. The system of claim 14, wherein the program of instructions is further operable to:

determine one or more recommended values of the one or more parameter adjustments; and

communicate the one or more recommended values of the one or more parameter adjustments to a user.

16. A system for managing performance data, comprising:

a processor;

an interface operable to receive a plurality of system generation parameters; and

a storage device embodying a program of instructions operable, when executed on the processor, to;

compare at least one of the plurality of system generation parameters with a threshold value; and

determine whether one or more parameter adjustments are required based upon the comparison.

17. The system of claim 16, wherein the program of instructions is further operable to:

determine one or more recommended values of the one or more parameter adjustments; and

communicate the one or more recommended values of the one or more parameter adjustments to a user.

18. Logic encoded in media, the logic being operable, when executed on a processor, to:

compare at least one of the plurality of cache metrics with a threshold value; and

determine whether one or more parameter adjustments are required based upon the comparison.

19. The logic of claim 18, wherein the logic is further operable to:

determine one or more recommended values of the one or more parameter adjustments; and

communicate the one or more recommended values of the one or more parameter adjustments to a user.

20. Logic encoded in media, the logic being operable, when executed on a processor, to:

compare at least one of the plurality of system generation parameters with a threshold value; and

determine whether one or more parameter adjustments are required based upon the comparison.

21. The logic of claim 20, wherein the logic is further operable to:

determine one or more recommended values of the one or more parameter adjustments; and

communicate the one or more recommended values of the one or more parameter adjustments to a user.