|Publication number||US7533371 B1|
|Application number||US 10/667,951|
|Publication date||May 12, 2009|
|Filing date||Sep 22, 2003|
|Priority date||Sep 22, 2003|
|Publication number||10667951, 667951, US 7533371 B1, US 7533371B1, US-B1-7533371, US7533371 B1, US7533371B1|
|Inventors||Kyle R. Johns, J. Andrew Goossen|
|Original Assignee||Microsoft Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (20), Non-Patent Citations (6), Referenced by (21), Classifications (11), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates to performance analysis, and more particularly to user interfaces for facilitating performance analysis for processing.
As computing technology has advanced, the hardware on which video games are run has also advanced and lead to increasingly complex video games. Such complexity can result in video games with excellent graphics and a wide range of actions that can be performed by the users. However, such complexity can also make it difficult for game designers to create video games.
Problems or errors encountered in building and designing video games oftentimes are resolved by “debugging” the instructions that make up the video game. Unfortunately, such debugging can be a very tedious and time-consuming process. For example, in order to maintain the desired playback rate for frames in a video game (typically a rate of 30 frames per second or 60 frames per second), each frame should require no more than a designated amount of time to be drawn (e.g., at 60 frames per second, each frame should require no more than 16.67 ms (milliseconds) to be drawn). If this designated amount of time is exceeded, then the video playback can appear slow and the on-screen action may not appear smooth. When the game designer sees portions of the video playback that are slow, he or she typically tries to debug the instructions by finding out why the designated amount of time is being exceeded, and changing the instructions so that the certain amount of time is no longer exceeded.
Such debugging, however, can be very difficult. One reason for this difficulty is that many video games are designed to be run on game systems that include a graphics processing unit (GPU). The GPU receives commands to draw various aspects of a scene, and renders the scene as indicated by these commands. Unfortunately, the GPU frequently provides very little feedback, if any, to the designer as to why the certain amount of time may be violated. As such, much of the debugging effort is reduced to a trial and error methodology. Thus, it would be beneficial to improve the quality and/or amount of information available to game designers as they build and test their video games.
A user interface for facilitating performance analysis for processing is described herein.
In accordance with certain aspects, a user interface includes a first window that identifies events that have been captured during the drawing of a video frame by a graphics processing unit. The user interface further includes a second window that shows how the frame appears at different chronological points while being drawn.
In accordance with other aspects, a method for controlling presentation of information to facilitate performance analysis for processing includes displaying a listing of events that have been captured during processing of a set of commands as well as information regarding the processing of the events. The method also includes displaying a frame portion that includes information regarding the processing of the set of commands at different chronological points during the processing, and receiving a user selection of one of the events in the listing and selecting which chronological point should be shown in the frame portion based at least in part on the user-selected event.
The same numbers are used throughout the document to reference like components and/or features.
User interfaces for facilitating performance analysis for processing are described herein. Although discussed herein primarily with reference to graphics processing and graphics processing units, user interfaces for facilitating performance analysis for other types of processors can also be facilitated. Commands submitted to a graphics processing unit (GPU) for drawing a frame of video data are captured and saved. These captured commands can subsequently be modified and submitted to the GPU, and/or only some of the commands may be submitted to the GPU. By modifying the captured commands appropriately, and/or submitting appropriate subsets of the captured commands, a wide variety of information can be obtained regarding how the frame is being drawn.
In process 100, commands for drawing a frame of video data are captured and saved. The video data is typically the video portion of a video game, such as video games played on gaming consoles or computers. However, it is to be appreciated that the video data may be associated with other types of applications other than video games, such as educational or reference applications, simulation or emulation applications, productivity or office applications, and so forth.
Video is typically made up of a series of individual images which are played back sequentially. When played back at a fast enough rate, different objects within these images appear to the human eye to move smoothly. Each one of these individual images is referred to as a frame or a scene herein. Different rates of playback can be used, and the rates of 30 frames per second or 60 frames per second are commonly used with the NTSC (National TV Standards Committee) standard.
Process 100 is initiated by a request, typically from a user, to initiate a frame capture. In response to the request, the state of the graphics processing unit is captured (act 102) when drawing of the current frame is finished. Given the speed at which video frames are drawn, a request to capture a frame or scene is typically received while another frame or scene is being drawn. Process 100 waits until drawing of the current frame is finished so that all of the data desired to be captured for drawing an entire frame can be captured.
The state of the graphics processing unit refers to all of the registers, buffers, and/or other memory of the graphics processing unit in which variables or settings are stored. These variables or settings are used by the graphics processing unit in drawing frames. A variety of different variables or settings may be used, such as shading or lighting variables, transparency variables, and so forth. Many of these variables and/or settings can be programmed by the game designer, and thus their settings are relevant to the frame about to be drawn. For example, a frame being drawn may appear differently if transparency is turned on than if transparency is turned off.
After the state of the graphics processing unit is captured, the commands sent to the graphics processing unit for a frame are captured (act 104). The number of commands sent to the graphics processing unit in order for the unit to draw a single frame can vary, but can easily be in the hundreds if not thousands of commands. Additional information associated with these commands (e.g., the contents of memory referenced by the commands) may also be captured, as discussed in more detail below. A set of commands sent to the graphics processing unit is also referred to herein as a command stream or stream of commands.
The captured state of the graphics processing unit from act 102 and the captured set of commands from act 104 are saved (act 106). By saving the state of the GPU and the captured set of commands, at a later time the GPU can be set to the same state as when the set of commands were captured, and then selected ones of the commands can be submitted to the GPU, as discussed in more detail below.
Alternatively, rather than capturing the commands or in addition to capturing the commands, timing data may be captured in act 104 and saved in act 106. As discussed in more detail below, this timing data can identify, for example, an amount of time taken to draw the frame and/or amounts of time taken to draw different parts of the frame.
The set of captured commands can optionally be modified (act 108). This modification can be changing one or more of the commands in the set, adding one or more commands to the set, removing one or more commands from the set, and/or reordering one or more commands in the set. The specific way in which the modification is performed can vary based on the type of information to be ascertained. For example, the modification may involve analyzing the set of commands to identify redundant commands and then removing those redundant commands. Additional details regarding modifications to the set of captured commands are discussed below.
The GPU is then set to the state that was captured in act 102 (act 110). This setting can be performed by, for example, setting all of the registers, buffers, and/or other memory of the graphics processing unit in which variables or settings are stored to the same settings as were captured in act 102.
Once the GPU is set to the captured state, at least a subset of the set of commands captured in act 104 are sent to the GPU (act 112). These commands sent to the GPU in act 112 may optionally include the set of commands as modified in act 108. For example, if there are commands to draw the terrain in a frame and commands to draw characters in the frame, only the commands to draw the terrain may be sent to the GPU in act 112 to allow the user to see how the terrain was drawn without the characters being present. By way of another example, if the set of commands is modified in act 108 to remove the redundant commands, then the modified set of commands (having the redundant commands removed) may be sent to the GPU in act 112.
After the commands are sent to the GPU in act 112, feedback is returned based on the commands sent in act 112 (act 114). This feedback can take a variety of different forms. For example, the feedback may be the frame drawn given the commands sent to the GPU in act 112. By way of another example, the feedback may be an indication of how long it took the GPU to draw the frame given the commands sent to the GPU in act 112. The feedback may also take other forms, as discussed in additional detail below.
Game device 152 includes a central processing unit (CPU) 156 and a graphics processing unit (GPU) 158. CPU 156 runs a game or other application 160, and during running of the game 160 various commands are presented to GPU 158 in order to generate the video data for display by the game. Any of a variety of conventional CPUs and GPUs can be used as CPU 156 and GPU 158, respectively. GPU 158 processes the commands it receives and outputs its results into a memory commonly referred to as a frame buffer. Once GPU 158 has processed all of the commands it has received and output its results to the frame buffer, the display device can display the frame using the contents of the frame buffer. In certain embodiments, the frame buffer is a bit map that identifies, for each pixel of the display device, what color is to be displayed for that pixel. The processing of the commands and outputting of results into the frame buffer by GPU 158 is also referred to as GPU 158 drawing the frame.
The video is displayed on one or more display devices 162, and the user can control the game through one or more input devices 164. Display device 162 is intended to represent any device on which video can be displayed. Display device 162 can be, for example, a television (e.g., cathode-ray tube (CRT), plasma, projection, etc.), a computer monitor (e.g., CRT, plasma, LCD, etc.), a display device built into the same housing as game device 152 (e.g., a plasma display, LCD display, etc.), and so forth. Input device 164 is intended to represent any device which can input data to the game device 152. Input device 164 can be, for example, a handheld controller (e.g., having a joystick(s), button(s), and/or triggers), a mouse or other cursor control device, a steering wheel and pedals, a keyboard, a microphone, and so forth. Input device 164 can be external to game device 152, or alternatively may be included as part of game device 152.
Computing device 154 is a remote device to game device 152. Computing device 154 may be located close to game device 152 (e.g., on the same desk or in the same room), or alternatively may be located further away from game device 152 (e.g., in another part of the building, or across the Internet). Computing device 154 represents any of a variety of computing devices (e.g., a desktop PC, workstation, portable or notebook computer, etc.). Computing device 154 similarly is coupled to (and/or includes) one or more display devices 166 and one or more input devices 168. Display device 166 can be any device on which video can be displayed, analogous to display device 162. Input device 168 can be any device which can input data to computing device 154, analogous to input device 164.
Computing device 154 includes a capture control application 170 that is executed by one or more processors (not shown) of computing device 154. Capture control application 170 displays, on display device 166, a user interface that allows a user (e.g., a game designer or tester) to request that frames of video be captured and/or to present feedback (e.g., from act 114 of
When a user, such as a game designer or tester, desires to capture a frame of video data, he or she indicates to capture application 172 to begin capturing a frame of video data. Capture application 172 can be invoked to begin capturing a frame of video data in a variety of different manners. In certain embodiments, a command is entered by the user to capture control application 170 by way of input device 168 (e.g., a keyboard sequence may be entered, a “capture” button or menu option displayed in the user interface provided by application 170 may be selected, a verbal command may be input, and so forth). When such a command is received by application 170, application 170 sends a request to capture application 172 for capture application 172 to begin capturing a video frame. In other embodiments, the command may be entered by the user to capture application 172 by way of input device 164 (e.g., a keyboard sequence may be entered, a sequence of buttons, triggers, and/or joystick positions on a game controller may be entered, a verbal command may be input, and so forth).
The game designer or tester may desire to capture frames of video data at different times for a variety of different reasons. For example, the designer or tester may simply desire to randomly capture video frames while playing the game in order to analyze the frames and verify they are being drawn as desired. By way of another example, the designer or tester may play the game and, whenever he or she perceives that the game is running slower than he or she believes it should, then he or she can have a video frame selected at this “slow” spot. This allows, for example, the designer or tester to analyze a frame in a “slow” spot of the game in order to ascertain whether the frame is being drawn as fast as it should be, and if not why not.
When capture application 172 receives the command to begin capturing a video frame, application 172 waits for drawing of the current frame to finish, then captures the state of GPU 158 and saves that state in capture storage 174. Capture storage 174 can be any of a variety of storage devices (e.g., volatile or nonvolatile memory such as RAM or Flash memory, a magnetic or optical disk, etc.). Although illustrated as being part of game device 152, capture storage may be located entirely or partially elsewhere. For example, capture storage 174 may be distributed across multiple storage devices, or may be located entirely on a storage device in another location. Other locations where capture storage 174 may be located include an input device 164, computing device 154, input device 168, and so forth.
After capturing the state of GPU 158, capture application 172 proceeds to capture all commands that are sent to GPU 158 for the frame and stores the captured commands in capture storage 174. Capturing the commands sent to GPU 158 is a process in which running application 160, which sends commands to GPU 158, is interrupted each time it sends a command and the command is copied into capture storage 174. When the command has been copied, running application 160 continues to execute and submits its next command to GPU 158. After all of the commands for the frame have been sent to GPU 158, capture application 172 stops capturing the commands. Capture application 172 then waits until it again receives a command to capture a frame before proceeding to capture any additional frames.
Although described herein as typically capturing only one frame at a time, alternatively multiple frames may be captured by capture application 172 when it receives a command to capture a frame. Capture application 172 may be pre-configured or pre-programmed with a number of frames it will capture when it receives a command to capture a frame, capture application 172 may have a default number of frames it will capture, the user that initiates the command to capture a frame may supply as part of the command the number of frames to be captured, and so forth. For example, capture application 172 may capture two, three, four, or more consecutive frames in response to such a command. By way of another example, capture application 172 may capture one frame, then capture a second frame some amount of time afterwards (e.g., the second frame may be the 45th frame after the command is received). By way of yet another example, a user may specify when the capture is to begin and then frames are captured until the user specifies that the capture should end. In this situation, a variable number of frames would be captured.
Capture application 172 can capture timing data regarding commands submitted to GPU 158 and/or the commands submitted to GPU 158. When timing data and the commands are both captured, care should be taken that the time involved in capturing of commands is not reflected in the captured timing data. This situation can be resolved in different manners. In certain embodiments, either the timing data or the commands are captured, and then the game 160 is informed that it should repeat the frame. The game repeats preparing that frame at which time the other of the timing data and commands are captured. In alternate embodiments, the commands are captured and then timing data is obtained subsequently as part of the analysis process (e.g., in acts 112 and 114 of
The way in which the state of the GPU 158 and the commands sent to the GPU 158 (or timing data) are captured can vary. The state of the GPU 158 and commands sent to the GPU 158 may be captured in different manners due to design choices as well as due to differences in the architecture of GPU 158 and/or game device 152.
In certain embodiments, game device 152 includes a Direct3DŽ (D3D) Application Programming Interface DLL (dynamic link library) which is a library of graphics functions that can be invoked by game 160. Capture application 172 can optionally be incorporated into the D3D library.
Table I illustrates an example list of CPU events for which timing data can be captured, as well as whether there is a GPU event that corresponds to the CPU event. These events refer to calls to API (application programming interface) functions or procedures. The time when the call to the API is made, as well as when the called function or procedure ends, is recorded as part of the timing data.
Capture application 172 can obtain the current state of GPU 158 in a variety of manners. In certain embodiments, capture application 172 submits one or more commands specific to GPU 158, in response to which GPU 158 returns its state (e.g., the current values of all of the registers, buffers, and/or other memory of GPU 158 in which variables or settings are stored). Other static information in GPU 158 may also be obtained as part of the capture, such as the instructions of programs used internally by GPU 158 (e.g., pixel shader or vertex shader programs used GPU 158). In other embodiments, the regions of memory in GPU 158 are accessible by memory address to capture application 172, and capture application 172 can read from these memory addresses.
Capture application 172 can capture commands sent to GPU 158 by monitoring the commands that are sent to GPU 158 (e.g., from the D3D DLL). Every time a command is sent from the D3D DLL library, application 172 captures the command and all of the parameters of the command. Additionally, some commands may have as parameters references to other memory locations. In these situations, application 172 obtains the data from the referenced memory location(s) and captures that data as well. Additionally, rather than always capturing the data at the referenced memory location, application 172 can check whether that memory location was previously referenced by another command already captured for this frame—if so, then application 172 can check whether the data previously obtained from that memory location is the same as the data currently obtained from that memory location, and if so then the data need not be captured again for this command. Such a check can be performed in different manners, such as by maintaining a record of memory locations accessed and their contents when accessed, by searching through the commands already captured, and so forth.
By obtaining data from other memory locations referenced in calls to GPU 158, the capture performed by application 172 is more robust. As a specific example, assume that texture mapping is being used to draw the surfaces of tree leaves in a frame. The texture mapping for the leaves is stored in the same memory location, but CPU 156 may modify that texture mapping for two different leaves in the frame. So, even though each command sent to GPU 158 references the same memory location, the texture mapping used for the two different leaves is different. Thus, in order to accurately capture the frame being drawn, the data at that memory location (the texture map) should be captured as well.
In certain embodiments, a capture opcode in the D3D DLL is used to indicate whether the next frame is to be captured. When a command to capture a frame is received by capture application 172, capture application 172 sets the capture opcode. The end of a frame is indicated by game 160 by use of a Present( ) or Swap( ) call. When a Present( ) or Swap( ) call is detected by the D3D DLL, the D3D DLL checks whether the capture opcode has been set. If the capture opcode has been set, then application 172 proceeds to begin capturing the next frame. Additionally, application 172 clears the capture opcode so that at the end of the frame being captured the capture opcode will not be set and another frame will not be captured.
Additionally, the game designer may design the game to specify certain information when the game is submitting commands to GPU 158. For example, the game designer may include information identifying what part of the frame is being drawn (e.g., the character's left arm, the character's right arm, the character's weapon, the background terrain, etc.). When such information is present, capture application 172 can capture this information and save it in capture storage 174. This captured information can then subsequently be used when feedback is presented to the user (e.g., in act 114 of
In addition, stack trace information may also be captured by application 172. Stack trace information tells the user which software routines called a particular function (e.g., a D3D function) which resulted in a command being sent to GPU 158. Each time a function is called, the return address is placed on the stack. The stack trace is obtained by parsing back through the stack from the current stack pointer and retrieving these return addresses. Using this series of return addresses, capture application 172 examines the symbols for running application 160 and converts the addresses to symbols that are more informative to the user. For example, a fully resolved stack trace might look something like the following:
The last function listed in the stack trace, DrawIndexedVertices( ), is typically a function that resulted in a GPU command being passed to GPU 158. When a developer is analyzing data from a captured scene, the stack trace helps the developer to identify which drawing calls are which.
Game device 200 includes a CPU 202 (analogous to CPU 156 of
Game device 200 also includes a capture control application 214 and a capture application 216. Capture control application 214 is similar to capture control application 170 of
Game device 242 is similar to game device 152 of
Computing device 244 includes an analysis control and feedback application 258. Application 258 provides a user interface, through display device 254. The user interface allows the user of device 244 to input, through input device 256, requests for analysis of a frame to be performed. These requests can also be referred to as questions regarding the frame. The user interface provided by application 258 also displays feedback regarding the frame to the user of device 244 (e.g., the feedback in act 114 of
Requests for analysis are sent from application 258 to analysis application 260. Analysis of a frame can begin immediately after the frame is captured, or alternatively at some later time. For example, when the designer or tester captures a frame, the analysis of the frame may begin right after the frame is captured, or alternatively multiple frames may be captured and the designer or tester (or some other user) may begin analysis of the captured frames at some later time.
Analysis application 260 receives the requests for analysis and sends the appropriate portions of captured data 262 to GPU 248. Feedback regarding the drawing of the data sent to GPU 248 is then returned by analysis application 260 to application 258 for presentation to the user on display device 254. Depending on the analysis requested, analysis application 260 may generate modified data 264 that is sent to GPU 248 in place of, or alternatively in addition to, captured data 262.
The captured data 262 is the same data for the frame as was captured and stored in the capture storage (e.g., storage 174 of
Additionally, although analysis application 260 is shown as being part of game device 242, portions of analysis application 260 may be implemented in computing device 244. For example, any required modifications to the data may be performed by computing device 244 rather than game device 242. Additionally, some analysis can be performed by computing device 244 without any help from game device 242. For example, the size of the captured data and the number of commands in the data can be determined by computing device 244 by parsing through the command stream.
When analysis of a frame is to begin, the state of GPU 248 is set to the previously captured state (e.g., as captured in act 102 of
It should be noted that, during the analysis process, certain other memory locations in game device 242 may be accessed. For example, the memory location(s) for texture map(s) used in drawing the frame may be accessed. In such situations where other memory locations are accessed, analysis application 260 writes the appropriate data (as captured) to those memory locations prior to their being accessed by the captured commands.
One type of analysis that can be performed by analysis application 260 is timing analysis. Timing analysis refers to determining an amount of time a particular frame or portion of a frame takes to be drawn. Game device 242 has a clock (not shown) that can be used to determine an amount of time taken for a particular frame to be drawn. The commands for drawing the frame are sent to GPU 248 by analysis application 260, so application 260 can identify the current time of the clock when the first command is sent to GPU 248 (e.g., immediately prior to sending the first command to GPU 248). Application 260 also sends a command to GPU 248 to indicate that it has completed sending commands to GPU 248 (e.g., the Present( ) or Swap( ) commands discussed above). When GPU 248 has completed drawing the last command, GPU 248 returns an indication to the application sending the commands to GPU 248 (analysis application 260 in this instance) that the last command is completed. Application 260 can then identify the current time of the clock. By knowing the time when drawing of the frame began and the time when drawing of the frame was completed, the difference between these two times can be readily determined in order to identify the amount of time taken to draw the frame.
The amount of time taken to draw a portion of a frame can be determined in an analogous manner. By accessing the clock, the time when drawing of the portion begins and drawing of the portion is completed can be readily determined. These different portions can correspond to, for example, the events identified above in Table I.
The timing analysis can be used as a basis to provide various feedback to the user. The amount of time taken for a frame or portion of a frame to be drawn can be returned to the user. Additionally, other information can be ascertained based on the timing analysis and this other information can be returned to the user. This other information can be ascertained by analysis application 260 and/or analysis control and feedback application 258.
A wide variety of information can be ascertained based on this timing analysis. For example, which portions (e.g., objects) of the frame took the longest or shortest time to draw can be ascertained.
The timing analysis can also be performed based on modified data 264. This allows analysis application 260 to modify captured data 262 and then submit the modified data to GPU 248. The time taken to draw both the unmodified data and the modified data can be determined, and these two times used to determine how much the modification affected the time taken to draw the frame. For example, analysis application 260 may analyze captured data 262 to identify redundant commands. Redundant commands within the set of commands that is captured data 262 refers to duplicate commands that are present in the set of commands but one or more of these duplicate commands can be removed without altering the frame drawn by the set of commands. E.g., multiple commands to turn off transparency may be present in the set of commands, even though no other command in the set of commands operates to turn on transparency. Thus, all of the commands to turn off transparency after the first command to turn off transparency could be removed from the set of commands (the first command may also be removed if there is no previous command or state of the GPU 248 that would have caused transparency to be turned on).
It should be noted that some timing data for performing the timing analysis may be captured when the frame is captured, rather than being determined during the analysis process. For example, situations may arise where the amount of time taken by the CPU in the game device to determine particular values to be used in drawing the frame is very large. By capturing the timing data when the CPU is determining the particular values, rather than capturing the timing data based on the resultant captured values, situations where the GPU goes idle can be more easily detected. For example, the CPU can be so busy that it waits too long to issue a new command to the GPU which causes the GPU to go idle because it has nothing to work on. This is an important case for developers to be aware of because they typically endeavor to keep the GPU busy at all times. This information is lost when playing back a captured stream of commands because the commands are played back one-after-another without regard for any idle spots that may have been present when the application (e.g., game) originally ran.
Another type of analysis that can be performed by analysis application 260 is a partial frame draw. All of the commands in the captured data 262 are used to draw the entire frame. A partial frame draw can be performed by sending only a subset of the commands in the captured data 262 to GPU 248 and having GPU 248 draw the frame using only that subset (and thus less than all of the captured commands). For example, analysis application 260 may choose to send only the first five commands or the first ten commands, or all of the commands leading up to a particular command, etc. to GPU 248.
Whatever the subset of commands is, GPU 248 receives the subset and draws a frame given only that subset. Analysis application 260 can then return this frame to analysis control and feedback application 258 for display to the user on display device 254. Application 260 can send this frame in different manners, such as generating a bitmap representing the frame as drawn by GPU 248 and sending that bitmap to application 258. Drawing a partial frame can be useful to the developer as it allows the developer to see what the frame looks like after the first n drawing commands are completed (where the value of n can be set by the developer). Much like single-stepping a program, this allows the developer to see the scene being drawn step-by-step and to quickly determine which step drew something incorrectly.
Another type of analysis that can be performed by analysis application 260 is the determining of internal non-exposed state of GPU 248. Some state of the GPU 248 can be accessed by devices external to GPU 248 (e.g., the settings of certain variables, register values, etc.), and these states are captured as discussed above (e.g., in act 102 of
However, GPU 248 may also include additional internal state for which GPU 248 provides no mechanism for any component or module external to GPU 248 to access (e.g., no command can be sent to GPU 248 to read particular internal register values). Such states are typically transitory states. Transitory states can be thought of as similar to scratchpad memory, where the contents are only valid during a particular instruction of a particular invocation of the vertex or pixel shader program. When the next vertex or pixel is processed, this state is overwritten. Such transitory states are typically not easily retrievable because GPUs typically have no way to halt execution at a particular point so that these states can be read.
Some GPUs include internal programs that process some of the data received as commands. For example, one or more vertex shader programs and/or one or more pixel shader programs may be included in the GPU that operate on some of the data received by the GPU. As these programs within the GPU can make use of their own internal variables (e.g., registers and/or other memories), it may be useful to the designer or tester to know what the values of these registers and/or variables are as each pixel or vertex is processed. These registers and/or variables are often transitory states, such as the contents of a temporary register after a particular instruction has executed in a pixel shader program of GPU 248 that is a particular pixel in a particular drawing operation in the scene (e.g., the tmp0 register contents after instruction 3 has executed in the pixel shader program that is processing pixel 238,242 in the 7th drawing operation in the scene). By modifying the captured commands, and possibly internal programs for the GPU, additional information can be obtained.
Such modifications to identify settings of internal registers and/or other variables is illustrated by the following example. Assume that a pixel shader program used by the GPU is as follows (where t0, t1, and r0 are internal GPU registers):
tex t0 //load the result of texture stage t0 into register t0
tex t1 //load the result of texture stage t1 into register t1
add r0, t0, c0 //r0=t0+c0
mul r0, r0, t1 //r0=r0*t1
Analysis application 260 can determine the internal value of the register r0 in the third instruction as follows. The shader programmer is modified to be as follows:
tex t0 //load the result of texture stage t0 into register to
tex t //load the result of texture stage t1 into register t1
add r0, t0, c0 //r0=t0+c0
Notice that the last instruction which loaded register r0 with the value r0*t1 was removed. At the end of the shader program, r0 will contain the value of t0+c0 and that will be the result value that will be written to the frame buffer for that pixel. The modified command stream is fed to the GPU and the value for the pixel being tested is read from the frame buffer and can be returned to application 258 for presentation to the user. This value is the value of the r0 register in the third instruction.
The program can be modified again as follows:
tex t0 //load the result of texture stage t0 into register t0
tex t0 //load the result of texture stage t1 into register t1
mov r0, t1 //r0=t1
Now, the value written by the GPU to the frame buffer will be the value of the t1 register in the second instruction. This process can be followed repeatedly to extract the values of all the internal registers.
In certain embodiments, analysis control and feedback application 258 has multiple default requests or questions that it submits to analysis application 260. These default requests or questions are pre-programmed into application 258. Additionally, the user of computing device 244 may also request information that involves one or more additional requests or questions be sent to analysis application 260.
In certain embodiments, analysis application 260 and/or analysis control and feedback application 258 analyze the requests sent to analysis application 260 and generate warnings for the user regarding rules or recommendations that were violated by the frame. For example, each different type of GPU typically has its own recommended programming practices. Tests to determine whether these programming practices were violated can be programmed in to application 258 or 260, so that each time a frame is analyzed these tests can be performed to determine whether the recommendations for programming the GPU were violated. A variety of such recommendations may exist, such as not setting certain register values if certain GPU functionality is not being used in a frame, issuing certain commands in certain orders, having the frame buffer and depth buffer both in tiled memory, not clearing the screen multiple times (e.g., clearing the screen after it has already been cleared), not submitting redundant commands, and so forth. Additionally, warnings can be given different priorities. For example, the warnings can be ranked according to how much time adhering to their associated recommendations would save for this frame. By way of another example, particular warnings may be presented only if they satisfy certain constraints (e.g., display a warning to the user only if not violating the recommendation would have allowed the frame to be drawn a threshold amount faster).
Analysis of the frame can continue until analysis application 260 is informed to stop analyzing the frame. The user, for example, can select a “stop” or “cancel” option on the user interface presented by application 258 to stop analyzing the frame.
It should be noted that all of the analysis of the set of commands, whether captured commands or modified commands are sent to GPU 248, is based on the commands being performed by the same GPU as will be running the game. As the actual GPU can be used, an emulator or simulator need not be used. By using the actual GPU, the accuracy of the analysis is improved due to any approximations or errors that may be introduced by an emulator or simulator. Additionally, any timing measurements obtained by an emulator or simulator would have little, if any, meaning.
Game device 300 includes a CPU 302 (analogous to CPU 246 of
Game device 300 also includes an analysis control and feedback application 314 and an analysis application 316. Analysis control and feedback application 314 is similar to analysis control and feedback application 258 of
The analysis control and feedback application (e.g., application 258 of
Timeline window 342 displays the captured timing information graphically using a timeline. This captured timing information can include, for example, when particular CPU or GPU events occurred.
Events window 344 contains a listing or grid of all of the events that have been captured along with all of the data regarding the frame that has been calculated as part of the analysis of the frame (e.g., by analysis application 260 of
Frame window 346 displays information regarding the display of the frame, and may include images showing how the frame appears at different points during its being drawn. Windows 342, 344, and 346 are discussed in additional detail below.
It should be noted that although all three windows 342, 344, and 346 are illustrated in
Windows 342, 344, and 346 are illustrated in
An event as discussed herein can be different things in different embodiments. For example, in certain embodiments there may be particular commands that constitute events, such as those listed in Table I above. In other embodiments, every command submitted to the graphics processing unit may be an event. In other embodiments, the events may be identified by the game designer. For example, as discussed above the game designer may design a game to specify certain information when the game is submitting commands to the graphics processing unit (e.g., identifying what part of the frame is being drawn, such as the character's left arm, the character's right arm, the character's weapon, the background terrain, etc.). Such information can be used as events (e.g., each part of the frame being drawn can be a separate event).
Timeline window 362 displays the events that are listed in events window 364. These events can be hierarchical in nature. For example, a MainCharacter event may contain other events (referred to as children events) for DrawLeftArm, DrawHead, DrawWeapon, and so forth. When one event contains other events, it is displayed with a small plus sign next to it in events window 364. When the plus sign is clicked, the event is expanded so that its children events are displayed. When this happens, the event display in timeline window 362 changes. The horizontal bar that represented the parent event is now replaced with one or more horizontal bars that represent the child events. These horizontal bars may be the same color as the parent event or a different color. the space covered by the children events on the timeline does not exceed the space covered by the parent event.
All of the bars in timeline 368 may be the same color, or different colors may be used to signify different events. For example, clear commands may be one color, draw commands may be another color, swap commands may be yet another color, and so forth.
Additionally, more specific information may be available to the user by moving a cursor (e.g., an arrow or other on-screen cursor) over a part of timeline 368. The cursor can be moved using any of a variety of devices, such as a mouse, game controller, keyboard, track pad, trackball, and so forth. When the cursor is stationary over an event for greater than a threshold amount of time (e.g., one or two seconds), more specific information can be displayed to the user. Alternatively, when the event is “selected” (such as by depressing a mouse button or game controller button when the cursor is over the event) the more specific information can be displayed to the user. This more specific information can take a variety of different forms, such as the specific start and end times for the event (e.g., in nanoseconds).
Timeline window 362 can include a timeline for the CPU, a timeline for the GPU, or timelines for both the CPU and the GPU.
When a CPU event is selected, the head of the arrow that points to the CPU event is solid and the head of the arrow that points to the corresponding GPU event is hollow. When a CPU event is selected, the arrow keys cause the CPU cursor to move linearly along CPU timeline 382. The down-arrow key moves the solid headed arrow down to the GPU event and subsequent arrow-key presses move the cursor linearly along GPU timeline 384. Pressing the up-arrow key moves the solid arrow head back up to CPU timeline 382 and the corresponding CPU event is selected. When a CPU event is selected, the other arrow points to the corresponding GPU event. Likewise, when a GPU event is selected, the other arrow points to the corresponding CPU event.
One or more graphs 386 may also be included in timeline window 380. Different information may be graphed, and in certain embodiments the user is able to select one of the columns from the events window (e.g., window 364 of
The ordering of the events listed in events window 364 is ordinarily determined by the CPU Start Time column. Clicking on another column will cause the events to be listed in ascending order for that column. Clicking again on the header will cause the events to be listed in descending order for that column. An option is provided in the context menu (e.g., activated by right-clicking in the window) to restore the event sorting to its default value. Each column can be resized by dragging the edge of the column header with a cursor control device. The headers remain in place vertically as the events are scrolled up or down but they track the horizontal movement of the table as it is scrolled from side-to-side. Right clicking on the table or the columns brings up a context menu with additional options for resizing or other operations.
One example of such an operation is to export the entire table to a file that can be loaded into a spreadsheet or other program for further analysis. Another example of such an operation is to specify one or more columns that will be graphed in the timeline window along with the GPU event data (e.g., as graph 386 of
One or more rows of the table can be highlighted. The highlighted row(s) represent the event(s) which correspond to the event(s) that are represented by the currently selected horizontal bar of timeline 368. When a new horizontal bar(s) of timeline 368 is selected, then a new row(s) of the table is highlighted (the new row(s) representing the same event(s) as the newly selected horizontal bar(s)). Similarly, if a new row(s) of the table is selected and highlighted, then a new horizontal bar(s) of timeline 368 is selected (the new horizontal bar(s) representing the same event(s) as the newly selected row(s).
The last row in the table is a summary row. The summary row contains calculated values based on all of the other events in the table. Each column has a summary type associated with it that is one of a maximum value, a minimum value, an average value, or a sum value. The summary value is calculated based on the summary type and the data in the column.
The events window will also support a hierarchical display of events. An application can specify user-defined events in a hierarchical way. When these events encompass other events, the user will have an option to display the user-event, the CPU and GPU events, and/or other hierarchical events that comprise it. For example, a game may specify a Start time for their physics engine and an end time. If no graphics events occurred during this time, the physics engine event will show up as a discrete CPU-only event in the events window. A game may also specify a start time for rendering the main character in the game and also an end time. In between these times are all the rendering calls for the main character. This event can be displayed in the events window with an expansion icon next to it. If the user clicks on this expansion icon, the events window will display all of the graphics events that occurred during the user event. When the user event is displayed, its columns will contain a summary of the information contained by the events under it in the hierarchy based on the summary type specified for each column.
By way of example, events window 400 of
A variety of different columns can be included in events window 364. Table II lists examples of such columns. Reference is made in Table II, as well as elsewhere in this description, to the “push buffer” or “pushbuffer”. The push buffer or pushbuffer refers to the commands and their associated data that are submitted to the graphics processing unit to be drawn. These commands and their associated data are captured, as discussed above.
Total back-end time that the rendering primitive took,
as measured at the Z-cull stage of the graphics
hardware pipeline. A hardware back-end flush is done
between primitives to measure each primitive
independently from one another. Because the flush
eliminates overlaps in the pipeline between primitives,
the sum of the back-end times may be more than the
overall back-end render time.
The number of pixels that would have been rendered if
Cull Pixel Count
depth, stencil, and alpha comparison functions were
ALWAYS. When multi-sampling, this is the post-
The number of pixels that are actually rendered, taking
Cull Pixel Count
into account depth, stencil, and alpha occlusion. When
multi-sampling, this is the post-multisample-expansion
Percent of pixels that are occlusion culled.
Effective pixel fill rate, relative to the back-end time.
Ideal Fill Rate
Ideal pixel fill rate, relative to the back-end time. This
is measured using all of the current state with the
current render target, but using large quads that are
rendered such that Z and stencil tests always pass, and
with all textures forced to be opaque and 1 × 1 (or
1 × 1 × 1) texels in size. This is the fill-rate that could
be achieved with the current primitive in the current
state if the current Z compression was 100%, there was
100% utilization of the 4 pixel pipelines, and the
texture reads had no performance impact.
Effective triangle fill rate, relative to the back-end
Measured speed of the current vertex shader program
(or fixed-function T&L), in GPU cycles.
The same measurement as the back-end time, but done
with all textures set to opaque, 1 × 1 (or 1 × 1 × 1)
% Texture Bound
Measures how much of the rendered primitive time is
attributable to texture fetches, as computed using the
back-end times for 1 × 1 and normal sized textures.
The same measurement as the back-end time, but done
with the viewport forced to a zero-pixel size.
% Fill Bound
Measures how much of the rendered primitive time is
attributable to fills, as computed using the back-end
times for zero-pixel and normal sized viewports.
The percentage of Z packets that are compressed after
the primitive is rendered. Note that this is not the
effective compression of the Z-buffer (after a Z clear,
the percentage of Z-compressed packets will be 100%,
but the effective compression is 87.5% due to 8-to-1
The number of bytes that are written into the push
buffer to handle the command for the primitive
rendering. For DrawIndexedVertices, this is effectively
the amount of index data that has to be copied to the
The number of bytes of state change commands in the
push buffer that preceded the rendered primitive.
Where the event occurs chronologically in drawing of
Different windows can be displayed as the frame window 366. Examples of such windows that can be displayed as the frame window 366 include an images window (examples of which are illustrated in
The surfaces can be displayed within the images window 420 at various sizes (e.g., 100%, 200%, 400%, 50%, 25%, fit to window, etc.).
When the mouse is moved over a particular place on a surface displayed in the images window, the actual values at that pixel will be displayed in a status bar. An example status bar 426 is illustrated in
For one or more of the views of the images window, such as the render target view, a particular pixel or group of pixels can be selected by the user. This selection can be made, for example, by the user moving a cursor over a pixel and activating the pointing device being used to control the cursor (e.g., clicking on the mouse button). By way of another example, a user could click and drag a rectangle to select a group of pixels. When such a pixel(s) is selected, all of the events in the events window (view 364 of
The render target view 422 shows the color and alpha values held by the frame buffer. These values can correspond to the final image that is the frame, or alternatively may be some point during drawing of the frame. For example, as discussed above, only the commands for drawing a particular part of the scene may be submitted to the graphics processing unit, and the resultant frame can be displayed using the render target view.
In certain embodiments, the render target view 422 in conjunction with the timeline in timeline window 362 or the events in events window 364 can allow a user to “step through” the drawing of a frame event by event. For example, the user can select the first event (the first row) in the grid of window 364 and have the resultant view after only that first event is drawn by the graphics processing unit displayed as the render target view 422. The user can then select the second event (the second row) in the grid of window 364 and have the resultant view after both the first and second events are drawn by the graphics processing unit displayed as the render target view 422. This process can continue, allowing the user to slowly see how the frame is drawn and to easily identify any drawing problems associated with each event.
In the example call stack window 450, the stack trace data displayed to the user shows the sequence of calls that resulted in the listed event being sent as a command to the GPU. Each line in the display corresponds to a function call in the program. The first function listed shows the function that submitted a command to the GPU that resulted in the listed event. The next line shows the function that called the first function, etc. The last function listed for each event is the top-level function in the game. The filename and line number where each function is located in the game source code is also displayed.
Each warning has a priority associated with it from 1 to 3. Priority 1 warnings are serious problems that may have a significant impact on the time it takes the game to draw a frame. Priority 2 warnings are less important but still important to consider when performance-tuning a game. Priority 3 warnings are suggestions that are good to follow but may not have a large impact on the overall performance. The user can use check boxes 462 to choose which warnings should be displayed according to their priority.
Pixel history window 500 lists each event that affects the selected pixel during the frame, or alternatively only up to a particular point in the frame (e.g., as identified by the user). Additional information regarding each event as it affects the selected pixel is also displayed. The specific information displayed can vary based on the event. In the illustrated example of pixel history window 500, initial frame buffer values 502 are displayed. The frame then starts with a clear command, which is shown as clear event 504. Each subsequent event 506 affecting the selected pixel is also identified in window 500, as well as additional information regarding those events. For example, the pixel shader output color and frame buffer color after blending may can be identified.
Pixel history window 500 may also include links to the event, a pixel shader debugger, a vertex shader debugger, and a mesh debugger. If the link to the event is selected by the user, then that event is made the current event in the user interface (e.g., windows 362, 364, and 366 of
Pixel shader debugger window 520 also includes a vertex portion 522 that includes information regarding the vertices of the triangle currently being drawn (as part of the current event) that the selected pixel is part of. The vertex shader debugger window can be displayed in response to a user selection of such an option in window 520, such as user selection of one of the vertices identified in vertex portion 522.
It should be noted that, with reference to
Although the discussions above primarily discuss facilitating performance analysis for graphics processing, the techniques described herein can similarly be used to facilitate performance analysis for other types of processors, including general purpose processors and specific purpose (e.g., dedicated) processors. The techniques described herein can be applied to virtually any processor that accepts a command stream and can be used to provide information regarding processing of the command stream. For example, the techniques described herein can be used to facilitate performance analysis for general purpose processors (e.g., CPUs). Correspondingly, the techniques described herein can be used to facilitate performance analysis for processors on other computing devices other than game devices.
Depending on the type of application being executed on the computing device and the type of processor, the capture of commands sent to the processor can vary. For example, if the application is a graphics or video application, then the application may still send commands to the processor indicating the beginning and ending of frames. Thus, the commands to be captured can be identified on a frame-by-frame basis. In other examples, the application may not issue any such indications of the beginning and ending of frames. In such situations, the beginning and ending points for capture would be identified in different manners. For example, a separate command(s) may be embedded in the application that indicate the beginning and ending of points for capture, or the capture may simply begin as soon as the request to capture is received, and then end after some amount of time (e.g., the request may indicate how long the capture should continue for, such as a length of time in milliseconds or seconds, or a number of commands to be captured, etc.).
Capturing commands for a general purpose processor can permit a great deal of information regarding processing of those commands by the processor to be returned to the application designer. For example, using the techniques described herein precise measures of how long processing of particular commands or groups of commands took can be made. By way of another example, instruction traces identifying the specific instructions executed in the captured portion can be readily determined.
Computer environment 600 includes a general-purpose computing device in the form of a computer 602. Computer 602 can be, for example, game device 152 or computing device 154 of
The system bus 608 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures can include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnects (PCI) bus also known as a Mezzanine bus.
Computer 602 typically includes a variety of computer readable media. Such media can be any available media that is accessible by computer 602 and includes both volatile and non-volatile media, removable and non-removable media.
The system memory 606 includes computer readable media in the form of volatile memory, such as random access memory (RAM) 610, and/or non-volatile memory, such as read only memory (ROM) 612. A basic input/output system (BIOS) 614, containing the basic routines that help to transfer information between elements within computer 602, such as during start-up, is stored in ROM 612. RAM 610 typically contains data and/or program modules that are immediately accessible to and/or presently operated on by the processing unit 604.
Computer 602 may also include other removable/non-removable, volatile/non-volatile computer storage media. By way of example,
The disk drives and their associated computer-readable media provide non-volatile storage of computer readable instructions, data structures, program modules, and other data for computer 602. Although the example illustrates a hard disk 616, a removable magnetic disk 620, and a removable optical disk 624, it is to be appreciated that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes or other magnetic storage devices, flash memory cards, CD-ROM, digital versatile disks (DVD) or other optical storage, random access memories (RAM), read only memories (ROM), electrically erasable programmable read-only memory (EEPROM), and the like, can also be utilized to implement the example computing system and environment.
Any number of program modules can be stored on the hard disk 616, magnetic disk 620, optical disk 624, ROM 612, and/or RAM 610, including by way of example, an operating system 626, one or more application programs 628, other program modules 630, and program data 632. Each of such operating system 626, one or more application programs 628, other program modules 630, and program data 632 (or some combination thereof) may implement all or part of the resident components that support the distributed file system.
A user can enter commands and information into computer 602 via input devices such as a keyboard 634 and a pointing device 636 (e.g., a “mouse”). Other input devices 638 (not shown specifically) may include a microphone, joystick, game pad, satellite dish, serial port, scanner, and/or the like. These and other input devices are connected to the processing unit 604 via input/output interfaces 640 that are coupled to the system bus 608, but may be connected by other interface and bus structures, such as a parallel port, game port, or a universal serial bus (USB).
A monitor 642 or other type of display device can also be connected to the system bus 608 via an interface, such as a video adapter 644. In addition to the monitor 642, other output peripheral devices can include components such as speakers (not shown) and a printer 646 which can be connected to computer 602 via the input/output interfaces 640.
Computer 602 can operate in a networked environment using logical connections to one or more remote computers, such as a remote computing device 648. By way of example, the remote computing device 648 can be a personal computer, portable computer, a server, a router, a network computer, a peer device or other common network node, and the like. The remote computing device 648 is illustrated as a portable computer that can include many or all of the elements and features described herein relative to computer 602.
Logical connections between computer 602 and the remote computer 648 are depicted as a local area network (LAN) 650 and a general wide area network (WAN) 652. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.
When implemented in a LAN networking environment, the computer 602 is connected to a local network 650 via a network interface or adapter 654. When implemented in a WAN networking environment, the computer 602 typically includes a modem 656 or other means for establishing communications over the wide network 652. The modem 656, which can be internal or external to computer 602, can be connected to the system bus 608 via the input/output interfaces 640 or other appropriate mechanisms. It is to be appreciated that the illustrated network connections are examples and that other means of establishing communication link(s) between the computers 602 and 648 can be employed.
In a networked environment, such as that illustrated with computing environment 600, program modules depicted relative to the computer 602, or portions thereof, may be stored in a remote memory storage device. By way of example, remote application programs 658 reside on a memory device of remote computer 648. For purposes of illustration, application programs and other executable program components such as the operating system are illustrated herein as discrete blocks, although it is recognized that such programs and components reside at various times in different storage components of the computing device 602, and are executed by the data processor(s) of the computer.
Various modules and techniques may be described herein in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.
An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available media that can be accessed by a computer. By way of example, and not limitation, computer readable media may comprise “computer storage media” and “communications media.”
“Computer storage media” includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.
“Communication media” typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier wave or other transport mechanism. Communication media also includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.
One or more flowcharts are described herein and illustrated in the accompanying Figures. The ordering of acts in these flowchart(s) are examples only—these orderings can be changed so that the acts are performed in different orders and/or concurrently.
Although the description above uses language that is specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5321838 *||Feb 28, 1991||Jun 14, 1994||Hensley Billy W||Event capturing for computer software evaluation|
|US5862381 *||Nov 26, 1996||Jan 19, 1999||International Business Machines Corporation||Visualization tool for graphically displaying trace data|
|US5970439||Mar 13, 1997||Oct 19, 1999||International Business Machines Corporation||Performance monitoring in a data processing system|
|US6046751 *||Feb 5, 1998||Apr 4, 2000||Ssd Company Limited||Color graphics processor|
|US6047123 *||Mar 27, 1997||Apr 4, 2000||Hewlett-Packard Company||Methods for recording a compilable graphics call trace|
|US6055560 *||Nov 8, 1996||Apr 25, 2000||International Business Machines Corporation||System and method to provide interactivity for a networked video server|
|US6199199||Sep 16, 1998||Mar 6, 2001||International Business Machines Corporation||Presentation of visual program performance data|
|US6332212 *||Oct 2, 1997||Dec 18, 2001||Ltx Corporation||Capturing and displaying computer program execution timing|
|US6421738 *||Jul 15, 1997||Jul 16, 2002||Microsoft Corporation||Method and system for capturing and encoding full-screen video graphics|
|US6446029||Jun 30, 1999||Sep 3, 2002||International Business Machines Corporation||Method and system for providing temporal threshold support during performance monitoring of a pipelined processor|
|US6468160||Aug 27, 1999||Oct 22, 2002||Nintendo Of America, Inc.||Security system for video game system with hard disk drive and internet access capability|
|US6557167 *||Sep 3, 1999||Apr 29, 2003||International Business Machines Corporation||Apparatus and method for analyzing performance of a computer program|
|US6631423 *||Mar 31, 1998||Oct 7, 2003||Hewlett-Packard Development Company, L.P.||System and method for assessing performance optimizations in a graphics system|
|US6712704||May 15, 2002||Mar 30, 2004||Nintendo Of America Inc.||Security system for video game system with hard disk drive and internet access capability|
|US6769989||Apr 4, 2003||Aug 3, 2004||Nintendo Of America Inc.||Home video game system with hard disk drive and internet access capability|
|US6864893 *||Nov 22, 2002||Mar 8, 2005||Nvidia Corporation||Method and apparatus for modifying depth values using pixel programs|
|US20020073360 *||Feb 4, 1999||Jun 13, 2002||Bradley Lewis||Methods, systems, and articles of manufacture for analyzing performance of application programs|
|US20040003370 *||Mar 7, 2003||Jan 1, 2004||Electronic Arts Inc.||Systems and methods for implementing shader-driven compilation of rendering assets|
|US20040162137||Feb 12, 2004||Aug 19, 2004||Scott Eliott||Security system for video game system with hard disk drive and internet access capability|
|US20040201627 *||Jan 31, 2001||Oct 14, 2004||Maddocks Peter M.||Method and apparatus for analyzing machine control sequences|
|1||"Performance Analyzer+ Real World Examples" printed Sep. 16, 2003 from Sony Computer Entertainment Europe Technology Group web site (www.scee.sony.co.uk/sceesite/articles.html, PerformanceAnalyzer.pdf), 4 pages.|
|2||Ammar, et al.; "Graphic Modelling Technique For Software Execution Time Estimation"; Information and Software Technology, 1991, vol. 33, No. 2; March; pp. 151-156.|
|3||Bender, et al.; "Introduction to the Performance Analyzer for PlayStation2"; Game Developers Conference, Mar. 6-8, 2003; 57 pages.|
|4||Doing; "Hard-Tuning the PS 2", Slides presented at Game Developers Conference Europe 2002, Aug. 27-29, 2002; 36 pages.|
|5||Ikedo; "Design and Performance Evaluation of a Pixel Cache Implemented Within Application-Specific Integrated Circuits"; Visual Computer, 1996, vol. 12, No. 5, pp. 215-233.|
|6||Lemarie; "Performance Analyser Play Your Game Cycle by Cycle"; Slides presented at Australian Game Developer Conference 2002, Dec. 7, 2002; 36 pages.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7950003 *||May 24, 2011||Sony Computer Entertainment Inc.||Heads-up-display software development tool for analyzing and optimizing computer software|
|US8015551 *||Sep 6, 2011||Ntt Docomo, Inc.||Software operation modeling device, software operation monitoring device, software operation modeling method, and software operation monitoring method|
|US8219975 *||Jul 10, 2012||Microsoft Corporation||Real-time analysis of performance data of a video game|
|US8276129 *||Sep 25, 2012||Nvidia Corporation||Methods and systems for in-place shader debugging and performance tuning|
|US8566797 *||Feb 27, 2008||Oct 22, 2013||Red Hat, Inc.||Heuristic backtracer|
|US8615739 *||Apr 23, 2009||Dec 24, 2013||Hewlett-Packard Development Company, L.P.||Resource monitoring|
|US8667473 *||Oct 31, 2007||Mar 4, 2014||Microsoft Corporation||Analyzing video game performance using non-intrusive capture and storage of run-time game data|
|US8780120 *||Oct 19, 2011||Jul 15, 2014||Microsoft Corporation||GPU self throttling|
|US9013494 *||Apr 22, 2011||Apr 21, 2015||Sony Computer Entertainment Inc.||Heads-up-display software development tool|
|US9069905 *||Jul 16, 2012||Jun 30, 2015||Microsoft Technology Licensing, Llc||Tool-based testing for composited systems|
|US20070204257 *||Nov 27, 2006||Aug 30, 2007||Ntt Docomo, Inc.||Software operation modeling device, software operation monitoring device, software operation modeling method, and software operation monitoring method|
|US20090113251 *||Oct 26, 2007||Apr 30, 2009||Microsoft Corporation||Real-time analysis of performance data of a video game|
|US20090113303 *||Oct 31, 2007||Apr 30, 2009||Microsoft Corporation||Analyzing video game performance using non-intrusive capture and storage of run-time game data|
|US20090217006 *||Feb 27, 2008||Aug 27, 2009||Soren Sandmann Pedersen||Heuristic backtracer|
|US20100275184 *||Oct 28, 2010||Dor Nir||Resource monitoring|
|US20120124559 *||May 17, 2012||Shankar Narayana Kondur||Performance Evaluation System|
|US20120268470 *||Apr 22, 2011||Oct 25, 2012||Sony Computer Entertainment Inc.||Heads-up-display software development tool|
|US20130083042 *||Apr 4, 2013||Microsoft Corporation||Gpu self throttling|
|US20140019940 *||Jul 16, 2012||Jan 16, 2014||Microsoft Corporation||Tool-Based Testing For Composited Systems|
|US20150002521 *||Jun 28, 2013||Jan 1, 2015||Lockheed Martin Corporation||Externally directed gpu data|
|EP2831739A4 *||Mar 6, 2013||Jan 13, 2016||Microsoft Technology Licensing Llc||Profile data visualization|
|U.S. Classification||717/130, 345/419, 717/124, 717/125, 345/522|
|International Classification||G06T15/00, G06F9/44|
|Cooperative Classification||G06F11/323, G06T15/00|
|European Classification||G06F11/32P, G06T15/00|
|Dec 24, 2012||REMI||Maintenance fee reminder mailed|
|May 12, 2013||LAPS||Lapse for failure to pay maintenance fees|
|Jul 2, 2013||FP||Expired due to failure to pay maintenance fee|
Effective date: 20130512
|Jan 15, 2015||AS||Assignment|
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034766/0001
Effective date: 20141014