METHOD AND SYSTEM FOR PROFILING VIRTUAL APPLICATION RESOURCE UTILIZATION PATTERNS

• US 20120005674A1
• Filed: 09/03/2010
• Published: 01/05/2012
• Est. Priority Date: 07/02/2010
• Status: Active Grant

• Current Assignee: Code Systems Incorporated (VOXX International Corporation)
• Original Assignee: Code Systems Incorporated (VOXX International Corporation)
• Inventors: Larimore, Stefan I., Obata, Kenji C., Zeller, Mark Jeremy
• Granted Patent: US 9,218,359 B2
• Time in Patent Office: Days
• US Class Current: 718/1
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70
• CPC Class Codes: G06F 16/9024 Graphs; Linked lists G06F16/9027 takes precedence
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2212/152 Virtualized environment, e.g. logically partitioned system
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 9/45537 Provision of facilities of other operating environments, e.g. WINE I/O emulation G06F13/105
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: H04L 67/1085 involving dynamic management of active down- or uploading connections

Abstract

A method and system for profiling execution of an application implemented by an application file comprising a plurality of data blocks. The application is executed in response to an execute command from a management process. Read messages are sent to the management process each time the application reads one or more of the plurality of data blocks of the application file. The management process records information about the read operations in one or more transcripts which may be used to create a streaming model for the application allowing the application to be downloaded using a conventional download protocol without using a specialized streaming protocol.

Claims

1. A computer-implemented method performed by a runtime engine, the method comprising:

in response to an execute command from a management process operating independently of the runtime engine but configured to direct at least a portion of the operations of the runtime engine, executing an application implemented by an application file comprising a plurality of data blocks;

monitoring read operations performed by the application on the application file as the application is executing; and

sending a read message to the management process each time the application reads one or more of the plurality of data blocks of the application file.

2. The computer-implemented method of claim 1, wherein monitoring read operations performed by the application as the application is executing comprises:

receiving a thread discriminate value from a thread initiated by execution of the application when the thread performs a read operation on the application file, the read message comprising the thread discriminate value, the thread having been created by a module associated with a module identifier and execution of the thread having been initiated at an offset location within the module, the thread discriminate value identifying the module identifier and an offset value identifying the offset location in the module.

3. The computer-implemented method of claim 2, wherein the module is a Dynamic Link Library file or an executable file.

4. The computer-implemented method of claim 2, wherein monitoring read operations performed by the application as the application is executing comprises:

receiving a pseudo thread identifier from a thread initiated by execution of the application when the thread performs a read operation on the application file, the read message further comprising the pseudo thread identifier.

5. The computer-implemented method of claim 4, wherein the pseudo thread identifier for each thread initiated by execution of the application is determined as a function of the time value and a thread identifier generated by an operating system for the thread when the thread was created.

6. The computer-implemented method of claim 1, wherein execution of the application initiates one or more threads, and the method further comprises for each thread initiated by the execution of the application:

determining a thread discriminate value for the thread; and

instructing the thread to store the thread discriminate value determined for the thread in a thread-local-storage accessible by only the thread.

7. The computer-implemented method of claim 1, wherein execution of the application initiates one or more threads, and each thread initiated by the execution of the application was created by a module associated with a module identifier and execution of the thread was initiated at an offset location within the module, and

the method further comprises, for each thread initiated by execution of the application:

determining a thread discriminate value for the thread as a function of the module identifier and an offset value identifying the offset location in the module; and

instructing the thread to store the thread discriminate value determined for the thread in a thread-local-storage accessible by only the thread.

8. The computer-implemented method of claim 1, further comprising:

determining a pseudo thread identifier for each thread initiated by execution of the application; and

instructing each thread to store its pseudo thread identifier in a thread-local-storage accessible by only the thread.

9. The computer-implemented method of claim 8, wherein the pseudo thread identifier for each thread initiated by execution of the application is determined as a function of the time value and a thread identifier generated by an operating system for the thread when the thread was created.

10. The computer-implemented method of claim 1, wherein the application is executing on an operating system configured to generate a process identifier for each process executing on the operating system, and the method further comprises:

determining a pseudo process identifier as a function of a time value indicating when the application began executing and a process identifier generated by the operating system for the application when the application began executing; and

sending a process start message comprising the pseudo process identifier and the time value indicating when the application began executing to the management process.

11. The computer-implemented method of claim 10, wherein the pseudo process identifier is determined by performing a hash function on the time value and the process identifier generated by the operating system for the application when the application began executing.

12. The computer-implemented method of claim 1, wherein the application is executing on an operating system configured to generate a thread identifier for each thread executing on the operating system, and the method further comprises:

determining a pseudo thread identifier as a function of a time value indicating when the thread was created and a thread identifier generated by the operating system for the thread when the thread was created; and

sending a thread start message comprising the pseudo thread identifier to the management process, the thread start message comprising the time value indicating when the thread was created.

13. The computer-implemented method of claim 12, wherein the pseudo thread identifier is determined by performing a hash function on the time value and the thread identifier generated by the operating system for the thread when the thread was created.

14. The computer-implemented method of claim 1, wherein monitoring the read operations performed by the application as the application is executing comprises monitoring read operations performed using an IStream interface.

15. The computer-implemented method of claim 1, wherein the application file is a virtualized application file and the runtime engine is a virtual runtime engine.

16. The computer-implemented method of claim 1, wherein the read message comprises:

an offset value indicating where in the application file the read operation started, and

a length value indicating an amount of the application file read.

17. The computer-implemented method of claim 16, wherein the read message comprises a process identifier identifying a process that performed the read operation.

18. The computer-implemented method of claim 17, wherein the read message comprises a thread identifier identifying a thread of the process that performed the read operation.

19. The computer-implemented method of claim 16, wherein the read message further comprises a time value.

20. The computer-implemented method of claim 1, further comprising:

sending a process start message to the management process when execution of the application has begun.

21. The computer-implemented method of claim 1, wherein the management process comprises a named pipe,

the method further comprises connecting to the named pipe of the management process, and

the read message is sent to the management process over the connection with the named pipe of the management process.

22. The computer-implemented method of claim 1, further comprising:

receiving a pause command from the management process to pause execution of the application file; and

pausing execution of the application file in response to receiving the pause command.

23. A computer-implemented method performed by a management process, the method comprising:

sending an execute command to a runtime engine to execute an application implemented by an application file comprising a plurality of data blocks;

each time the executing application requests access to one of the plurality of data blocks, receiving an access request message from the runtime engine indicating the application has requested access to the one of the plurality of data blocks; and

recording that the application requested access to the one of the plurality of data blocks in a transcript.

24. The computer-implemented method of claim 23, further comprising:

establishing a named pipe connection between the management process and the runtime engine, wherein the access request message is received from the runtime engine over the named pipe connection.

25. The computer-implemented method of claim 23, further comprising:

after the runtime engine begins executing the application, receiving a process start message from the runtime engine, the process start message comprising a process identifier; and

recording the process identifier in the transcript.

26. The computer-implemented method of claim 23, further comprising:

after the runtime engine begins executing the application, receiving a process start message from the runtime engine, the process start message comprising a pseudo process identifier that uniquely identifies the application; and

recording the pseudo process identifier in the transcript.

27. The computer-implemented method of claim 26, wherein the application is executing on an operating system configured to generate a process identifier for each process executing on the operating system,

the process start message comprises a time value indicating when the application began executing, and

the pseudo process identifier is determined as a function of the time value and a process identifier generated by the operating system for the application when the application began executing.

28. The computer-implemented method of claim 27, wherein the pseudo process identifier is determined by performing a hash function on the time value and the process identifier generated by the operating system for the application when the application began executing.

29. The computer-implemented method of claim 23, wherein the application file comprises a file name, and the method further comprises:

after the runtime engine begins executing the application, receiving a process start message from the runtime engine, the process start message comprising the file name of the application file.

30. The computer-implemented method of claim 23, further comprising:

after the runtime engine begins executing the application, receiving a process start message from the runtime engine, the process start message comprising a pseudo process identifier that uniquely identifies the application, the access request message from the runtime engine comprising the pseudo process identifier; and

associating the access request message with the pseudo process identifier using a dictionary.

31. The computer-implemented method of claim 23, further comprising:

each time the executing application creates a new thread, creating a new data structure for the new thread, the new data structure storing a thread identifier.

32. The computer-implemented method of claim 23, further comprising:

after the runtime engine begins executing the application, receiving a thread start message from the runtime engine, the thread start message comprising a pseudo thread identifier that uniquely identifies the thread, the access request message from the runtime engine comprising the pseudo thread identifier; and

recording the pseudo thread identifier in the transcript.

33. The computer-implemented method of claim 32, wherein the application is executing on an operating system configured to generate a thread identifier for each thread executing on the operating system,

the thread start message comprises a time value indicating when the thread was created, and

the pseudo thread identifier is determined as a function of the time value and a thread identifier generated by the operating system for the thread when the thread was created.

34. The computer-implemented method of claim 33, wherein the pseudo thread identifier is determined by performing a hash function on the time value and the thread identifier generated by the operating system for the thread when the thread was created.

35. The computer-implemented method of claim 23, wherein the application file is a virtualized application file and the runtime engine is a virtual runtime engine.

36. The computer-implemented method of claim 23, further comprising:

uploading the transcript to a build server configured to construct a streaming model based at least in part on the information included in the transcript.

37. The computer-implemented method of claim 23, further comprising:

downloading the entire application file from a server before sending the execute command to the runtime engine.