Identifying code that wastes time switching tasks

• US 8,806,462 B2
• Filed: 12/11/2011
• Issued: 08/12/2014
• Est. Priority Date: 10/12/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Krauss, Kirk J.
• Primary Examiner(s): DAO, THUY CHAN
• Application Number:
  US13/316,508
• Publication Number:
  US 20120084763A1
• Time in Patent Office: 975 Days
• US Class Current: 717/151
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/88 Monitoring involving counting

Abstract

A method of detecting portions of code of a computer program that protect resources of a computer system unnecessarily can include identifying threads and synchronization objects that are used by a computer program during execution, determining the number of threads that have accessed each resource while it has been consistently protected by a particular synchronization object, and indicating whether the resource is suited for protection according to the number of threads that have accessed the resource.

Claims

1. A method of detecting portions of code of a computer program that protect resources of a computer system, comprising:

identifying a synchronization object engaged by a thread of the computer program;

recording, while the synchronization object is engaged,

each access of a resource, of the computer system, that is protected by the synchronization object and

a thread associated with the access;

determining, upon the synchronization object being disengaged, a number of threads that have accessed the resource while the resource was protected by the synchronization object during execution of the computer program; and

indicating, according to the number of threads, whether the resource is suited for protection.

2. The method of claim 1, wherein said recording includes:

for each resource that is accessed, determining whether state memory has been allocated for the resource; and

upon not, allocating state memory for recording accesses to the resource.

3. The method of claim 2, wherein said allocating includes

apportioning a number of state bits determined according to a number of synchronization objects that have been engaged in the computer program, a number of threads running in the computer program, and a measure of size of the resource.

4. The method of claim 3, wherein said recording includes:

for each access of the resource, setting at least one bit corresponding to a thread responsible for the access and the synchronization object engaged during the access.

5. The method of claim 1, wherein said indicating includes

upon more than one thread has accessed the resource during an execution of the program under test while the synchronization object was engaged, noting that the resource is suitable for protection by that synchronization object.

6. The method of claim 1, wherein said indicating includes

upon a single thread accessed the resource while the synchronization object was engaged, noting that the resource is unsuitable for protection.

7. The method of claim 1, further comprising

storing a call chain leading to a first access of the resource protected by the synchronization object.

8. The method of claim 7, wherein said indicating includes:

counting a number of instances in which the resource is deemed apparently unsuitable for protection; and

upon the number of instances exceeds a predetermined threshold, indicating the call chain.

9. A method of detecting portions of code of a multithreaded computer program that cause task switching within a computer system, comprising:

identifying resources protected by synchronization objects during execution of the multithreaded computer program;

counting instances during execution of the multithreaded computer program in which a resource that is protected by a synchronization object is accessed by only a single thread that engaged the synchronization object; and

indicating that resources accessed by only the single thread that engaged the synchronization object during execution of the multithreaded program are unsuitable for protection by a synchronization object.

10. The method of claim 9, further comprising:

for each resource that is accessed while a synchronization object is engaged for the resource, determining whether state memory has been allocated; and

upon not, allocating state memory for recording accesses to the resource.

11. The method of claim 10, wherein said allocating includes

apportioning a number of state bits determined according to a number of synchronization objects that have been engaged in the multithreaded computer program, a number of threads running in the multithreaded computer program, and a measure of size of the resource.

12. The method of claim 11, wherein said identifying includes

for each access of a memory block, setting at least one bit corresponding to the thread responsible for the access and the synchronization object engaged during the access.

13. The method of claim 9, further comprising

storing a call chain leading to a first access of the resource protected by the synchronization object.

14. The method of claim 13, wherein said indicating includes

upon the number of instances exceeds a predetermined threshold, indicating the call chain.

15. A computer program product comprising computer usable memory having stored therein computer usable program code for detecting portions of code of a computer program that protect resources of a computer system, the computer usable program code which when executed by a computer hardware device, causes the computer hardware device to perform:

identifying resources protected by synchronization objects during execution of the multithreaded computer program;

counting instances during execution of the multithreaded computer program in which a resource that is protected by a synchronization object is accessed by only a single thread that engaged the synchronization object; and

indicating that resources accessed by only the single thread that engaged the synchronization object during execution of the multithreaded program are unsuitable for protection by a synchronization object.

16. The computer program product of claim 15, wherein the computer usable program code further causes the computer hardware device to perform:

for each resource that is accessed while a synchronization object is engaged for the resource, determining whether state memory has been allocated; and

upon not, allocating state memory for recording accesses to the resource.

17. The computer program product of claim 16, wherein said allocating includes

apportioning a number of state bits determined according to a number of synchronization objects that have been engaged in the multithreaded computer program, a number of threads running in the multithreaded computer program, and a measure of size of the resource.

18. The computer program product of claim 17, wherein said identifying includes

for each access of a memory block, setting at least one bit corresponding to the thread responsible for the access and the synchronization object engaged during the access.

19. The computer program product of claim 15, wherein the computer usable program code further causes the computer hardware device to perform

storing a call chain leading to a first access of the resource protected by the synchronization object.

20. The computer program product of claim 15, wherein said indicating includes

upon the number of instances exceeds a predetermined threshold, indicating the call chain.