CN110377383B - Method, device and storage medium for checking performance parameters of application software - Google Patents

Abstract

The application discloses a method, a device and a storage medium for checking performance parameters of application software, relates to the field of performance parameter detection, and is used for solving the problem that in the prior art, all performance parameters of the application software cannot be checked in real time. According to the method, by integrating the SDK plug-in into the application software, when the application software is opened, the SDK plug-in detects the performance parameters of the application software in real time and displays the floating window assembly on an interface; and if the performance parameters of the current application software are required to be checked, checking the performance parameters of the application software by clicking the floating window component. Therefore, the SDK plug-in realizes real-time checking of the performance parameters of the application software, and the performance parameters of the application software are not required to be detected through a plurality of tools.

Description

A method, device and storage medium for viewing application software performance parameters

technical field

The present application relates to the field of performance parameter detection, in particular to a method, device and storage medium for checking performance parameters of application software.

Background technique

At present, application software monitors performance parameters through third-party application software, and different third-party application software needs to be used for different performance parameters.

Therefore, in the prior art, various performance parameters of the application software cannot be viewed in real time.

Contents of the invention

Embodiments of the present application provide a method, device, and storage medium for checking performance parameters of application software, so as to solve the problem in the prior art that various performance parameters of application software cannot be checked in real time.

In the first aspect, the embodiment of the present application provides a method for viewing application software performance parameters, which is applied to an Android system client, and the method includes:

After receiving the request to open the application software, the performance parameters of the application software are detected in real time, and the floating window component in the initial state is displayed on the interface;

After receiving a click request for clicking on the floating window component, controlling the floating window component to display an operation interface of the performance parameters of the application software;

If a display request for any of the performance parameters is received, the real-time detection results of the performance parameters are displayed.

In the second aspect, the embodiment of the present application provides a device for viewing application software performance parameters, the device includes:

The detection module is used to detect the performance parameters of the application software in real time after receiving the request to open the application software, and display the floating window component in the initial state on the interface;

The display module is configured to control the floating window component to display the operation interface of the performance parameters of the application software after receiving a click request for clicking on the floating window component;

The first display module is configured to display the real-time detection result of the performance parameter if a display request for any of the performance parameters is received.

In a third aspect, another embodiment of the present application further provides a computing device, including at least one processor; and;

A memory connected in communication with the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processing The device can execute a method for viewing application software performance parameters provided in the embodiment of the present application.

In a fourth aspect, another embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores computer-executable instructions, and the computer-executable instructions are used to cause a computer to execute the method described in the embodiment of the present application. A method of viewing application software performance parameters.

A method, device, and storage medium for viewing application software performance parameters provided in the embodiments of the present application, by integrating an SDK (Software Development Kit, Software Development Kit) plug-in to the application software, when the application software is opened, the SDK plug-in will The performance parameters of the application software are detected in real time, and the floating window components are displayed on the interface; if you want to view the various performance parameters of the current application software, you can check the various performance parameters of the application software by clicking the floating window components. In this way, through the SDK plug-in, real-time viewing of various performance parameters of the application software is realized.

Additional features and advantages of the application will be set forth in the description which follows, and, in part, will be obvious from the description, or may be learned by practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The schematic embodiments and descriptions of the application are used to explain the application and do not constitute an improper limitation to the application. In the attached picture:

FIG. 1 is a schematic flow diagram of viewing application software performance parameters in an embodiment of the present application;

Fig. 2 is a schematic diagram 1 of the floating window assembly in the initial state in the embodiment of the present application;

Fig. 3 is a schematic diagram after clicking on the floating window component in the embodiment of the present application;

Fig. 4 is a second schematic diagram of the floating window assembly in the initial state in the embodiment of the present application;

FIG. 5 is a schematic structural diagram of viewing application software performance parameters in an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a computing device according to an embodiment of the present application.

Detailed ways

In order to solve the problem in the prior art that various performance parameters of application software cannot be checked in real time, embodiments of the present application provide a method, device and storage medium for checking performance parameters of application software. In order to better understand the technical solution provided by the embodiment of the present application, the basic principle of the solution is briefly explained below:

The performance parameters of the application software include information such as network requests, traffic usage, memory usage, CPU (Central Processing Unit, central processing unit) usage, stuttering and frame loss, and application exceptions. In the prior art, the third-party packet capture tool is used to detect the network request, the setting of the developer tool is used to distinguish whether the frame is stuck, the third-party application software is used to obtain the specific information of the application software exception, and the first Three-party SDK plug-in to view information such as CPU usage and memory usage.

However, although the performance parameters of the application software can be detected in the prior art, it is difficult to check the performance parameters of the application software in real time due to the detection of the performance parameters of the application software by multiple tools.

In view of this, an embodiment of the present application provides a method, device, and storage medium for viewing application software performance parameters. By integrating SDK (Software Development Kit, Software Development Kit) plug-ins for application software that wants to view performance parameters, in When the application software is opened, the SDK plug-in will detect the various performance parameters of the application software in real time, and display the floating window component on the interface; if you want to view the various performance parameters of the current application software, click the floating window Check the performance parameters. In this way, through the SDK plug-in, real-time viewing of various performance parameters of the application software is realized, and there is no need to use multiple tools to detect various performance parameters of the application software.

For ease of understanding, the technical solutions provided by the present application will be further described below in conjunction with the accompanying drawings. Figure 1 is a schematic flow chart of viewing application software performance parameters, including the following steps:

Step 101: After receiving the request to open the application software, perform real-time detection of the performance parameters of the application software, and display the floating window component in the initial state on the interface.

In the embodiment of the present application, in order to realize the real-time detection of the performance parameters of the application software, it is necessary to integrate the SDK plug-in for real-time detection into the application software. In this way, after the application software is opened, the integrated The SDK plug-in detects each performance parameter of the application software, and the SDK plug-in only detects each performance parameter of the integrated application software, and does not detect other application software.

In one embodiment, SDK plug-ins can be integrated on multiple application software respectively. For example: both application software 1 and application software 2 are integrated with SDK plug-ins; when application software 1 is opened, the SDK plug-in integrated on application software 1 starts to detect the performance parameters of application software 1, and does not detect the performance parameters of application software 2. Various performance parameters; when the application software 2 is opened, the SDK plug-in integrated on the application software 2 starts to detect the various performance parameters of the application software 2, and does not detect the various performance parameters of the application software 1.

Step 102: After receiving a click request for clicking the floating window component, control the floating window component to display an operation interface of the performance parameters of the application software.

As shown in FIG. 2 , it is a schematic diagram of the floating window assembly in an initial state. Wherein, the floating window component in the initial state is above the current application software and displayed in a floating manner. And the transparency of the floating window component can be adjusted through settings. As shown in FIG. 3 , it is a schematic diagram after clicking the floating window component. Wherein, the expanded floating window component is still above the application software and displayed in a floating manner. The expanded floating window component will display viewable performance parameters; such as: network request, traffic usage, CPU usage, memory usage, frame loss and exception list, etc., click on the corresponding performance parameters to view.

Step 103: If a display request for any of the performance parameters is received, display the real-time detection results of the performance parameters.

In this way, through the SDK plug-in, real-time viewing of various performance parameters of the application software is realized, and there is no need to use multiple tools to detect various performance parameters of the application software.

In the embodiment of this application, in order to improve the user experience, some brief performance parameter information is added to the floating window component in the original state, which can be specifically implemented as steps A1-A2:

Step A1: Display brief information of the real-time detection results of the memory usage, the CPU usage, and the traffic usage on the floating window component in an initial state.

Step A2: Display the real-time detection result of the freezing frame loss through the background color of the floating window component in the initial state.

It should be noted that the execution sequence of Step A1-Step A2 is not limited.

As shown in FIG. 4 , it is a schematic diagram of the floating window assembly in an initial state. Among them, the brief information of the real-time detection result of the memory usage is the percentage of the used memory to the total memory, as shown in the figure: 57%; the brief information of the real-time detection result of the CPU usage is the percentage of the used CPU to the total CPU The percentage of CPU as shown in the figure: 29%; the brief information of the real-time detection result of traffic usage is download speed and upload speed, as shown in the figure, upload speed: 10k/s (kilobytes per second) and download speed: 200k/s. The percentage of the used memory to the total memory, the percentage of the used CPU to the total CPU, and the download speed and upload speed are displayed in the floating window component.

However, in the embodiment of the present application, the background color of the floating window component in the initial state reflects the current situation of freezing and dropping frames. For example: if the background color is green, it means no frames are dropped, and if the background color is red, it means frames are dropped. Of course, in order to further refine whether the frame is dropped or stuck, multiple background colors can be used to illustrate the frame dropped. For example: if the background color is green, the frame is not dropped, if the background color is yellow, it is close to the border of frame loss, and if the background color is red, it is frame loss. Of course, other background colors may also be used to explain the situation of frame loss due to freezing, which is not limited in this application.

In this way, when the user does not click on the floating window component, he can still view the performance parameters of the current application software, which improves the user experience.

In the embodiment of the present application, in order to display the floating window component on the smart terminal through the SDK plug-in, it can be realized through the add view (addView) method under the interface window manager (WindowMananger). Wherein, the interface window manager can be obtained by obtaining Android system service (Android WINDOW_SERVICE).

After introducing how to view the performance parameters of the application software, the following will further explain how to detect the performance parameters of the application software through the SDK plug-in.

Performance parameters include information such as network requests, traffic usage, memory usage, CPU usage, freeze frame loss, and application exceptions. The following describes how to detect each performance parameter.

1. Network request:

In the embodiment of the present application, in order to realize the real-time detection of the network request through the SDK plug-in, it can be determined through the aspect-oriented programming (AOP) mechanism; specifically, it can be implemented as step B1-step B3:

Step B1: Based on the aspect-oriented programming AOP mechanism, determine the two tangent points of the network request of the current interface before and after the call.

Step B2: Make an aspect of the two tangent points respectively to obtain the request parameters of the network request before invocation and the return parameters after invocation.

Step B3: taking the request parameter and the return parameter as the real-time detection result of the network request.

In this way, through the AOP mechanism, the real-time detection of the network request of the current application software is realized, and the real-time viewing of the network request is realized by clicking on the network request in the floating window component to view.

Furthermore, in order to allow developers to edit the network request, in the embodiment of this application, it is also possible to edit the network request by intercepting the request parameters at the cut point. The following takes the cut point before calling as an example , which can be specifically implemented as step C1-step C3:

Step C1: Intercept the request parameter at the cut point before calling.

Step C2: Setting the request parameter to an editable state.

In this embodiment of the application, when the request parameter is editable, the developer can modify and edit the request parameter.

Step C3: After receiving the editing completion request, respectively make a cut to the two cut points to obtain the edited request parameters of the network request before invocation and the edited request parameters after invocation corresponding to the edited request parameters. return parameters.

Similarly, the return parameter can be edited by intercepting the return parameter at the cut point after the call, and intercepting the return parameter at the cut point after the call; After the request is completed, the two tangent points are respectively cut to obtain the request parameters of the network request before invocation and the edited return parameters after invocation.

In this way, by intercepting the cut-out, the developer can edit the network request through the SDK plug-in, which simplifies the operation of the developer.

2. Flow usage:

In the embodiment of this application, in order to realize the real-time detection of traffic usage through the SDK plug-in, it can be determined through the Android TrafficStats class; specifically, it can be implemented as step D1-step D2:

Step D1: Use the Android TrafficStats class to locate the UID (user identity certificate) of the application software on the current interface.

Step D2: Acquire the located upload traffic and/or download traffic of the application software as a real-time detection result of the traffic usage.

In this way, through the Android TrafficStats class, the real-time detection of the traffic usage of the current application software is realized, and the real-time viewing of the traffic usage is realized by clicking the traffic usage in the floating window component to view.

3. Memory usage:

In this embodiment of the application, in order to realize the real-time detection of memory usage through the SDK plug-in, it can be determined through the method of obtaining memory structure information (ActivityManager.getMemoryInfo(ActivityManager.MemoryInfo)) under the activity manager; specifically, it can be implemented as steps E1- Step E3:

Step E1: Read the information in the system file for storing memory information, and obtain the total amount of memory of the client.

In one embodiment, system files can be read through the /proc/meminfo path.

Step E2: Obtain the current amount of available memory through the method of obtaining memory structure information under the activity manager.

Step E3: taking the total amount of memory and the amount of currently available memory as the real-time detection result of the memory usage.

In this way, through the method ActivityManager.getMemoryInfo(ActivityManager.MemoryInfo), the real-time detection of the memory usage of the current application software is realized, and the real-time viewing of the memory usage is realized by clicking the memory usage in the floating window component to view.

4. CPU usage:

In the embodiment of this application, in order to realize real-time detection of CPU usage through the SDK plug-in, it can be determined by reading the system file used to store CPU information; specifically, it can be implemented as step F1-step F2:

Step F1: Read the information in the system file for storing CPU information, and determine the current CPU usage.

Wherein, the CPU usage may include the currently used CPU resources and the total CPU resources.

In one embodiment, system files can be read through the proc/stat path.

Step F2: taking the current CPU usage as the real-time detection result of the CPU usage.

In this way, by reading the system file, the real-time detection of the CPU usage of the current application software is realized, and the real-time viewing of the CPU usage is realized by clicking on the CPU usage in the floating window component to check.

5. Caton frame loss:

In the embodiment of this application, in order to realize the real-time detection of frame loss through the SDK plug-in, it can be determined through the callback (Choreographer.FrameCallback) method of the interface frame refresh under the message processor; specifically, it can be implemented as steps G1-step G4 :

Step G1: Monitor the current screen through the callback method of interface frame refresh under the message processor.

Step G2: Call back when a screen refresh is detected, and record the refresh interval.

Step G3: Compare the refresh interval with the preset standard interval to determine whether there is a frame freeze or frame loss.

In one embodiment, the preset standard interval may be 16 milliseconds.

Step G4: Use the result of the refresh interval and whether the frame is stuck or lost as the real-time detection result of the frame freezing or not.

In this way, through the Choreographer.FrameCallback method, the real-time detection of the frame loss of the current application software is realized, and the real-time view of the frame loss is realized by clicking the frame loss in the floating window component to view.

6. Abnormal application:

In the embodiment of this application, in order to realize real-time detection of application exceptions through the SDK plug-in, it can be determined through the exception capture mechanism (UncaughtExceptionHandler); specifically, it can be implemented as step H1-step H3:

Step H1: After receiving the request to open the application software, initialize UncaughtExceptionHandler.

Step H2: If it is detected that the application software is abnormal, obtain the log file of the application software through the abnormality capture mechanism.

Wherein, the abnormality of the application software is the crash of the application process.

Step H3: Store the log file into an exception list.

In the embodiment of the present application, when the application software is abnormal, the log file is stored in the exception list before the application software is closed.

In this embodiment of the application, after obtaining the log file of the application software, the log file can be saved locally, or uploaded to the server after saving, and the server can analyze the application anomaly.

In this way, through the exception capture mechanism, real-time detection of application exceptions is realized, and the saved log files can be viewed by clicking the exception list in the floating window component, and real-time viewing of application exception log files is realized.

Based on the same inventive concept, the embodiment of the present application also provides a device for checking performance parameters of application software. As shown in Figure 5, the device includes:

The detection module 501 is configured to detect the performance parameters of the application software in real time after receiving the request to open the application software, and display the floating window component in the initial state on the interface;

The display module 502 is configured to control the floating window component to display the operation interface of the performance parameters of the application software after receiving a click request for clicking on the floating window component;

The first display module 503 is configured to display the real-time detection result of the performance parameter if a display request for any of the performance parameters is received.

Further, if the performance parameter is a network request, the real-time detection result of the network request is obtained by the following means:

Determine the point-cutting module, which is used to determine the two point-cutting points of the network request of the current interface before and after calling based on the aspect-oriented programming AOP mechanism;

An aspect module, configured to perform an aspect on the two cut points respectively, to obtain the request parameters of the network request before invocation and the return parameters after invocation;

The first result module is configured to use the request parameter and the return parameter as the real-time detection result of the network request.

Further, the device also includes:

The first interception module is used for the sectioning module to perform sectioning on the two cut points respectively, obtain the request parameter of the network request before the call and the return parameter after the call, and intercept at the cut point before the call said request parameters;

A first setting module, configured to set the request parameter to an editable state;

The face-cutting module is configured to perform face-cutting on the two cut points respectively after receiving the editing completion request, and obtain the edited request parameters of the network request before invocation and the corresponding edited request parameters after invocation The return parameter.

Further, the device also includes:

The second interception module is used for the sectioning module to perform sectioning on the two cut points respectively, to obtain the request parameter of the network request before the call and the return parameter after the call, and to intercept at the cut point after the call said return parameter;

The second setting module is used to set the return parameter to an editable state;

The face-cutting module is configured to perform face-cutting on the two cut points respectively after receiving the completion request of editing, and obtain the request parameters of the network request before calling and the edited return parameters after calling.

Further, if the performance parameter is traffic usage, the real-time detection result of traffic usage is obtained through the following means:

The positioning module is used to perform user identification UID positioning on the application software of the current interface through the Android TrafficStats class of Android traffic statistics;

The second result module is configured to obtain the located upload traffic and/or download traffic of the application software as the real-time detection result of the traffic usage.

Further, if the performance parameter is memory usage, the real-time detection result of memory usage is obtained through the following means:

The first reading module is used to read the information in the system file for storing memory information, and obtain the total amount of memory of the client;

The obtaining module is used to obtain the current amount of available memory through the method of obtaining memory structure information under the activity manager;

The third result module is configured to use the total amount of memory and the amount of currently available memory as the real-time detection result of the memory usage.

Further, if the performance parameter is CPU usage, the real-time detection result of CPU usage is obtained by the following means:

The second reading module is used to read the information in the system file for storing the CPU information, and determine the usage of the current CPU;

The fourth result module is configured to use the current CPU usage as the real-time detection result of the CPU usage.

Further, if the performance parameter is stuck frame loss, the real-time detection result of stuck frame loss is obtained by the following means:

The monitoring module is used to monitor the current picture through the callback method of interface frame refresh under the message processor;

The callback module is used to call back when the screen refresh is detected, and record the refresh interval;

A comparison module, configured to compare the refresh interval duration with a preset standard interval duration, to determine whether a frame is stuck or not;

The fifth result module is configured to use the result of the refresh interval duration and whether the freeze frame is lost or not as the real-time detection result of the freeze frame loss.

Further, the device also includes:

The initialization module is used to initialize the exception catching mechanism UncaughtExceptionHandler after receiving the request to open the application software;

An exception module, configured to obtain a log file of the application software through the exception capture mechanism if an exception is detected in the application software;

The storage module is configured to store the log file into an exception list.

Further, the device also includes:

The second display module is used to display the memory usage, the CPU usage and The brief information of the real-time detection result of the traffic usage is displayed on the floating window assembly in the initial state;

The third display module is configured to display the real-time detection result of frame freezing and frame loss through the background color of the floating window component in an initial state.

After introducing the method and device for viewing application software performance parameters according to the exemplary embodiment of the present application, next, a computing device according to another exemplary embodiment of the present application is introduced.

Those skilled in the art can understand that various aspects of the present application can be implemented as a system, method or program product. Therefore, various aspects of the present application can be specifically implemented in the following forms, that is: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, which can be collectively referred to herein as "circuit", "module" or "system".

In some possible implementation manners, according to the embodiment of the present application, a computing device may at least include at least one processor and at least one memory. Wherein, the memory stores program codes, and when the program codes are executed by the processor, the processor is made to execute steps 101-103 in the method for viewing application software performance parameters according to various exemplary embodiments of the present application described above in this specification .

A computing device 60 according to this embodiment of the present application is described below with reference to FIG. 6 . The computing device 60 shown in FIG. 6 is only an example, and should not limit the functions and scope of use of this embodiment of the present application. The computing device may be, for example, a mobile phone, a tablet computer, or the like.

As shown in FIG. 6, computing device 60 takes the form of a general-purpose computing device. Components of the computing device 60 may include, but are not limited to: at least one processor 61 , at least one memory 62 , and a bus 63 connecting different system components (including the memory 62 and the processor 61 ).

Bus 63 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, or a local bus using any of a variety of bus structures.

Memory 62 may include readable media in the form of volatile memory, such as random access memory (RAM) 621 and/or cache memory 622 , and may further include read only memory (ROM) 623 .

Memory 62 may also include programs/utilities 625 having a set (at least one) of program modules 624 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, which Each or some combination of the examples may include the implementation of a network environment.

Computing device 60 may also communicate with one or more external devices 64 (such as pointing devices, etc.), and may also communicate with one or more devices that enable a user to interact with computing device 60, and/or communicate with computing device 60 to enable Any device (eg, router, modem, etc.) that communicates with one or more other computing devices communicates. Such communication may occur through input/output (I/O) interface 65 . Also, computing device 60 may communicate with one or more networks (eg, local area network (LAN), wide area network (WAN), and/or public networks, such as the Internet) via network adapter 66 . As shown, network adapter 66 communicates with other modules for computing device 60 over bus 63 . It should be understood that although not shown, other hardware and/or software modules may be used in conjunction with computing device 60, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives And data backup storage system, etc.

In some possible implementations, various aspects of the method for viewing application software performance parameters provided in this application can also be implemented in the form of a program product, which includes program code. When the program product runs on a computer device, the program code To make the computer device execute the steps in the method for viewing application software performance parameters according to various exemplary embodiments of the present application described above in this specification, execute steps 101 to 103 as shown in FIG. 1 .

A program product may take the form of any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: electrical connection with one or more conductors, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

The method for viewing the performance parameters of application software in the embodiment of the present application may adopt a portable compact disc read-only memory (CD-ROM) and include program codes, and may run on a computing device. However, the program product of the present application is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program, and the program may be used by or in combination with an instruction execution system, device, or device.

A readable signal medium may include a data signal carrying readable program code in baseband or as part of a carrier wave. Such propagated data signals may take many forms, including - but not limited to - electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including - but not limited to - wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program codes for performing the operations of the present application can be written in any combination of one or more programming languages, including object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural programming Language - such as "C" or similar programming language. The program code may execute entirely on the user computing device, partly on the user device, as a stand-alone software package, partly on the user computing device and partly on a remote computing device, or entirely on the remote computing device or server to execute. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or alternatively, may be connected to an external computing device (e.g., using an Internet service Provider via Internet connection).

It should be noted that although several units or subunits of the apparatus are mentioned in the above detailed description, this division is only exemplary and not mandatory. Actually, according to the embodiment of the present application, the features and functions of two or more units described above may be embodied in one unit. Conversely, the features and functions of one unit described above may be further divided to be embodied by a plurality of units.

Additionally, while operations of the methods of the present application are described in order in the figures, there is no requirement or implication that these operations must be performed in that order, or that all illustrated operations must be performed to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowcharts and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing apparatus to operate in a manner such that the instructions stored in the computer readable memory produce an article of manufacture comprising instruction means, the instruction means Realize the function specified in one or more procedures of the flowchart and/or one or more boxes of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

While preferred embodiments of the present application have been described, additional changes and modifications to these embodiments can be made by those skilled in the art once the basic inventive concept is appreciated. Therefore, the appended claims are intended to be construed to cover the preferred embodiment and all changes and modifications which fall within the scope of the application.

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims (10)

1. A method for viewing application software performance parameters is characterized in that, being applied to an Android system client, the application software to which the client belongs is integrated with an SDK plug-in, and the method includes: After the SDK plug-in receives the request to open the application software, it detects the performance parameters of the application software in real time, and displays the floating window component in the initial state on the interface. The performance parameters include network requests, traffic usage, memory Usage, CPU usage, freeze frame loss and application exception; After receiving a click request for clicking on the floating window component, controlling the floating window component to display an operation interface of the performance parameters of the application software; If a display request for any of the performance parameters is received, display the real-time detection results of the performance parameters; If the performance parameter is a network request, the real-time detection result of the network request is obtained by the following method: Based on the aspect-oriented programming AOP mechanism, determine the two tangent points of the network request of the current interface before and after the call; Intercept the request parameter at the cut point before invoking, set the request parameter to an editable state, and after receiving the completion request of editing, make cuts to the two cut points respectively, and obtain the network request in The edited request parameter before the call and the return parameter corresponding to the edited request parameter after the call; or; intercept the return parameter at the cut point after the call, and set the return parameter to be editable state, after receiving the completion request of editing, respectively make an aspect to the two cut points, and obtain the request parameters of the network request before calling and the edited return parameters after calling; The request parameter and the return parameter are used as the real-time detection result of the network request. 2. The method according to claim 1, wherein if the performance parameter is traffic usage, the real-time detection result of traffic usage is obtained by the following method: Through the Android TrafficStats class of Android traffic statistics, the user identity certification UID location is performed on the application software of the current interface; Acquiring the located upload traffic and/or download traffic of the application software as the real-time detection result of the traffic usage. 3. The method according to claim 1, wherein if the performance parameter is memory usage, the real-time detection result of memory usage is obtained by the following method: Read the information in the system file used to store memory information to obtain the total memory of the client; Obtain the current amount of available memory through the method of obtaining memory structure information under the activity manager; The total amount of memory and the amount of currently available memory are used as real-time detection results of memory usage. 4. The method according to claim 1, wherein, if the performance parameter is used by the CPU, the real-time detection result obtained by the CPU is obtained by the following method: Read the information in the system file used to store CPU information to determine the current CPU usage; Using the current CPU usage as the real-time detection result of the CPU usage. 5. The method according to claim 1, wherein, if the performance parameter is stuck and lost frames, the real-time detection result of stuck and lost frames is obtained by the following method: Monitor the current screen through the callback method of interface frame refresh under the message processor; Callback when the screen refresh is detected, and record the refresh interval; Comparing the refresh interval duration with the preset standard interval duration to determine whether the frame is stuck or lost; The result of the refresh interval length and frame loss is taken as the real-time detection result of frame loss. 6. The method according to claim 1, further comprising: After receiving the request to open the application software, initialize the exception catching mechanism UncaughtExceptionHandler; If it is detected that the application software is abnormal, the log file of the application software is obtained through the abnormal capture mechanism; Store said log file into an exception list. 7. The method according to claim 1, wherein after receiving the click request for clicking on the floating window component, before controlling the floating window component to display an operation interface of network information, the method further comprises: displaying brief information on real-time detection results of the memory usage, the CPU usage, and the traffic usage on the floating window component in an initial state; and, The real-time detection result of frame freezing and frame loss is displayed through the background color of the floating window component in an initial state. 8. A device for viewing application software performance parameters, characterized in that it is applied to an Android system client, the application software to which the client belongs is integrated with an SDK plug-in, and the device is applied to the SDK plug-in, and includes: The detection module is used to detect the performance parameters of the application software in real time after receiving the request to open the application software, and display the floating window component in the initial state on the interface. The performance parameters include network requests, traffic usage, Any combination of memory usage, CPU usage, stuttering and frame loss, and application exceptions; The display module is configured to control the floating window component to display the operation interface of the performance parameters of the application software after receiving a click request for clicking on the floating window component; The first display module is configured to display the real-time detection results of the performance parameters if a display request for any of the performance parameters is received; If the performance parameter is a network request, the real-time detection result of the network request is obtained through the following modules: Determine the point-cutting module, which is used to determine the two point-cutting points of the network request of the current interface before and after calling based on the aspect-oriented programming AOP mechanism; The aspect module is used to intercept the request parameter at the point of cut before invoking, set the request parameter to an editable state, and after receiving the completion request of editing, perform the cut of the two points of cut respectively to obtain The edited request parameter of the network request before the call and the return parameter corresponding to the edited request parameter after the call; or; intercept the return parameter at the cut point after the call, and return the return The parameter is set to an editable state, and after receiving the editing completion request, the two cut points are respectively cut to obtain the request parameter of the network request before invocation and the edited return parameter after invocation; The first result module is configured to use the request parameter and the return parameter as the real-time detection result of the network request. 9. A medium readable by a smart terminal, storing executable instructions of the smart terminal, wherein the executable instructions of the smart terminal are used to execute the method according to any one of claims 1-7. 10. A computing device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to The at least one processor is enabled to perform the method of any one of claims 1-7.

Images