CN106776302A - Calculate method, the device of method execution time in JAVA projects - Google Patents

Abstract

The invention discloses a method for calculating the execution time of a method in a JAVA project, comprising: obtaining all bytecode files in a target directory of a specified JAVA project; obtaining a class path from the bytecode file; , create a proxy class corresponding to each class path and a corresponding proxy method; wherein, the proxy method includes a program that records the proxy start time and proxy end time of each method in the proxy class; the proxy end time and the proxy end time The proxy start time difference is obtained to obtain the corresponding execution time of each method in the target directory; this method can completely abandon the traditional manual method, thereby greatly shortening the time for finding time-consuming methods and improving the timeliness of software development and operation and maintenance , cost reduction; the invention also discloses a device for calculating the execution time of a method in a JAVA project, which has the beneficial effects above.

Description

Method and device for calculating method execution time in JAVA project

technical field

The invention relates to the technical field of data processing, in particular to a method and a device for calculating the execution time of a method in a JAVA project.

Background technique

Java is an advanced programming language launched by Sun Microsystems in May 1995. Java can run on multiple platforms, such as Windows, Mac OS, and other systems of various UNIX versions. Because of its simplicity, object-oriented, distribution, compilation and interpretation, robustness, security, portability, high performance, multithreading, dynamics, etc., the JAVA language is widely used in various industries related to information technology . The support for network applications and multimedia access it provides will also promote the web application of JAVA language on the Internet and enterprise networks. Moreover, its openness and innovation have also attracted the favor of the world's largest software technology developers.

However, in some real projects, it is often because the developer's code is not standardized or the method of calling the API is incorrect, resulting in slow program execution, which affects the user experience in the slightest, and may lead to unpredictable product risks such as system crashes. For example, when a user clicks the OK button of the software, the software does not respond or the execution result is fed back after a long period of time. When encountering such a situation, the software developer first needs to analyze the software execution process through the printed log, or through Debug debugging Track the execution process of the software in a way to locate the specific method of the specific class that consumes time in the software. This manual method is time-consuming and labor-intensive, and has certain subjectivity and blindness. Therefore, how to efficiently calculate the execution time of the JAVA method and quickly locate the problem is a technical problem to be solved by those skilled in the art.

Contents of the invention

The purpose of the present invention is to provide a method and device for calculating the execution time of a method in a JAVA project, which can completely abandon the traditional manual method, thereby greatly shortening the time for finding time-consuming methods, and improving the timeliness of software development and operation and maintenance. cut costs.

In order to solve the problems of the technologies described above, the present invention provides a method for calculating the execution time of a method in a JAVA project, said method comprising:

Obtain all bytecode files in the target directory of the specified JAVA project;

get the classpath from said bytecode file;

According to the class path, create a proxy class and a corresponding proxy method corresponding to each class path, and execute the proxy method; wherein, the proxy method includes recording the proxy start time and proxy end time of each method in the proxy class program of;

The execution time corresponding to each method in the target directory is obtained by making a difference between the proxy end time and the proxy start time.

Optionally, obtain all bytecode files in the target directory of the specified JAVA project, including:

Specify the target directory of the JAVA project;

The target directory is scanned to filter out bytecode files with a suffix of .class.

Optionally, after obtaining the execution time corresponding to each method in the target directory, further include:

Output the execution time corresponding to each method in the target directory to the designated device.

Optionally, output the execution time corresponding to each method in the target directory to the specified device, including:

Arranging the execution time corresponding to each method in the target directory in descending order according to the duration to form an output sequence;

Output the execution time corresponding to each method in the target directory to the designated device according to the output sequence.

Optionally, after obtaining the execution time corresponding to each method in the target directory, further include:

comparing the execution time with a set time threshold, and determining an execution time greater than the set time threshold;

Outputting the location information of the method corresponding to the execution time greater than the set time threshold in the target directory.

The present invention also provides a device for calculating the execution time of a method in a JAVA project, comprising:

The bytecode file obtaining module is used to obtain all bytecode files in the target directory of the specified JAVA project;

A class path obtaining module, used to obtain the class path from the bytecode file;

The proxy method execution module is used to create a proxy class corresponding to each class path and a corresponding proxy method according to the class path, and execute the proxy method; wherein, the proxy method includes records of each method in the proxy class Procedures for agency start time and agency end time;

The execution time calculation module is used to make a difference between the agent end time and the agent start time to obtain the execution time corresponding to each method in the target directory.

Optionally, the bytecode file acquisition module includes:

Specify the target directory unit, which is used to specify the target directory of the JAVA project;

The screening unit is configured to scan the target directory, and filter out bytecode files with a suffix of .class.

Optionally, the device also includes:

An output module, configured to output the execution time corresponding to each method in the target directory to a designated device.

Optionally, the output module includes:

A sorting unit, configured to sort the execution times corresponding to the methods in the target directory in descending order according to the duration to form an output sequence;

An output unit, configured to output the execution time corresponding to each method in the target directory to a designated device according to the output sequence.

Optionally, the device also includes:

A comparison module, configured to compare the execution time with a set time threshold, and determine an execution time greater than the set time threshold;

The location information output module is configured to output the location information in the target directory corresponding to the method whose execution time is greater than the set time threshold.

A method for calculating the execution time of a method in a JAVA project provided by the present invention includes: obtaining all bytecode files in the target directory of the specified JAVA project; obtaining a class path from the bytecode file; Path, create the proxy class corresponding to each class path and the corresponding proxy method; wherein, the proxy method includes a program that records the proxy start time and proxy end time of each method in the proxy class; the proxy end time and the proxy end time The starting time of the agent is made a difference to obtain the execution time corresponding to each method in the target directory;

It can be seen that this method can completely abandon the traditional manual method, automatically record the proxy start time and proxy end time of each method in the proxy class through the created proxy class and the corresponding proxy method, and obtain the corresponding execution time of each method in the target directory; Thereby, the time for finding time-consuming methods is greatly shortened, the timeliness of software development and operation and maintenance is improved, and the cost is reduced; the present invention also provides a device for calculating the execution time of methods in a JAVA project, which has the above-mentioned beneficial effects, and is not described here. Let me repeat.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

Fig. 1 is the flowchart of the method for calculating the method execution time in the JAVA project that the embodiment of the present invention provides;

Fig. 2 is the flowchart of another method for calculating the method execution time in the JAVA project provided by the embodiment of the present invention;

Fig. 3 is the block diagram of the structure of calculating the termination of the method execution time in the JAVA project provided by the embodiment of the present invention;

FIG. 4 is a structural block diagram of another calculation method execution time termination in a JAVA project provided by an embodiment of the present invention.

detailed description

The core of the present invention is to provide a method and device for calculating the execution time of a method in a JAVA project, which can completely abandon the traditional manual method, thereby greatly shortening the time for finding time-consuming methods, and improving the timeliness of software development and operation and maintenance. cut costs.

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Please refer to Fig. 1, Fig. 1 is the flow chart of the method for calculating the method execution time in the JAVA project provided by the embodiment of the present invention; Said method comprises:

S100. Obtain all bytecode files in the target directory of the specified JAVA project;

Wherein, the target directory here may be set by the user, and the user may select the target directory for execution time calculation according to his own needs. For example, it can be the directory where the JAVA project is located or specify a finer-grained directory containing bytecode files. That is, the target directory here can be a JAVA project directory or a file subdirectory with finer granularity. The number of target directories can be one or more, that is, the user can designate all directories in the JAVA project for which execution time calculation is to be performed as target directories. Therefore, this embodiment does not limit the number and size of the target directories.

Specifically, the specific process of this step is to specify the target directory, scan the target directory, and determine all the bytecode files contained in the target directory; that is, specify the directory of the JAVA project as the target directory, scan the directory, and obtain all the class files in the project File, that is, the original bytecode file. Optionally, obtaining all bytecode files in the target directory of the specified JAVA project may include:

Specify the target directory of the JAVA project;

The target directory is scanned to filter out bytecode files with a suffix of .class.

Specifically, specifying the target directory may be to determine the target directory according to the name of the target directory input by the user; wherein, the input process may be keyboard input or voice input. This embodiment does not limit the specific manner of specifying the target directory of the JAVA project. After specifying the target directory, load the files of the target directory, and filter the bytecode files with the extension .class.

Further, if the target directory does not contain a bytecode file with the suffix .class after scanning, the method for calculating the execution time of the method in the JAVA project can be terminated immediately.

S110. Obtain a class path from the bytecode file;

Specifically, the class paths included in all the extracted bytecode files are determined, where the number of class paths may be multiple, and the specific number of class paths is related to specific bytecode files.

S120. According to the class path, create a proxy class and a corresponding proxy method corresponding to each class path, and execute the proxy method; wherein, the proxy method includes recording the proxy start time and the proxy method of each method in the proxy class end time program;

S130. Taking the difference between the proxy end time and the proxy start time to obtain the execution time corresponding to each method in the target directory.

Specifically, in this step, a corresponding proxy class and a corresponding proxy method are created for each class path. For example, if the target directory contains three classpaths, and each classpath contains two methods, there are three proxy classes corresponding to the three classpaths. The three proxy classes correspond to three proxy methods, where the proxy methods are used to execute the methods in the corresponding proxy classes.

The proxy method here includes a program that records the proxy start time and proxy end time of each method in the proxy class. Using the above example to continue to illustrate, since each class path contains two methods, that is, each proxy method contains two methods, the proxy start time and proxy end time of each method in the class can be obtained. That is, in the above example, a total of six agent start times and agent end times can be obtained. That is, the JAVA proxy method in the class corresponding to each classpath records the time before execution and after execution, and marks it as the proxy start time and proxy end time; according to [proxy end time - proxy start time], the calculation is The duration of method execution in JAVA.

According to the end time of each agent and the start time of the agent, the execution time corresponding to each method in the target directory can be obtained. Here, the calculation process of the difference between the proxy end time and the proxy start time can also be performed in the proxy method, that is, the execution time of each method corresponding to the proxy method can be directly output. It may also be that there is another program in the device that calculates the execution time independently, and the execution time is calculated by taking the difference between the agent end time and the agent start time.

That is, continue to illustrate with the above example, there are three classes in the target directory, each class has two methods, that is, there are three proxy classes and corresponding proxy methods, each proxy method executes the corresponding two methods, and a total of six execution time of a method.

The specific process of this method can be to obtain the bytecode file of the target directory, obtain the class path from the bytecode file, create a proxy class and proxy method for each class path according to the above obtained class path, and record in the proxy method The start and end times of each method in this class are calculated based on [proxy end time - proxy start time] to calculate the execution duration of each JAVA method being proxied.

Based on the above technical solution, the embodiment of the present invention proposes a method for calculating the execution time of a method in a JAVA project. This method can completely abandon the traditional manual method, and automatically record the time of each method in the proxy class through the created proxy class and the corresponding proxy method. The agent start time and agent end time can be used to obtain the corresponding execution time of each method in the target directory; thus greatly shortening the time for finding time-consuming methods, improving the timeliness of software development and operation and maintenance, and reducing costs.

Based on the above embodiment, please refer to Figure 2. In order to enable developers to obtain the execution time of each method in the target directory in a more timely manner, after the execution time corresponding to each method in the target directory is obtained in the above embodiment, this embodiment can include:

S200. Obtain all bytecode files in the target directory of the specified JAVA project;

S210. Obtain a class path from the bytecode file;

S220. According to the class path, create a proxy class and a corresponding proxy method corresponding to each class path, and execute the proxy method; wherein, the proxy method includes recording the proxy start time and the proxy method of each method in the proxy class end time program;

S230. Taking the difference between the proxy end time and the proxy start time to obtain the execution time corresponding to each method in the target directory.

S240. Output the execution time corresponding to each method in the target directory to the specified device.

Specifically, after obtaining the execution time corresponding to each method in the target directory, it is sent to the designated device in time, so that the developer can obtain the execution time data in time, and then maintain the code in the JAVA project in time. The designated device here can be the developer's mobile phone, computer and other devices. The output process can be to send the execution time information to the specified device according to the path reserved by the developer. This embodiment does not limit the specified device and the quantity of the specified device.

For example, when the proxy method is run, the execution time corresponding to each method in the target directory is obtained and then sent to the user's mobile phone, so that the user can know the execution time corresponding to each method in the target directory in time. Make timely modifications to method codes that do not meet the time requirements.

Further, on the basis of outputting to the execution time specifying device, a prompt message may also be sent after the execution time data is obtained, prompting the user agent to end the execution of the method.

Wherein, for the specific content of S200 to S230, please refer to the content of S100 to S130, which will not be repeated here.

Based on the above embodiment, since the target directory specified by the user may contain many classes, each class may contain multiple methods. Therefore, the execution time corresponding to each method in the target directory obtained by this method may be a lot. If the random order is sent to the developer, the developer needs to spend time to find out whether there is a method that takes a long time, and due to the large number of execution times, it may be Omission occurs. Therefore, in this embodiment, in order to improve the reliability and efficiency of data acquisition by users. In this embodiment, outputting the execution time corresponding to each method in the target directory to the designated device may include:

Arranging the execution time corresponding to each method in the target directory in descending order according to the duration to form an output sequence;

Output the execution time corresponding to each method in the target directory to the designated device according to the output sequence.

Specifically, output is performed sequentially according to the execution time from the longest to the shortest. In this way, the method corresponding to the first execution time takes the longest, and may be the method that does not meet the execution time requirement the least. So that developers can obtain the most valuable information at the first time. Because the method with a small execution time is basically a method that meets the requirements and does not require code modification. On the contrary, the method that takes a long time is very likely to require maintenance by developers. Even the data that developers care about most can be obtained in the shortest possible time. And it can also improve the processing speed of the developer. For example, when the execution time of the first one meets the requirements, the subsequent ones will all meet the time requirements. Developers don't need to look at the code of subsequent methods one by one. Further improve the timeliness of software development and operation and maintenance, and reduce costs.

The following example illustrates the above process:

Step 1. Specify the JAVA project directory to be searched or a subdirectory of a file at a finer granularity as the target directory.

Step 2. Search for the JAVA bytecode file with the filter suffix .class for the target directory specified in step 1. If it exists, execute step 3. If it does not exist, exit.

Step 3. According to the JAVA bytecode file found in step 2, analyze and obtain the corresponding class path.

Step 4. Create a proxy of the class, and create proxy methods for all the methods in it, and add a method program to record the proxy start time and proxy end time in the proxy method.

Step 5. Calculate the execution time of the method according to [agent end time-agent start time].

Step 6. Arrange in descending order of execution time, and output the execution time corresponding to each method.

Based on any of the above embodiments, in order to further improve the availability of the calculated execution time data, after obtaining the execution time corresponding to each method in the target directory, this embodiment may further include:

comparing the execution time with a set time threshold, and determining an execution time greater than the set time threshold;

Outputting the location information of the method corresponding to the execution time greater than the set time threshold in the target directory.

Wherein, the setting time threshold here can be set by the developer according to the requirements of the actual JAVA project. Therefore, this embodiment does not limit the value of the set time threshold.

Specifically, in order to further filter out the available information from all the execution time, in this embodiment, the set time threshold can be used as the filter condition for screening; that is, the method corresponding to the execution time that does not meet the time requirement is screened out, that is, the output is greater than the specified The execution time of the set time threshold corresponds to the location information of the method in the target directory. Developers can quickly locate the original code location that needs to be maintained. The location information here can be the code that directly outputs the execution time corresponding method greater than the set time threshold, or the position in the JAVA project that outputs the execution time corresponding method greater than the set time threshold (such as which directory, In which subdirectory, in which class, the number of lines from the beginning to the end of the corresponding code, etc.).

Based on the above technical solution, the embodiment of the present invention proposes a method for calculating the execution time of a method in a JAVA project. This method can completely abandon the traditional manual method, thereby greatly shortening the time for finding time-consuming methods. Moreover, based on this method The obtained method execution time, combined with the configuration of the execution set time threshold, can locate the code fragments that need to be optimized in the software execution process in time, and quickly feed back to the designated developer for optimization and repair. It can efficiently find classes and methods in JAVA projects that take a long time to execute, improve the timeliness of software development and operation and maintenance, and reduce costs.

The following is an introduction to the device for calculating the execution time of a method in a JAVA project provided by an embodiment of the present invention. The device for calculating the execution time of a method in a JAVA project described below and the method for calculating the execution time of a method in a JAVA project described above can be referred to in correspondence.

Please refer to Fig. 3, Fig. 3 is the structural block diagram of the termination of the calculation method execution time in the JAVA project that Fig. 3 provides for the embodiment of the present invention; This device can comprise:

Bytecode file obtaining module 100, used to obtain all bytecode files in the target directory of the specified JAVA project;

A class path obtaining module 200, configured to obtain a class path from the bytecode file;

The proxy method execution module 300 is used to create a proxy class corresponding to each class path and a corresponding proxy method according to the class path, and execute the proxy method; wherein, the proxy method includes recording each method in the proxy class The procedures for the proxy start time and proxy end time;

The execution time calculation module 400 is configured to make a difference between the agent end time and the agent start time to obtain the execution time corresponding to each method in the target directory.

Based on the foregoing embodiments, the bytecode file acquisition module 100 may include:

Specify the target directory unit, which is used to specify the target directory of the JAVA project;

The screening unit is configured to scan the target directory, and filter out bytecode files with a suffix of .class.

Based on any of the above embodiments, please refer to FIG. 4, the device may also include:

The output module 500 is configured to output the execution time corresponding to each method in the target directory to a specified device.

Based on the foregoing embodiments, the output module 500 may include:

A sorting unit, configured to sort the execution times corresponding to the methods in the target directory in descending order according to the duration to form an output sequence;

An output unit, configured to output the execution time corresponding to each method in the target directory to a designated device according to the output sequence.

Based on any of the above embodiments, the device may further include:

A comparison module, configured to compare the execution time with a set time threshold, and determine an execution time greater than the set time threshold;

The location information output module is configured to output the location information in the target directory corresponding to the method whose execution time is greater than the set time threshold.

Each embodiment in the description is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for the related information, please refer to the description of the method part.

Professionals can further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of the two. In order to clearly illustrate the possible For interchangeability, in the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be directly implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

The method and device for calculating the execution time of a method in a JAVA project provided by the present invention have been introduced in detail above. In this paper, specific examples are used to illustrate the principle and implementation of the present invention, and the descriptions of the above embodiments are only used to help understand the method and core idea of the present invention. It should be pointed out that for those skilled in the art, without departing from the principle of the present invention, some improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

Claims (10)

1. a method for calculating the method execution time in the JAVA project, is characterized in that, described method comprises: Obtain all bytecode files in the target directory of the specified JAVA project; get the classpath from said bytecode file; According to the class path, create a proxy class and a corresponding proxy method corresponding to each class path, and execute the proxy method; wherein, the proxy method includes recording the proxy start time and proxy end time of each method in the proxy class program of; The execution time corresponding to each method in the target directory is obtained by making a difference between the proxy end time and the proxy start time. 2. The method according to claim 1, wherein obtaining all bytecode files in the target directory of the specified JAVA project comprises: Specify the target directory of the JAVA project; The target directory is scanned to filter out bytecode files with a suffix of .class. 3. The method according to claim 2, characterized in that, after obtaining the execution time corresponding to each method in the target directory, further comprising: Output the execution time corresponding to each method in the target directory to the designated device. 4. The method according to claim 3, wherein outputting the execution time corresponding to each method in the target directory to the designated device includes: Arranging the execution time corresponding to each method in the target directory in descending order according to the duration to form an output sequence; Output the execution time corresponding to each method in the target directory to the designated device according to the output sequence. 5. The method according to any one of claims 1-4, characterized in that, after obtaining the execution time corresponding to each method in the target directory, further comprising: comparing the execution time with a set time threshold, and determining an execution time greater than the set time threshold; Outputting the location information of the method corresponding to the execution time greater than the set time threshold in the target directory. 6. A device for calculating the execution time of a method in a JAVA project, characterized in that it comprises: The bytecode file obtaining module is used to obtain all bytecode files in the target directory of the specified JAVA project; A class path obtaining module, used to obtain the class path from the bytecode file; The proxy method execution module is used to create a proxy class corresponding to each class path and a corresponding proxy method according to the class path, and execute the proxy method; wherein, the proxy method includes records of each method in the proxy class Procedures for agency start time and agency end time; The execution time calculation module is used to make a difference between the agent end time and the agent start time to obtain the execution time corresponding to each method in the target directory. 7. The device according to claim 6, wherein the bytecode file acquisition module comprises: Specify the target directory unit, which is used to specify the target directory of the JAVA project; The screening unit is configured to scan the target directory, and filter out bytecode files with a suffix of .class. 8. The device according to claim 7, further comprising: An output module, configured to output the execution time corresponding to each method in the target directory to a designated device. 9. The device according to claim 8, wherein the output module comprises: A sorting unit, configured to sort the execution times corresponding to the methods in the target directory in descending order according to the duration to form an output sequence; An output unit, configured to output the execution time corresponding to each method in the target directory to a designated device according to the output sequence. 10. The device according to any one of claims 6-9, further comprising: A comparison module, configured to compare the execution time with a set time threshold, and determine an execution time greater than the set time threshold; The location information output module is configured to output the location information in the target directory corresponding to the method whose execution time is greater than the set time threshold.