JP2008310748A - Task execution time recording device, task execution time recording method, and task execution recording program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a task execution time recording device capable of recording an actual execution time period of tasks with a simple configuration, low processing load, and a small amount of memory, in a software comprising a plurality of tasks; method; and program. <P>SOLUTION: The task execution time recording device includes: a timing storing part 300 which, when a start-up data or completion data of a task occurs, stores the occurrence time of the data generated just therebefore as a timing data; a first execution time calculating part 420 which, each time the start-up data occurs, calculates the execution time period of an interrupted task using the timing data and the start-up time of the started task; a second execution time calculating part 430 which, each time the completion data occurs, calculates the execution time period of the completed task using the timing data and the completion time period of the completed task; and an actual execution time calculating part 410 which calculates the actual execution time period of each task using calculation results of the first and second execution time calculating parts 420 and 430. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an apparatus for recording the execution time of each task of software having a plurality of tasks.

  Conventionally, in the verification of software having a plurality of tasks, the processing execution time is used for checking whether or not there is an illegal operation and whether the processing completion requirement has not been met. As a method for calculating the processing execution time, a common timer is used to calculate the processing execution time from the start to the end of processing of the measurement target task, or the actual execution time (actual execution time for each task). ) For calculating the actual execution time for each task.

  Specifically, as a method for calculating the processing execution time using the common timer, for example, the value of the common time measurement timer that always counts is recorded at the start and end of the processing by the measurement target task, and the difference is processed. There is a method of setting the execution time. In this method, the configuration is simple and the processing load for measurement is small. However, if another task is interrupted and executed during execution of the measurement target task, the time including the execution time of the other task is also measured. Therefore, the time during which the measurement target task is actually executed cannot be calculated.

  On the other hand, as a method for calculating the actual execution time, for example, a timer is provided for each individual task, the timer is stopped when the task is interrupted, and the timer is restarted when the interrupt is ended (returned). A method for measuring the execution time can be mentioned. This method eliminates the time at which the task was interrupted and can only measure the time at which each task was actually processed, but it must provide a means for measuring each task, and in addition, the task suspension / It is necessary to monitor the return, and the processing load for measurement increases.

Therefore, a technique for calculating the actual execution time for each task with one time measurement timer has been proposed (see, for example, Patent Document 1). In the apparatus of Patent Document 1, the start and end times of the task from the start to the end of the task and the switching time of other high priority tasks that interrupt the task are recorded, and the time from the start to the end Then, the actual execution time of each task is calculated by reducing the execution time of the high priority tasks in descending order of priority.
JP 2002-323984 A

  However, in the apparatus of Patent Document 1, from the start to the end of a task, the start and end times of the task and the switching time of other high priority tasks that interrupt the task are recorded, and then the high priority task Due to the technique of reducing the processing time, there is a problem that when the number of tasks interrupted from the start to the end of the task increases, the amount of memory for storing the time increases.

  In view of the above circumstances, the present invention is a task execution time recording device capable of calculating and recording the actual execution time of each task with a simple configuration, a low processing load, and a small amount of memory in software having a plurality of tasks. An object is to provide a task execution time recording method and a task execution time recording program.

  In order to achieve this object, a task execution time recording device of the present invention is a task execution time recording device that records the execution time of each task of software having a plurality of tasks, and when the activation data of each task is generated A startup information detecting unit that detects the startup time that is the start time and the type of the started task as startup information, and an end time that is the time when the end data of each task is generated, respectively, as end information An end information detection unit; a timing data storage unit that stores, as timing data, a generation time of data generated immediately before task activation data and end data when task activation data or termination data is generated; and a task Each time the activation data is generated, it is determined whether or not there is a task that is interrupted by the activation. A first execution time calculation unit that calculates the execution time of the suspended task using the timing data stored in the timing data storage unit and the activation time of the activated task; A second execution time calculation unit that calculates the execution time of the completed task using the timing data stored in the timing data storage unit and the end time of the completed task each time completion data is generated And an actual execution time calculation unit that calculates the actual execution time of each task using the calculation results of the first and second execution time calculation units (first invention).

  In the task execution time recording device of the first invention, in software having a plurality of tasks, task interruption (the task is activated and other tasks being executed are interrupted) / return (the interrupted task is terminated, The execution of another task that has been suspended is resumed). When each task is activated, activation data is generated, and the activation information detection unit detects the activation time of each task and the type of the activated task as activation information. Further, when each task ends, end data is generated, and the end information detecting unit detects the end time of each task as the end information. At this time, the return to the interrupt uniquely occurs in the software. In other words, when a measurement target task is interrupted by another task interrupt (when a task is switched), the start time of the other task that interrupted the measurement target task is the measurement target task suspension time. At the same time, the end time of the other task that interrupts the task to be measured becomes the restart time of the task to be measured.

  Therefore, when the task start data or end data is generated by the timing data storage unit, the generation time of the data generated immediately before the task start data and end data is stored as timing data. Then, every time task activation data is generated, the first execution time calculation unit determines whether there is a task interrupted by the activation, and if there is an interrupted task, the timing data and the activation The execution time of the interrupted task is calculated using the start time of the task. That is, in this case, the timing data indicates the activation time or resumption time of the task to be interrupted. Therefore, using the timing data and the start time of the started task (task switching time), it is possible to easily and sequentially calculate the execution time of the interrupted task from the start or restart to the interrupt. Can do.

  The second execution time calculation unit calculates the execution time of the completed task by using the timing data and the end time of the completed task every time task completion data is generated. That is, in this case, the timing data indicates the start time or restart time of the finished task. Therefore, by using the timing data and the end time of the completed task (task switching time), it is possible to easily and sequentially calculate the execution time of the completed task from the start or restart to the end. it can.

  That is, the execution time of each task is sequentially calculated by the first and second execution time calculation units only by measuring the start time and end time of each task. Then, using the calculation results of the first and second execution time calculation units, the actual execution time (actual execution time) of each task excluding the time interrupted by other tasks by the actual execution time calculation unit is obtained. Calculated. At this time, since the execution time of each task is sequentially calculated by the first and second execution time calculation units, the actual execution of each task is recorded without recording all the start time and end time of each task. It is possible to calculate the time.

  Therefore, without providing a timer for each task or recording all the start time and end time of each task, the actual execution time of each task can be easily determined using only the task switching time and its timing data. It is possible to calculate. Therefore, according to the present invention, in software having a plurality of tasks, the actual execution time of each task can be calculated and recorded with a simple configuration, a low processing load, and a small amount of memory.

  In the task execution time recording device of the first invention, every time task activation data is generated, it is determined whether or not there is a task interrupted by the activation. Task type hierarchy generated by stacking the activated task types on top of the activated task types and, when there is no task to be interrupted, the task type activated as the lowest layer A type hierarchy generation unit, and a task type deletion unit that deletes the highest task type of the task type hierarchy generated by the task type hierarchy generation unit each time task completion data is generated, In the execution time calculation unit, it is preferable that the task type deleted by the task type deletion unit is specified as a completed task when the type of the completed task is specified The second aspect of the present invention).

  That is, tasks are switched by interrupt / return and a return to the interrupt occurs uniquely, so that the activated task can be appropriately expressed as a task type hierarchy. In the task type hierarchy, the completed task is easily identified from the type of task deleted by the task type deletion unit.

  Next, the task execution time recording method of the present invention is a task execution time recording method for recording the execution time of each task of software having a plurality of tasks, and the start time is the time when the start data of each task is generated An activation information detection step for detecting the time and the type of the activated task as activation information, and an end information detection step for detecting an end time, which is the time when the end data of each task is generated, as the termination information; When a task start data or end data is generated, a timing storage step for storing the generation time of the data generated immediately before the task start data and the end data as timing data, and task start data are generated. Each time, it is determined whether there is a task that is interrupted by the activation, and if there is a task that is interrupted, A first execution time calculating step for calculating an execution time of the interrupted task using the timing data stored in the timing data storage step and the start time of the started task; A second execution time calculating step of calculating the execution time of the completed task using the timing data stored in the timing data storage step and the end time of the completed task each time it occurs, An actual execution time calculating step of calculating the actual execution time of each task using the calculation results of the first and second execution time calculating steps (third invention).

  According to the task execution time recording method of the third invention, as described with respect to the task execution time recording device of the first invention, the task switching time and its timing data can be obtained only by measuring the start time and the end time of each task. The execution time of each task is sequentially calculated by the first and second execution time calculation steps. Then, without recording all the start time and end time of each task, the actual execution time calculation step was interrupted by another task using the calculation results of the first and second execution time calculation steps. The actual execution time of each task excluding the time is calculated. Therefore, without providing a timer for each task or recording all the start time and end time of each task, the actual execution time of each task can be easily determined using only the task switching time and its timing data. It is possible to calculate. Therefore, according to the present invention, in software having a plurality of tasks, the actual execution time of each task can be calculated and recorded with a simple configuration, a low processing load, and a small amount of memory.

  Next, the task execution time recording program of the present invention is a task execution time recording program for causing a computer to execute a process for recording the execution time of each task of software having a plurality of tasks, and the startup data of each task The start time, which is the start time of the task, and the start information detection process for detecting the type of the started task as start information, and the end time, which is the end time of the end data for each task, is detected as the end information. Information detection processing, timing storage processing for storing, as timing data, the generation time of the data generated immediately before task activation data and completion data when task activation data or termination data occurs, and task activation Each time data is generated, it is determined whether there is a task that is interrupted by the activation. When there is a task to be executed, a first execution time calculation process for calculating an execution time of the suspended task using the timing data stored by the timing data storage process and the start time of the started task And the execution time of the completed task is calculated using the timing data stored by the timing data storage process and the end time of the completed task each time task completion data is generated. A function of causing the computer to execute an execution time calculation process and an actual execution time calculation process for calculating an actual execution time of each task using the calculation results of the first and second execution time calculation processes; Features (fourth invention).

  According to the task execution time recording program of the fourth aspect of the invention, it is possible to cause the computer to execute processing that can achieve the effects described with respect to the task execution time recording apparatus of the first aspect of the invention.

  An embodiment of the task execution time recording apparatus of the present invention will be described with reference to FIGS. FIG. 1 is a functional block diagram of the task execution time recording apparatus of the present embodiment, and FIG. 2 is an explanatory diagram showing task switching in software that is a measurement target of the task execution time recording apparatus of FIG. FIG. 4 is an explanatory diagram showing an example of task type hierarchy data in the task switching of FIG.

  As shown in FIG. 1, the task execution time recording apparatus of this embodiment is configured by a computer (comprising a CPU, ROM, RAM, I / O, etc.) 1 on which software to be measured is mounted. Note that the task execution time recording device may be configured by another computer that is communicably connected to the computer 1 on which the software is installed. The computer 1 is mounted on, for example, a vehicle (not shown), and constitutes an ECU that controls the operation of the vehicle, a navigation device, and the like.

  The task execution time recording device records the actual execution time of each task of multitask software (software having a plurality of tasks). This task execution time recording device includes, as its functions, a task switching unit 10, a time measurement timer 110, a startup information detection unit 120, an end information detection unit 130, a task type hierarchy generation unit 220, a task type hierarchy storage unit 210, and a task type. A deletion unit 230, a timing data storage unit 300, an actual execution time calculation unit 410, a first execution time calculation unit 420, a second execution time conversion output unit 430, a measurement result data storage unit 500, and a reader 600 are provided. Yes. Each of these functions may be constituted by one computer or may be constituted by a plurality of independent computers.

  Each of these functions is realized by causing the computer 1 to execute a program previously installed in the memory of the computer 1. This program includes the task execution time recording program of the present invention. The program may be stored in the memory via a recording medium such as a CD-ROM. Alternatively, the program may be distributed or broadcast from an external server via a network or an artificial satellite, received by a communication device mounted on a vehicle or the like, and stored in a memory.

  The task switching unit 10 starts and ends a plurality of tasks included in the software, and switches each task. When starting and ending a task, task start data and end data are generated, respectively. The task switching unit 10 is incorporated in software that is a measurement target.

  The time measurement timer 110 measures the start time and end time of each task performed by the task switching unit 10. The activation time is the time when the activation data of each task generated when the task is activated by the task switching unit 10 is generated. The end time is the time when the end data of each task generated when the task is ended by the task switching unit 10 is generated.

  The activation information detection unit 120 detects the activation time of a task measured by the time measurement timer 110 and the type of the activated task as activation information each time task activation data is generated. Specifically, the activation information detection unit 120 outputs, as an activation signal, activation information including a time obtained from the time measurement timer 110 at a task activation timing and a symbol for identifying the type of the activation task.

  The end information detection unit 130 detects the end time of the task measured by the time measurement timer 110 as end information each time task end data is generated. Specifically, the end information detection unit 130 outputs, as an end signal, end information including a time obtained from the time measurement timer 110 at a task end timing and a symbol for identifying the type of the task that has ended.

  Each time task activation data is generated, the task type hierarchy generation unit 220 determines whether there is a task interrupted by the activation, and if there is no task interrupted, the task type hierarchy generation unit 220 determines the type of the activated task. When there is a task to be interrupted at the lowest level, a task type hierarchy is generated that is generated by stacking the activated task types on the interrupted task types. Specifically, the task hierarchy generation unit 220 generates task type hierarchy data based on the activation signal input from the activation information detection unit 120, and stores the generated data in the task type hierarchy storage unit 210. At the same time, the task type hierarchy generation unit 220 outputs the generated data to the first execution time calculation unit 420 together with the activation time included in the activation signal.

  The task type deletion unit 230 deletes the task type at the top of the task type hierarchy generated by the task type hierarchy generation unit 220 every time task completion data is generated. Specifically, the task type deletion unit 230 reads out the task type hierarchy data from the task type hierarchy storage unit 210 based on the end signal input from the end information detection unit 130, and the highest task of the task type hierarchy data As a deletion target data, data that is deleted is generated, and the generated data is stored in the task type hierarchy storage unit 210. At the same time, the task type deletion unit 230 outputs the deletion target data (the type of the deleted task) together with the end time included in the end signal to the second execution time calculation unit 430.

  The timing data storage unit 300 stores, as timing data, the generation time of data generated immediately before task activation data and completion data when task activation data or termination data is generated. That is, if the data generated immediately before is the task activation data, the timing data storage unit 300 stores the generation time (activation time) of the activation data as timing data, and the data generated immediately before is the task end data. If there is, the generation time (end time) of the end data is stored as timing data. Specifically, signals output from the activation information detection unit 110 and the end information detection unit 120 are input to the timing data storage unit 300 according to the signal generation timing. The timing data storage unit 300 uses this input signal, uses the time information of the input data immediately before the data input timing as timing data, and outputs the timing data to the first and second execution time calculation units 420 and 430.

  Each time task activation data is generated, the first execution time calculation unit 420 determines whether there is a task interrupted by the activation, and if there is an interrupted task, the first execution time calculation unit 420 stores the task in the timing data storage unit 300. The execution time of the suspended task is calculated using the stored timing data and the activation time of the activated task. At this time, the first execution time calculation unit 420 determines from the task type hierarchy data output from the task type hierarchy generation unit 220 whether there is a task to be interrupted and determines the type of task to be interrupted. Identify.

  Each time task completion data is generated, the second execution time calculation unit 430 uses the timing data stored in the timing data storage unit 300 and the completion time of the completed task to determine the completed task. Calculate the execution time. At this time, the second execution time calculation unit 430 identifies the task type deleted by the task type deletion unit 230 as a completed task.

  The actual execution time calculation unit 410 calculates the actual execution time of each task using the calculation result by the first execution time calculation unit 420 and the calculation result by the second execution time calculation unit 430. The actual execution time calculated by the actual execution time calculation unit 410 is stored in the measurement result data storage unit 500 as measurement result data of the actual execution time of each task. Then, the measurement result data stored in the measurement result data storage unit 500 is read out via the reader 600.

  The task type hierarchy storage unit 210, the timing data storage unit 300, and the measurement result data storage unit 500 are storage devices such as a RAM and an HDD.

  Next, the operation (task execution time recording process) of the task execution time recording device of this embodiment will be described. Hereinafter, in the multitask software to be measured, a case where task switching occurs as shown in FIG. 2 by the task switching unit 10 will be described as an example. In the example of FIG. 2, the multitask software that is the measurement target has three types of tasks A, B, and C, and the priority of these tasks is tasks C, B, and A in descending order. In FIG. 2, the horizontal axis indicates time, and the task A execution state, task B execution state, and task C execution state are shown in order from the bottom of FIG. 2. In FIG. 2, the time during which each task is actually executed is indicated by hatching.

  First, an example of task switching shown in FIG. 2 will be described. In this task switching example, task A is executed from the idle state, and task A is interrupted twice by task B during execution. In addition, task B that interrupted task A for the first time is further interrupted by task C. After task A ends, task B is executed from the idle state, and task B is interrupted by task C during execution.

  In this task switching example, the time from the start to the end of task A is t8-t1, but the time during which task A is actually processed (actual execution time) is (t2-t1) + (t6 -t5) + (t8-t7). Similarly, the actual execution time of task B is (t3-t2) + (t5-t4) and t7-t6 and (t10-t9) + (t12-t11). The actual execution time of task C is t4-t3 and t11-t10.

  Here, in the present embodiment, the activation information detection unit 120 continuously outputs S indicating activation, the name of the task, and the activation time as activation signals. Further, the end information detection unit 130 continuously outputs E indicating the end, the name of the task, and the end time as an end signal. Then, signals output from the activation information detection unit 120 and the end information detection unit 130 are input to the timing data storage unit 300 according to the signal generation timing.

For example, the activation information output by the activation information detection unit 120 in response to task switching in FIG.
{SA, t1, SB, t2, SC, t3, SB, t6, SB, t9, SC, t10}
It becomes. Also, the end signal output by the end information detection unit 130 in response to the task switching in FIG.
{EC, t4, EB, t5, EB, t7, EA, t8, EC, t11, EB, t12}
It becomes. A signal input to the timing data storage unit 300 in response to the task switching in FIG.
{SA, t1, SB, t2, SC, t3, EC, t4, EB, t5, SB, t6, EB, t7, EA, t8, SB, t9, SC, t10, EC, t11, EB, t12}
It becomes.

  Next, the task execution time recording process will be specifically described with reference to the example of FIG. First, at time t1, task A is activated by task switching unit 10 to generate activation data, and activation information detection unit 120 acquires time information t1 from time measurement timer 110 as the activation time of task A. Then, activation information detection section 120 outputs a signal that can identify the type of task and its activation time {SA, t1} as an activation signal. The output activation signal is input to the task type hierarchy generation unit 220 and the timing data storage unit 300. Since there is no task interrupted by task A, task hierarchy generation unit 220 generates a hierarchical structure with task A as the lowest layer and stores it in task type hierarchy storage unit 210. Further, the timing data storage unit 300 does not store timing data because there is no data generated immediately before. Since there is no task interrupted by task A, the first execution time calculation unit 420 does not calculate the execution time.

  Next, at time t2, task B is activated by task switching unit 10 to generate activation data, task A is interrupted, and activation information detection unit 120 receives time information t2 from time measurement timer 110 as the activation time of task B. To get. Then, the activation information detection unit 120 outputs a signal that can identify the type of task and its activation time {SB, t2} as an activation signal. The output activation signal is input to the task type hierarchy generation unit 220 and the timing data storage unit 300.

  The task hierarchy generation unit 220 reads the task type hierarchy data from the task type hierarchy storage unit 210, determines that there is a task A as a task interrupted by the activation of task B, and stacks task B on top of task A. Generate task type hierarchy data. The task types A and B are appropriately represented by the task type hierarchy data. The task type hierarchy data is stored in the task type hierarchy storage unit 210 and output to the first execution time calculation unit 420 together with the activation time t2. Further, the timing data storage unit 300 stores the generation time t1 of the immediately preceding activation data as timing data.

  The first execution time calculation unit 420 determines from the task type hierarchy data output from the task type hierarchy generation unit 220 that there is a task A as a task interrupted by the activation of the task B. Then, the first execution time calculation unit 420 uses the timing data t1 stored in the timing data storage unit 300 and the activation time t2 of the activated task B to execute the suspended task A execution time t2-t1. Is calculated. Thereby, using only the timing data and task switching time, the execution time of the interrupted task A from the start to the interrupt is easily calculated. Then, the first execution time calculation unit 420 outputs t2−t1 as the execution time of task A to the actual execution time calculation unit 410.

  Next, at time t3, task switching unit 10 activates task C, generates activation data, interrupts task B, and performs the same processing as at time t2. That is, the activation information detection unit 120 outputs {SC, t3} as an activation signal. The task hierarchy generation unit 220 determines that there is a task B as a task interrupted by the activation of the task C, and generates task type hierarchy data in which the task C is stacked above the task B. At this time, task type hierarchy data as illustrated in FIG. 3 is generated. Further, the timing data storage unit 300 stores the generation time t2 of the immediately preceding activation data as timing data. The first execution time calculation unit 420 calculates the execution time t3-t2 of the suspended task B using the timing data t2 and the activation time t3 of the activated task C. Thus, using only the timing data and the task switching time, the execution time of the interrupted task B from the start to the interrupt is easily calculated. Then, the first execution time calculation unit 420 outputs t3-t2 as the execution time of task B to the actual execution time calculation unit 410.

  Next, at time t4, task C is ended by task switching unit 10 to generate end data, and end information detection unit 130 acquires time information t4 from time measurement timer 110 as the end time of task C. Then, the end information detection unit 130 outputs a signal that can identify the type of task and its end time as an end signal {EC, t4}. The output end signal is input to the task type deletion unit 230 and the timing data storage unit 300.

  The task type deletion unit 230 reads the task type hierarchy data from the task type hierarchy storage unit 210, and stores the data obtained by deleting the task C, which is the highest-level task, in the task type hierarchy storage unit 300 as task type hierarchy data. At this time, the task type hierarchy data as illustrated in FIG. 4 is stored in the task type hierarchy storage unit 300. The deletion target data representing the deleted task C is output to the second execution time calculation unit 430 together with the end time t4. Further, the timing data storage unit 300 outputs the generation time t3 of the immediately preceding activation data as timing data.

  The second execution time calculation unit 430 calculates an execution time t4-t3 from the task end time t4 and the timing data t3. Thereby, using only the timing data and the task switching time, the execution time of the task C to be ended from the start to the end is easily calculated. Then, the second execution time calculation unit 430 outputs this value to the actual execution time calculation unit 410 as the execution time of the task C deleted by the task type deletion unit 230. The actual execution time calculation unit 410 calculates the actual execution time t3-t2 of the task C from the calculation result of the second execution time calculation unit 430. As a result, the actual execution time of task C can be easily calculated without recording all of the start time and end time of each task.

  Next, at time t5, task switching unit 10 ends task B and generates end data, and processing similar to that at time t4 is performed. That is, the end information detection unit 130 outputs an end signal {EB, t5}. The task type deletion unit 230 reads the task type hierarchy data from the task type hierarchy storage unit 210, and stores the data obtained by deleting the task B, which is the highest-level task, in the task type hierarchy storage unit 210 as task type hierarchy data. The timing data storage unit 300 stores the generation time t4 of the last end data as timing data. Then, the second execution time calculation unit 430 calculates an execution time t5-t4 from the task end time t5 and the timing data t4. Thereby, using only the timing data and the task switching time, the execution time of the task B to be ended from the restart to the end is easily calculated. Then, the second execution time calculation unit 430 outputs this value to the actual execution time calculation unit 410 as the execution time of the task B deleted by the task type deletion unit 230. The actual execution time calculation unit 410 is based on the execution time t3-t2 from the start to the end of task B calculated by the start of the task C and the execution time t5-t4 from the restart to the end calculated by the end of the task B. Then, the actual execution time of task B (t3-t2) + (t5-t4) is calculated. As a result, the actual execution time of task B can be easily calculated without recording all the start time and end time of each task.

  Thereafter, at times t6 to t12, the actual execution time of each task can be calculated from only the task switching signal (start signal / end signal) and timing data by the same processing. The calculated actual execution time is stored in the measurement result data storage unit 500 as measurement result data and can be read out via the reader 200.

  With the above processing, the actual execution time of each task A, B, C can be obtained without recording all the start time and end time of each task A, B, C using one time measurement timer 110. It can be easily calculated using only the task switching time and its timing data. Therefore, according to the present invention, the actual execution time of each task of software having a plurality of tasks can be calculated and recorded with a simple configuration, a low processing load, and a small amount of memory.

  In the present embodiment, the first execution time calculation unit 420 identifies the type of task to be interrupted from the task type hierarchy data output from the task type hierarchy generation unit 220, but other embodiments The timing data storage unit 300 stores the task type as timing data in addition to the generation time of the data generated immediately before the task start data and end data, and from the stored task type The type of task to be interrupted may be specified.

The functional block diagram of the task execution time recording device which is embodiment of this invention. Explanatory drawing which shows the task switching in the software which is a measuring object of the task execution time recording device of FIG. Explanatory drawing which shows the example of the task kind hierarchy data in the task switching of FIG. Explanatory drawing which shows the other example of the task kind hierarchy data in the task switching of FIG.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... Task switching part, 110 ... Time measurement timer, 120 ... Activation information detection part, 130 ... End information detection part, 210 ... Task type hierarchy memory | storage part, 220 ... Task type hierarchy production | generation part, 230 ... Task type deletion part, 300 ... timing data storage unit, 410 ... actual execution time calculation unit, 420 ... first execution time calculation unit, 430 ... second execution time calculation unit, 500 ... measurement result data storage unit, 600 ... reader.

Claims (4)

A task execution time recording device for recording the execution time of each task of software having a plurality of tasks,
An activation information detector that detects the activation time, which is the time when the activation data of each task is generated, and the type of the activated task, as activation information;
An end information detection unit for detecting an end time, which is a time when the end data of each task is generated, as end information;
A timing data storage unit that stores, as timing data, an occurrence time of data generated immediately before task activation data or end data when task activation data or termination data occurs;
Each time task activation data is generated, it is determined whether there is a task interrupted by the activation. If there is a task interrupted, the timing data stored in the timing data storage unit and the activated A first execution time calculation unit that calculates the execution time of the suspended task using the task activation time;
The second execution time for calculating the execution time of the completed task using the timing data stored in the timing data storage unit and the completion time of the completed task each time task completion data is generated A calculation unit;
A task execution time recording apparatus, comprising: an actual execution time calculation unit that calculates an actual execution time of each task using the calculation results of the first and second execution time calculation units. In the task execution time recording device according to claim 1,
Each time task activation data is generated, it is determined whether or not there is a task to be interrupted by the activation. A task type hierarchy generation unit that generates a task type hierarchy generated by stacking the activated task types on the interrupted task types,
A task type deletion unit that deletes the task type at the top of the task type hierarchy generated by the task type hierarchy generation unit each time task end data is generated;
The task execution time recording device characterized in that when the second execution time calculation unit specifies the type of the completed task, the task type deleted by the task type deletion unit is specified as a completed task. . A task execution time recording method for recording the execution time of each task of software having a plurality of tasks,
An activation information detection step of detecting the activation time, which is the time when the activation data of each task is generated, and the type of the activated task as activation information;
An end information detection step for detecting an end time, which is a time when the end data of each task is generated, as end information;
A timing storage step for storing, as timing data, the generation time of the data generated immediately before the task start data or the end data when task start data or end data is generated;
Each time task activation data is generated, it is determined whether there is a task interrupted by the activation. If there is a task interrupted, the timing data stored in the timing data storage step and the activated A first execution time calculating step of calculating an execution time of the suspended task using the task activation time;
The second execution time for calculating the execution time of the completed task using the timing data stored in the timing data storage step and the end time of the completed task each time task completion data is generated A calculation step;
A task execution time recording method comprising: an actual execution time calculation step of calculating an actual execution time of each task using the calculation results of the first and second execution time calculation steps. A task execution time recording program for causing a computer to execute a process of recording the execution time of each task of software having a plurality of tasks,
An activation information detection process for detecting the activation time, which is the time when the activation data of each task is generated, and the type of the activated task, as activation information;
An end information detection process for detecting an end time, which is a time when the end data of each task is generated, as end information;
A timing storage process for storing, as timing data, the generation time of the data generated immediately before task activation data or completion data when task activation data or termination data occurs;
Each time task activation data is generated, it is determined whether there is a task interrupted by the activation. If there is an interrupted task, the timing data stored by the timing data storage process and the activated A first execution time calculation process for calculating the execution time of the suspended task using the task activation time;
The second execution time for calculating the execution time of the completed task using the timing data stored by the timing data storage process and the end time of the completed task every time task completion data is generated Calculation process,
A task execution time having a function of causing the computer to execute an actual execution time calculation process for calculating an actual execution time of each task using the calculation results obtained by the first and second execution time calculation processes. Recording program.

Images