Mobile terminal performance early warning system

Abstract

The invention discloses a mobile terminal performance early warning system. The system comprises a system scheduling module, a data acquisition module, a data analysis module and an application layer performance management module. According to the method, performance gliding is recognized and blocked in advance, performance optimization work is preposed to a development stage, the performance landslide phenomenon is prevented as soon as possible, early warning is completed through CI automatic performance testing, performance monitoring, automatic lading and enterprise micro-alarm notification processes, adaptability testing and data acquisition are automatically triggered through intelligent code monitoring, and the system performance is improved. And deeply analyzing and automatically responding to an exception generation report. The core of the method is that an integrated test management tool is provided in the development stage, efficient performance optimization and team cooperation are promoted, a full-chain performance management system from monitoring, intelligent analysis to optimization execution is formed, developers can be helped to effectively recognize and block performance glide in the development stage, the probability of online performance problems is reduced, and the development efficiency is improved. App stability is facilitated, and the overall working efficiency is improved.

Description

Technical Field

[0001] The present application relates to an early warning system, specifically a mobile terminal performance early warning system. Background Art

[0002] Mobile performance warning is an important part of mobile application development and maintenance. It aims to timely discover and warn of problems that may affect application performance through real-time monitoring and data analysis, thereby ensuring user experience and application stability. Performance problems such as crashes, freezes, slow loading, etc. directly affect the user experience. The warning system can promptly discover and fix these problems to avoid user loss. Through the warning system, developers can promptly discover and deal with potential performance problems, reduce the occurrence of application crashes and failures, and improve application stability and reliability. The warning system can provide real-time data on application performance bottlenecks to help developers optimize resource allocation and improve application operation efficiency. Through real-time monitoring, data analysis, warning triggering and other means, it can effectively improve user experience, ensure application stability and optimize resource allocation. With the continuous advancement of technology and the continuous expansion of application scenarios, mobile performance warning systems will play a more important role in the field of mobile application development.

[0003] Mobile terminal performance warning is an indispensable part of mobile application development and maintenance. The existing mobile terminal performance warning has the following defects:

[0004] (1) Limitations of offline performance testing: There is a lack of automated performance testing processes offline. Even if the test supports automation, it does not cover the performance testing module and relies on manual intervention, resulting in low efficiency and high costs. It may also leave performance risks and damage the user experience.

[0005] (2) Limitations of online APM monitoring: Although online application performance management (APM) can dynamically monitor performance, it cannot generate detailed performance reports before the application is released. The lack of an automatic feedback mechanism makes it difficult to completely eliminate performance problems before the application goes online.

[0006] (3) Insufficient granularity of performance reports: The current performance data analysis reports are not detailed enough and fail to cover every commit of the main branch of each version. This results in missing key data when tracing problems, which affects the rapid location and resolution of problems. Summary of the invention

[0007] A mobile terminal performance early warning system, the early warning system includes a system scheduling module, a data collection module, a data analysis module and an application layer performance management module;

[0008] The system scheduling module includes a task adding unit and a task matching and dispatching unit; the data acquisition module includes a performance acquisition unit, a file analysis unit and a data processing and reporting unit; the data analysis module includes a data processing unit, a data comparison unit and an automatic bill of lading unit; the application layer performance management module includes a template testing unit, a performance reporting unit, an alarm unit, a test case management unit and a performance approval unit.

[0009] In this technical solution, the system scheduling module is connected to the data acquisition module, the data acquisition module is connected to the data analysis module, and the data analysis module is bidirectionally connected to the application layer performance management module.

[0010] In this technical solution, the task adding unit includes a Git time monitoring component and a custom task component.

[0011] In this technical solution, the task matching and dispatching unit includes a device and task matching component and a configuration file generation component.

[0012] In this technical solution, the data processing unit includes basic data processing principles, scene processing elements and key data processing elements.

[0013] In this technical solution, the data comparison unit includes a comparison relationship processing component, a value acquisition component and a performance report generation component.

[0014] In the technical solution, the automatic bill of lading unit includes a basic information acquisition component, a question screening component and a query component.

[0015] In this technical solution, the task adding unit is connected to the task matching and dispatching unit, and the data processing and reporting unit is connected to the performance collection unit and the file analysis unit respectively.

[0016] In this technical solution, the data processing unit is connected to the data comparison unit and the automatic bill of lading unit respectively.

[0017] In this technical solution, the template test unit is connected to the performance reporting unit, the alarm unit, the test case management unit and the performance approval unit respectively.

[0018] The beneficial effect of the present application is that the present application provides a mobile terminal performance early warning system that can identify and block performance degradation in advance, advance performance optimization work to the development stage, and prevent performance degradation as early as possible. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0020] Figure 1 This is a schematic diagram of the overall three-dimensional structure of an embodiment of the present application;

[0021] In the figure: 10, system scheduling module; 11, task adding unit; 111, Git time monitoring component; 112, custom task component; 12, task matching and dispatching unit; 121, device and task matching component; 122, configuration file generation component;

[0022] 20. Data collection module; 21. Performance collection unit; 22. File analysis unit; 23. Data processing and reporting unit;

[0023] 30. Data analysis module; 31. Data processing unit; 311. Basic data processing element; 312. Scene processing element; 313. Key data processing element; 32. Data comparison unit; 321. Comparison relationship processing element; 322. Value acquisition element; 323. Performance report generation element; 33. Automatic bill of lading unit; 331. Basic information acquisition element; 332. Problem screening element; 333. Query element;

[0024] 40. Application layer performance management module; 41. Template testing unit; 42. Performance reporting unit; 43. Alarm unit; 44. Test case management unit; 45. Performance approval unit. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] In the present application, the terms "upper", "lower", "left", "right", "front", "back", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the drawings. These terms are mainly used to better describe the present application and its embodiments, and are not used to limit the indicated devices, elements or components to have a specific orientation, or to be constructed and operated in a specific orientation.

[0028] In addition, some of the above terms may be used to express other meanings in addition to indicating orientation or positional relationship. For example, the term "on" may also be used to express a certain dependency or connection relationship in some cases. For those of ordinary skill in the art, the specific meanings of these terms in this application can be understood according to specific circumstances.

[0029] In addition, the terms "installed", "set", "provided with", "connected", "connected", and "socketed" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral structure; it can be a mechanical connection, or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate medium, or it can be an internal connection between two devices, elements, or components. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0030] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0031] See also Figure 1 As shown, a mobile terminal performance warning system includes a system scheduling module 10, a data collection module 20, a data analysis module 30 and an application layer performance management module 40;

[0032] The system scheduling module 10 includes a task adding unit 11 and a task matching and dispatching unit 12; the data acquisition module 20 includes a performance acquisition unit 21, a file analysis unit 22 and a data processing and reporting unit 23; the data analysis module 30 includes a data processing unit 31, a data comparison unit 32 and an automatic bill of lading unit 33; the application layer performance management module 40 includes a template testing unit 41, a performance reporting unit 42, an alarm unit 43, a test case management unit 44 and a performance approval unit 45.

[0033] The system scheduling module 10 is connected to the data collection module 20, the data collection module 20 is connected to the data analysis module 30, and the data analysis module 30 is bidirectionally connected to the application layer performance management module 40; the task adding unit 11 includes a Git time monitoring element 111 and a custom task element 112; the task matching dispatching unit 12 includes a device and task matching element 121 and a configuration file generation element 122; the data processing unit 31 includes a basic data processing principle 311, a scene processing element 312 and a key data processing element 313; the data comparison unit 32 includes a comparison relationship processing element The automatic billing unit 33 includes a basic information acquisition component 331, a problem screening component 332 and a query component 333; the task adding unit 11 is connected to the task matching and dispatching unit 12, and the data processing and reporting unit 23 is respectively connected to the performance collection unit 21 and the file analysis unit 22; the data processing unit 31 is respectively connected to the data comparison unit 32 and the automatic billing unit 33; the template testing unit 41 is respectively connected to the performance reporting unit 42, the alarm unit 43, the test case management unit 44 and the performance approval unit 45.

[0034] In this technical solution, the Git time monitoring component 111 in the system scheduling module 10 monitors the code base changes (Git MR events) in real time, and intelligently selects automated performance tests according to the code type, branch weight and author authority. The task adding unit 11 flexibly arranges test tasks and optimizes resource usage according to the system resource status, especially the CPU load. The self-defined task component 112 dynamically adjusts the test intensity and frequency according to the code change frequency and historical test results. The device and task matching component 121 automatically selects the most suitable test environment and equipment to ensure the accuracy and reliability of the test results. The configuration file generation component 122 automatically generates test configurations and scripts to maintain the consistency of the test environment and the repeatability of the test.

[0035] In this technical solution, the data collection module 20 integrates the performance module, such as deep integration between the iOS side and Xcode's XCTest / XCTrace, to achieve accurate matching with the Instruments tool data, comprehensively capture App performance data, respond to Git code changes in real time, automatically trigger the performance data collection process, record the user information of each change in detail, ensure transparency and traceability, format the collected data into a unified standard, facilitate subsequent analysis and sharing, and produce a standardized performance analysis report based on performance data and Git change information.

[0036] In this technical solution, the data analysis module 30 ensures the quality of analysis by integrating and purifying data, compares performance data from multiple angles according to gitcommit, compares performance from multiple angles such as time series, version, and environment, identifies problems, and uses statistics and machine learning to predict performance trends. It automatically monitors and immediately notifies performance anomalies, generates comparison reports, and automatically creates tracking tickets when problems are found, thereby accelerating the problem-solving process.

[0037] In this technical solution, the application layer performance management module 40 quickly starts the test through a preset template, supports customization to adapt to different scenarios, generates detailed reports, assists in quickly locating performance problems, monitors in real time and automatically alarms performance degradation, and notifies specific persons in charge in the form of WeChat, CQA bug tickets, emails, etc., integrates use case design, execution and version control, promotes team collaboration and use case reuse, configures approval processes, and improves work efficiency and management standardization.

[0038] The benefits of this application are: this kind of mobile terminal performance warning system can prevent performance landslides early by identifying and blocking performance degradation in advance, putting performance optimization work in the development stage, and completing warnings through CI automated performance testing, performance monitoring, automatic billing and enterprise micro-alarm notification processes. Through intelligent code monitoring, adaptive testing and data collection are automatically triggered, and in-depth analysis and automatic response to abnormality generation reports are performed. Its core is to provide a set of integrated test management tools in the development stage, promote efficient performance optimization and team collaboration, and form a full-chain performance management system from monitoring, intelligent analysis to execution optimization, which can help developers effectively identify and block performance degradation in the development stage, reduce the probability of performance problems online, help app stability, and improve overall work efficiency.

[0039] The circuits, electronic components and modules involved are all prior art and can be fully implemented by those skilled in the art, and needless to say, the content protected by this application does not involve improvements to software and methods.

[0040] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. Mobile terminal performance early warning system, characterized by: The early warning system comprises a system scheduling module (10), a data collection module (20), a data analysis module (30) and an application layer performance management module (40); The system scheduling module (10) comprises a task adding unit (11) and a task matching dispatching unit (12); the data acquisition module (20) comprises a performance acquisition unit (21), a file analysis unit (22) and a data processing reporting unit (23); the data analysis module (30) comprises a data processing unit (31), a data comparison unit (32) and an automatic bill of lading unit (33); the application layer performance management module (40) comprises a template testing unit (41), a performance reporting unit (42), an alarm unit (43), a test case management unit (44) and a performance approval unit (45).

2. The mobile terminal performance early warning system according to claim 1, characterized in that: The system scheduling module (10) is connected to the data collection module (20), the data collection module (20) is connected to the data analysis module (30), and the data analysis module (30) is bidirectionally connected to the application layer performance management module (40).

3. The mobile terminal performance early warning system according to claim 1, characterized in that: The task adding unit (11) includes a Git time monitoring component (111) and a self-defined task component (112).

4. The mobile terminal performance early warning system according to claim 1, characterized in that: The task matching and dispatching unit (12) comprises a device and task matching component (121) and a configuration file generating component (122).

5. The mobile terminal performance early warning system according to claim 1, characterized in that: The data processing unit (31) includes a basic data processing principle (311), a scene processing element (312) and a key data processing element (313).

6. The mobile terminal performance early warning system according to claim 1, characterized in that: The data comparison unit (32) comprises a comparison relationship processing component (321), a value acquisition component (322) and a performance report generation component (323).

7. The mobile terminal performance early warning system according to claim 1, characterized in that: The automatic bill of lading unit (33) includes a basic information acquisition component (331), a question screening component (332) and a query component (333).

8. The mobile terminal performance early warning system according to claim 1, characterized in that: The task adding unit (11) is connected to the task matching dispatching unit (12), and the data processing reporting unit (23) is connected to the performance collecting unit (21) and the file analyzing unit (22) respectively.

9. The mobile terminal performance early warning system according to claim 1, characterized in that: The data processing unit (31) is connected to the data comparison unit (32) and the automatic bill of lading unit (33) respectively.

10. The mobile terminal performance early warning system according to claim 1, characterized in that: The template testing unit (41) is respectively connected to a performance reporting unit (42), an alarm unit (43), a test case management unit (44) and a performance approval unit (45).

Images