Core page performance determination method, electronic device, medium and product

Abstract

The present application discloses a core page performance determination method, electronic device, medium and product, which relates to the field of data analysis technology and is applied to a business integration management system, which is used to manage a customer system, including: for any sub-application system under the customer system, identifying each core page in the sub-application system and determining each key user using the sub-application system; based on the user behavior data of the sub-application system, each key user and each core page, determining whether the core page performance index of the sub-application system meets the standard. The present application solves the technical problem of how to determine whether the performance of the core scene used by the core user is affected.

Description

Technical Field

[0001] The present application relates to the field of data analysis technology, and in particular to a core page performance determination method, device, electronic device, storage medium and computer program product. Background Art

[0002] With the development of the Internet, the requirements for informatization within each enterprise are getting higher and higher, and higher requirements are put forward for the normal operation of enterprise systems. For real estate customers, due to the particularity of real estate systems, each customer usually has multiple systems and multiple functional points, and because each customer's own basic configuration facilities are different, the performance of each page is different, and the page opening time will be affected by the performance. If core users such as senior executives of the enterprise or high-frequency users of the system open the system page, the poor page performance may affect the use of core users, reduce the image of the system services provided by the software supplier among core users, and may even affect the core users' judgment on whether to continue to use the system services in the future. Therefore, for software suppliers, how to determine whether the performance of core scenarios used by core users is affected is a problem that needs to be solved. Summary of the invention

[0003] The main purpose of this application is to provide a core page performance determination method, device, electronic device, storage medium and computer program product, aiming to solve the technical problem of how to determine whether the core scene performance used by core users is affected.

[0004] To achieve the above purpose, the present application proposes a core page performance determination method, which is applied to a business integration management system, wherein the business integration management system is used to manage customer systems. The core page performance determination method includes:

[0005] For any sub-application system under the client system, identify each core page in the sub-application system and determine each key user using the sub-application system;

[0006] Based on the user behavior data of the sub-application system, the key users and the core pages, it is determined whether the core page performance index of the sub-application system meets the standard.

[0007] In one embodiment, the step of identifying each core page in the sub-application system includes:

[0008] In the case where the sub-application system is a personalized system, collecting attribute tags of each page, the number of user visits to each page within a first preset period, and the number of page visits;

[0009] The page whose user access quantity reaches a preset user quantity threshold and whose page access times reaches a preset page access times threshold, or whose attribute tag is a preset attribute, is determined as a core page.

[0010] In one embodiment, the step of determining each key user using the sub-application system includes:

[0011] Collect the number of system accesses and the number of access functions of each user to the sub-application system within the second preset period;

[0012] A user whose system access times reaches a preset system access threshold and whose access function number reaches a preset function number threshold is determined as a key user.

[0013] In one embodiment, the step of determining whether the core page performance index of the sub-application system meets the standard based on the user behavior data of the sub-application system, the key users and the core pages includes:

[0014] For any one of the key users, judging whether the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system through the user behavior data of the sub-application system;

[0015] For any one of the core pages, judging whether the core page meets the page dimension evaluation requirements when accessed by each user through the user behavior data of the sub-application system;

[0016] When the individual dimension evaluation requirements are met when each key user accesses each page in the sub-application system, and when each core page meets the page dimension evaluation requirements when accessed by each user, it is determined that the core page performance index of the sub-application system meets the standard.

[0017] In one embodiment, the step of determining whether the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system includes:

[0018] For any one of the pages of the sub-application system, collecting the number of timeouts during which the response time of the key user accessing the page exceeds a standard threshold within a third preset period, and the first total number of times the key user accesses the page within the third preset period;

[0019] When the ratio of the number of timeouts to the first total number of times reaches a first timeout ratio threshold, and the first total number of times reaches a first preset access threshold, it is determined that the key user meets the first sub-requirement of the personal dimension evaluation requirement when accessing each page in the sub-application system;

[0020] Determine a first number of times the first sub-demand is satisfied within a fourth preset period, and when the first number of times reaches a first preset satisfaction threshold, determine that the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system.

[0021] In one embodiment, the step of determining whether the core page meets the page dimension evaluation requirement when accessed by each user includes:

[0022] Collecting the number of requests for which the response time exceeds the standard threshold when the core page is accessed within the fifth preset period, and the second total number of times the core page is accessed within the fifth preset period;

[0023] When the ratio of the number of requests to the second total number of times reaches a second timeout ratio threshold, and the second total number of times reaches a second preset access threshold, it is determined that the core page meets the second sub-requirement of the page dimension evaluation requirement when accessed by each user;

[0024] Determine a second number of times the second sub-demand is satisfied within a sixth preset period, and when the second number of times reaches a second preset satisfaction threshold, determine that the core page meets the page dimension evaluation requirement when accessed by each user.

[0025] In one embodiment, after the step of determining whether the core page performance index of the sub-application system meets the standard, the step further includes:

[0026] When the core page performance index does not meet the standard, determine the key users that do not meet the personal dimension evaluation requirements, the core pages that do not meet the page dimension evaluation requirements, and the corresponding sub-application systems, and output the sub-application systems, the key users, and the core pages;

[0027] When the core page performance index reaches the standard, a standard-reaching notification of each sub-application system is output.

[0028] In addition, to achieve the above purpose, the present application also proposes a core page performance determination device, which is applied to a business integration management system, wherein the business integration management system is used to manage a customer system, wherein the customer system includes various sub-application systems, and the core page performance determination device includes:

[0029] An identification module, for identifying each core page in any sub-application system managed by the client system, and determining each key user using the sub-application system;

[0030] The judgment module is used to determine whether the core page performance index of the sub-application system meets the standard based on the user behavior data of the sub-application system, the key users and the core pages.

[0031] In addition, to achieve the above-mentioned purpose, the present application also proposes an electronic device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the core page performance determination method as described above.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the core page performance determination method described above are implemented.

[0033] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the core page performance determination method described above are implemented.

[0034] The present application provides a core page performance determination method, which is applied to a business integration management system, which is used to manage a customer system. The core page performance determination method includes: for any sub-application system under the customer system, identifying each core page in the sub-application system, and determining each key user who uses the sub-application system; based on the user behavior data of the sub-application system, each key user and each core page, determining whether the core page performance index of the sub-application system meets the standard.

[0035] This application ensures the accuracy and pertinence of subsequent performance evaluation by accurately locating the core pages that are most critical to business operations, and ensures that performance evaluation can truly reflect the needs and experience of core users by identifying key users with the highest system performance requirements and the most influential system evaluation. Based on user behavior data, key users and core pages, the performance indicators of each core page are tested to determine whether they meet the preset threshold or standard, so that performance bottlenecks or potential problems can be discovered in a timely manner. Compared with related solutions that ignore user differences and conduct indiscriminate evaluations of all pages and users, making it impossible to determine whether there are problems with the use of core users, this application identifies core pages, determines key users, and evaluates performance indicators based on user behavior data, outputs detailed compliance status, and realizes accurate evaluation of the performance of core pages in the business integration management system, improves the accuracy and efficiency of the evaluation, and can promptly discover whether the use experience of core users is affected, which helps to improve the image among core users and enhance the trust and satisfaction of core users in subsequent system services. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0037] 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, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0038] Figure 1 A flowchart of the first embodiment of the method for determining the performance of a core page of the present application is provided;

[0039] Figure 2 A flowchart diagram of the second embodiment of the method for determining the performance of a core page of the present application;

[0040] Figure 3 A schematic diagram of the compliance details page provided for the performance determination method of the core page of this application;

[0041] Figure 4 A schematic diagram of a core performance problem details page provided for the core page performance determination method of this application;

[0042] Figure 5 This is a schematic diagram of the module structure of the core page performance determination device of an embodiment of the present application;

[0043] Figure 6 Schematic diagram of the device structure of the hardware operating environment involved in the core page performance determination method in the embodiment of the present application.

[0044] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0045] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0046] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0047] The embodiment of the present application is applied to a business integration management system, which is used to manage customer systems. The main solution is: for any sub-application system under the customer system, identify the core pages in the sub-application system and determine the key users who use the sub-application system; based on the user behavior data of the sub-application system, the key users and the core pages, determine whether the core page performance indicators of the sub-application system meet the standards.

[0048] In this embodiment, for the convenience of description, the following description is made with the business integration management system as the execution entity.

[0049] With the development of the Internet, the demand for internal informatization of enterprises has increased dramatically, and the requirements for system stability and operating efficiency have become increasingly stringent. For real estate industry customers, the complexity of their business systems is particularly prominent. Each customer often has multiple systems covering multiple functional points, and due to the differences in their respective infrastructures, there are significant differences in page loading speed and response time. The quality of system performance, especially for senior executives and high-frequency users of the company, is directly related to their intuitive feeling of the value of the software, which in turn affects the long-term use and renewal decisions of the software. However, with the increase in the application of customer information systems and the fluctuation of network traffic, software performance will inevitably be affected. For software suppliers, the challenge is how to accurately identify whether the core users that are critical to the enterprise and the core scenarios they rely on are affected by performance degradation, and to promptly discover and solve performance bottlenecks.

[0050] The present application provides a solution, which not only realizes the in-depth and accurate measurement of the core page performance, but also significantly improves the accuracy and efficiency of the evaluation work by accurately identifying the core pages in the business integration management system, clearly defining the key user groups, and using the user behavior data to comprehensively evaluate the performance indicators. It can quickly capture any subtle changes in the core users' usage experience, ensure that their needs and expectations are responded to in a timely manner, help to establish a more positive image among the core user groups, greatly enhance their trust and satisfaction with the subsequent system services, and lay a solid foundation for building long-term and stable customer relationships.

[0051] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a business integration management system, etc. The following takes the business integration management system as an example to illustrate this embodiment and the following embodiments.

[0052] Based on this, the present application embodiment provides a core page performance determination method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the core page performance determination method of the present application.

[0053] In this embodiment, the core page performance determination method is applied to a business integration management system for managing a customer system, and includes steps S01 to S02:

[0054] Step S01, for any sub-application system under the client system, identifying each core page in the sub-application system and determining each key user using the sub-application system;

[0055] It should be noted that the business integration management system is a comprehensive platform for managing multiple independent customer systems. The customer system is an independent system managed by the business integration management system, usually corresponding to a specific business field or customer. The sub-application system is a functional module or subsystem under the customer system, which provides specific business functions. For each sub-application system, through multi-dimensional analysis of its number of visits, number of visits, page attributes, etc., combined with the preset core page evaluation algorithm, the pages that are critical to business operations, namely the core pages, are identified. These core pages usually carry key business functions, are the focus of frequent user visits and interactions, and can also be pages that senior management of the enterprise has permission to access.

[0056] In addition, it should be noted that the users of the sub-application system are considered based on factors such as user roles, access frequency, and number of access functions, and the key users of the sub-application system are determined in combination with a preset key user evaluation algorithm. Key users refer to users who use the system frequently and have a large impact on the business, such as senior corporate executives, high-frequency system users, etc. Their usage experience has an important impact on the evaluation of system performance.

[0057] In addition, it should be noted that when evaluating core pages and key users, after the preliminary results are determined by the preset core page evaluation algorithm and the preset key user evaluation algorithm, the determined preliminary results can also be reviewed in combination with the core page evaluation model and the key user evaluation model, and the pages that meet the preset core page evaluation algorithm and are in the predicted results of the core page evaluation model are taken as core pages, and the users that meet the preset key user evaluation algorithm and are in the predicted results of the key user evaluation model are taken as key users, wherein the core page evaluation model is trained by historical core page data, and the key user evaluation model is trained by historical key user data.

[0058] It is understandable that the existing solution performs indiscriminate evaluation on all pages and users, resulting in low evaluation efficiency and failure to timely detect whether the user experience of important system users has been affected. Therefore, step S01 is performed to achieve accurate evaluation by identifying core pages and key users, thereby improving the pertinence and efficiency of the evaluation, reducing unnecessary waste of resources, and providing clear goals and scope for subsequent steps.

[0059] Step S02, based on the user behavior data of the sub-application system, each key user and each core page, determine whether the core page performance index of the sub-application system meets the standard.

[0060] It should be noted that since software suppliers have various data on customer system access, such as the number of visits and duration of each person's visits to each page at each time point, they can obtain access data such as users and pages of all systems, core pages and core people maintained by all operation and maintenance engineers, standard thresholds of all core pages (if the threshold is exceeded, the page access is considered to have timed out), and various functional points and page information in the system. Among them, the focus is on information related to users, pages, etc., that is, user behavior data. User behavior data refers to the behavior records of users accessing the system, such as the number of visits, duration, request response time, etc. User data and scenario data are determined through user behavior data. User data refers to the performance data of key users accessing any page, and scenario data refers to the performance data of key scenarios accessed by any user.

[0061] Specifically, the business integration management system's log recording, user behavior tracking and other functions are used to collect user behavior data generated by users in each sub-application system when they perform operations in the system, including but not limited to visit time, number of clicks, length of stay, page loading speed, etc.

[0062] In addition, it should be noted that based on the collected user behavior data and combined with the preset performance indicators, the core pages of each sub-application system are evaluated for performance. The core page performance indicators are key indicators for measuring the performance of core pages, such as page loading time, response time, error rate, etc. The evaluation obtains the compliance details of the core page performance indicators. The compliance details refer to a detailed report on whether the core page performance indicators meet the preset standards, which should list in detail the performance indicators, compliance status, potential problems and improvement suggestions for each core page.

[0063] It is understandable that since the existing solutions are evaluated based on static tests or theoretical models, there are deviations from the actual situation, so step S02 is performed to provide performance evaluation results based on actual user behavior by combining user behavior data, which is closer to the actual needs of users, thereby determining whether the performance of core scenarios used by core users is affected, thereby improving user experience and business efficiency.

[0064] In a feasible implementation, in step S01, the step of identifying each core page in the sub-application system includes steps A01-A02:

[0065] Step A01, when the sub-application system is a personalized system, collect attribute tags of each page, the number of user visits to each page within a first preset period, and the number of page visits;

[0066] It should be noted that the sub-application system includes personalized systems and standardized systems, among which, a personalized system refers to a system that has been customized to a certain extent according to customer needs. Compared with a standardized system, it may contain some specific functions or pages. The business integration management system automatically collects relevant data on user access to each page within a first preset period (such as a month or a quarter), including the number of user visits, the number of page visits, and the attribute label of the page. The number of user visits refers to the total number of users who visit a certain page within the first preset period, the number of page visits refers to the total number of times the page is visited by users within a specified period, and the attribute label refers to a specific attribute of the page, such as "senior level only", which means that the page is mainly used for senior company executives or specific user groups.

[0067] In addition, it should be noted that when each customer initially purchases a customer system, it is basically shipped in the form of a standardized system. For the standardized system, the administrator will use common and general standardized scenarios such as amounts and customer project information as core pages, and import the core pages into the database for centralized management.

[0068] Step A02: determine as a core page a page whose number of user visits reaches a preset user number threshold and whose number of page visits reaches a preset page visit number threshold, or whose attribute tag is a preset attribute.

[0069] It should be noted that, based on the preset core page evaluation algorithm, if a page is visited by enough users within the first preset period (the number of user visits reaches the preset user number threshold), and the frequency of these users' visits to the page is also high enough (the number of page visits reaches the preset page visit number threshold), then this page is likely to be a core page, wherein the preset user number threshold and the preset page visit number threshold are used to determine whether a page is "hot" enough to become a core page. For example, the preset user number threshold may be 20% of the total number of active users, and the preset page visit number threshold may be visited more than 18 days per month. If a page is marked with a preset attribute (such as "senior level only"), it is directly determined to be a core page regardless of its number of visits and number of users, because these pages usually carry important decision-making information.

[0070] For example, for a sub-application system of a personalized system type, the preset core page evaluation algorithm may be:

[0071] ① The number of users who visit the page each month accounts for 20% of the total number of active users this month;

[0072] ②The page is visited more than 18 days per month;

[0073] ③This page is for senior management only;

[0074] The scenario where conditions ① and ② are met at the same time, and condition ③ is met alone, is used as the core page.

[0075] In this embodiment, by collecting the number of users who visit the page, the number of page visits and the attribute tags of the page within the first preset period, the system can obtain comprehensive data on page usage, which provides an important basis for subsequent core page determination. By setting a preset user number threshold and a preset page visit number threshold, and combining the attribute tags of the page, the system can automatically and accurately determine which pages are core pages. By accurately identifying core pages, the system can focus on monitoring and optimizing these pages, thereby ensuring that the performance and experience of core users are not affected.

[0076] In a feasible implementation manner, in step S01, the step of determining each key user using the sub-application system includes steps A11 to A12:

[0077] Step A11, collecting the number of system accesses and the number of access functions of each user to the sub-application system within the second preset period;

[0078] It should be noted that for each user who uses the sub-application system, the system automatically records and collects the number of system visits and the number of function visits within the second preset period (such as one month). The number of system visits refers to the total number of times a user visits the sub-application system within a specified period, reflecting the user's activity and frequency of use; the number of function visits refers to the number of different functions visited by a user within a specified period, reflecting the user's degree of exploration of system functions and depth of use.

[0079] Step A12: determine the user whose system access times reach a preset system access threshold and whose access function number reaches a preset function number threshold as a key user.

[0080] It should be noted that each customer system is visited by many users every day. However, since senior corporate executives and high-frequency system users have a lot of daily business, if the work efficiency of these personnel is hindered due to the performance of the system pages, it will affect the image in the minds of customers. Therefore, it is necessary to pay special attention to these key users and the pages they visit. Generally speaking, administrators will have some understanding of the application personnel of the customer systems they are responsible for, and can directly import these identified key users into the database for centralized management.

[0081] In addition, it should be noted that although the administrator may be able to identify some key users due to his or her familiarity with the business, there are likely to be potential key users that have not been identified. For key users that have not been identified, through the preset key user evaluation algorithm, if the user's system access times reach the preset system access threshold (such as accessing the system for more than 18 days per month), and the number of accessed functions reaches the preset function number threshold (such as the number of functions accessed per month accounts for more than 20% of the overall function data), then the system automatically determines the user as a key user, wherein the preset system access threshold is used to determine whether the number of times a user accesses the system within a specified period meets the standard of a key user, such as accessing the system for more than 18 days per month. This threshold can be adjusted according to actual business conditions. The preset function number threshold is a ratio or a specific value used to determine whether the number of functions accessed by a user within a specified period meets the standard of a key user, such as the number of functions accessed per month accounts for more than 20% of the overall function data. This threshold can also be adjusted according to actual business conditions.

[0082] Exemplarily, for each user using the client system, the preset key user evaluation algorithm may be:

[0083] ①Access the system for more than 18 days per month;

[0084] ②The number of monthly access functions accounts for more than 20% of the overall function data;

[0085] Users who meet both conditions ① and ② are considered key users.

[0086] In addition, it should be noted that for each sub-application system, some pages may experience a sudden increase in visits during a specific time period. Therefore, these pages can be directly marked as core pages during a specific time period of each day / week / month / year. Specifically, within a preset time slot (daily / weekly / monthly / yearly), the performance of a certain page is detected, and the high-frequency time period when the performance of the page does not meet the standard is recorded. The corresponding slot of the high-frequency time period is determined. Under the corresponding slot, the page is directly recorded as a core page when it reaches the high-frequency time period.

[0087] For example, for the sales system in the customer system, since employees or managers need to check their performance at the end of the month, there will be a sudden increase in visits to the performance page at the end of each month. Therefore, in the last week of each month, the performance page is used as the core page and its indicators need to be evaluated.

[0088] In this implementation, by collecting the number of times users access the system and the number of functions accessed within the second preset period, the system can comprehensively record the user's usage behavior and provide data support for subsequent analysis. By accurately recording each access and the usage of system functions, the system can ensure the accuracy of the data and avoid data omissions or errors. By setting preset system access thresholds and preset function number thresholds, the system can accurately identify key users. For users who are determined to be key users, the system can further analyze the core functions or scenarios they access and monitor their performance, which helps to promptly discover and resolve performance bottlenecks and improve user experience.

[0089] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 2 In step S02, based on the user behavior data of the sub-application system, each key user and each core page, the step of determining whether the core page performance index of the sub-application system meets the standard includes steps S11 to S13:

[0090] Step S11, for any one of the key users, judging whether the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system through the user behavior data of the sub-application system;

[0091] It should be noted that data related to core page performance is obtained from software manufacturers and system operation and maintenance data warehouses, including but not limited to the number of visits and duration of each person to each page at each time point. Specifically, the operation and maintenance data warehouse is used to directly extract user and page access data from each customer system, and obtain information on all pages identified as core pages and core users. This information is the focus of subsequent evaluations. The access timeout standard threshold for each core page is determined as a benchmark for evaluating whether the page performance meets the standards. The various functional points of the customer system and the corresponding page information are collected to better understand the business logic behind the user behavior data.

[0092] In addition, it should be noted that the personal dimension evaluation requirements are specific evaluation conditions set for key users, which are used to evaluate performance issues that key users may encounter when using the system. By analyzing user behavior data, it is determined whether the personal dimension evaluation requirements are met when key users access each page in the sub-application system.

[0093] Step S12: for any one of the core pages, judging whether the core page meets the page dimension evaluation requirements when accessed by each user through the user behavior data of the sub-application system;

[0094] It should be noted that the page dimension evaluation requirements refer to specific evaluation conditions set for core pages, which are used to evaluate the performance of core pages. By analyzing user behavior data, it is determined whether the core pages meet the page dimension evaluation requirements when visited by each user.

[0095] Step S13, when each key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system, and each core page meets the page dimension evaluation requirements when accessed by each user, it is determined that the core page performance indicators of the sub-application system meet the standards.

[0096] It should be noted that, based on steps S11 and S12, the performance of each key user access page and each core page when accessed is comprehensively judged. If both dimensions meet the evaluation requirements, the core page performance index of the sub-application system is judged to be up to standard; otherwise, it is judged to be not up to standard.

[0097] In this implementation, by setting personal dimension evaluation requirements and page dimension evaluation requirements, the system can accurately identify whether there are performance issues when key users use the system and whether there are performance issues when core pages are accessed, providing strong support for subsequent optimization. By comprehensively considering the evaluation results of personal dimensions and page dimensions, the system can give a comprehensive and accurate judgment, which not only improves the stability and reliability of system performance, but also improves user experience and satisfaction.

[0098] In a feasible implementation, in step S11, the step of determining whether the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system includes steps B01 to B03:

[0099] Step B01, for any one of the pages of the sub-application system, collecting the number of timeouts in which the response time of a key user accessing the page exceeds a standard threshold within a third preset period, and the first total number of times the key user accesses the page within the third preset period;

[0100] It should be noted that the response time data of key users accessing each page within the third preset period (such as one day or one week) is collected, where the response time refers to the time required for the user to initiate a request to fully load the page, and is an important indicator for evaluating page performance. The standard threshold is set according to business needs. Access with a response time exceeding this value is considered a timed access. The number of timeouts refers to the number of times the response time exceeds the standard threshold when the key user accesses the page within the third preset period; the first total number is the total number of times the key user accesses the page within the third preset period.

[0101] Step B02, when the ratio of the number of timeouts to the first total number of times reaches a first timeout ratio threshold, and the first total number of times reaches a first preset access threshold, it is determined that the key user meets the first sub-requirement of the personal dimension evaluation requirement when accessing each page in the sub-application system;

[0102] It should be noted that, based on the collected data, the ratio of the number of timeouts to the first total number (i.e., the timeout ratio) is calculated and compared with the set first timeout ratio threshold. At the same time, it is also necessary to determine whether the first total number reaches the first preset access threshold. These two conditions together constitute the standard for determining whether the key user access page meets the first sub-requirement of the personal dimension evaluation requirement. Among them, the first timeout ratio threshold is used to determine whether the timeout access is frequent enough to affect the user experience. The first preset access threshold is a minimum number of visits set to ensure the reliability of the evaluation results and avoid evaluation bias caused by too few visits.

[0103] Step B03, determining a first satisfaction number of the first sub-demand being satisfied within a fourth preset period, and determining that the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system when the first satisfaction number reaches a first preset satisfaction threshold.

[0104] It should be noted that, based on the preliminary evaluation, the number of times the first sub-demand is met (i.e., the first number of satisfaction times) within the fourth preset period (e.g., 7 consecutive days) is further determined, and the first number of satisfaction times is compared with the set first preset satisfaction threshold (e.g., 4 days) to determine whether the personal dimension evaluation requirements are met when the key user visits the page.

[0105] For example, the individual dimension assessment requirements may be:

[0106] For any key user among the key users, when the key user visits any page:

[0107] Condition ①: The number of times the user visits the page for more than 3 seconds per day / the total number of times the user visits the page per day >= 10%;

[0108] Condition ②: The total number of times the user visits the page every day is greater than or equal to 5 times;

[0109] Condition ③: 4 out of 7 consecutive days meet conditions ① and ②;

[0110] When conditions ① and ② are met, the first sub-requirement of the personal dimension evaluation requirements is determined to be met. If the above three conditions are met, it is considered that the personal dimension evaluation requirements are met, and the core page performance indicators of this customer system do not meet the standards. As long as any set of sub-application system core page performance indicators in the customer system fails, it is considered that the core page performance indicators of the customer system fail.

[0111] In this implementation, data collection provides basic data support for subsequent evaluation, ensuring the accuracy and objectivity of the evaluation. Through preliminary evaluation, pages with frequent timeouts and sufficient access times can be screened out, providing an important basis for subsequent comprehensive evaluation. Through comprehensive evaluation, the performance of key users when accessing the page can be judged more comprehensively, ensuring the accuracy and reliability of the evaluation results.

[0112] In a feasible implementation manner, in step S12, the step of determining whether the core page meets the page dimension evaluation requirement when accessed by each user includes steps B11 to B13:

[0113] Step B11, collecting the number of requests whose response time exceeds the standard threshold when the core page is accessed within the fifth preset period, and the second total number of times the core page is accessed within the fifth preset period;

[0114] It should be noted that the response time data when the core page is accessed within the fifth preset period is collected, wherein the fifth preset period is usually a fixed time period, such as a day or a week, and is used to count the response time when the core page is accessed within the time period. The number of requests refers to the number of requests whose response time of the core page exceeds the standard threshold within the fifth preset period, and the second total number is the total number of times the core page is accessed within the fifth preset period.

[0115] Step B12: when the ratio of the number of requests to the second total number of requests reaches the second timeout ratio threshold, and the second total number of requests reaches the second preset access threshold, it is determined that the core page meets the second sub-requirement of the page dimension evaluation requirement when accessed by each user;

[0116] It should be noted that, based on the collected data, the ratio of the number of requests to the second total number (i.e., the timeout ratio) is calculated and compared with the set timeout ratio threshold (the second timeout ratio threshold). At the same time, it is determined whether the second total number reaches the second preset access threshold. These two conditions together constitute the standard for determining whether the core page meets the second sub-requirement of the page dimension evaluation requirement when it is accessed. Among them, the second timeout ratio threshold is a set proportion value, which is used to determine whether the core page timeout requests are frequent enough to affect the user experience. The second preset access threshold is a set minimum number of visits, which is used to ensure the reliability of the evaluation results.

[0117] Step B13, determining a second satisfaction number of times the second sub-demand is satisfied within a sixth preset period, and when the second satisfaction number reaches a second preset satisfaction threshold, determining that the core page satisfies the page dimension evaluation requirement when accessed by each user.

[0118] It should be noted that, based on the preliminary evaluation, the number of times the second sub-demand is met (i.e., the second satisfaction number) within the sixth preset period (e.g., 7 consecutive days) is further determined, and the second satisfaction number is compared with the set second preset satisfaction threshold (e.g., 5 days) to determine whether the core page meets the page dimension evaluation requirements when it is visited. The sixth preset period is a set continuous time period for counting the number of times the second sub-demand is met. The second satisfaction number is the number of days that the second sub-demand is met within the sixth preset period, i.e., within this period, the number of days that simultaneously meet the conditions that the timeout ratio exceeds the second timeout ratio threshold and the number of visits reaches the second preset visit threshold. The second preset satisfaction threshold is a set minimum satisfaction number, which is used to determine whether there are persistent performance problems when the core page is visited.

[0119] For example, the page dimension evaluation requirements may be:

[0120] For any core page among the core pages, when the core page is accessed by any user:

[0121] Sub-step S02-2-1: Setting personal dimension assessment conditions

[0122] When key users visit a page, set the following evaluation criteria:

[0123] Condition ①: For any core page, the number of requests that take more than 3 seconds accounts for ≥ 10% of the total number of visits.

[0124] Condition ②: The total number of visits to the core page per day is ≥ 25 times.

[0125] Condition ③: The same core page meets both conditions ① and ② for 5 out of 7 consecutive days;

[0126] When conditions ① and ② are met, the second sub-requirement of the page dimension evaluation requirement is determined to be met. If the above three conditions are met, it is considered that the page dimension evaluation requirement is met, and the core page performance indicators of this customer system do not meet the standards. As long as any set of sub-application system core page performance indicators in the customer system fails, it is considered that the core page performance indicators of the customer system fail.

[0127] In this implementation, by counting the number of requests and the second total number, we can have a preliminary understanding of the performance of the core pages, provide basic data support for subsequent evaluations, and ensure the accuracy and objectivity of the evaluations. Through preliminary evaluations, we can screen out core pages with frequent timeout requests and sufficient access times, which provides an important basis for subsequent comprehensive evaluations. Through comprehensive evaluations, we can more comprehensively judge the performance of the core pages when they are accessed, and ensure the accuracy and reliability of the evaluation results.

[0128] In a feasible implementation manner, in step S02, after determining whether the core page performance index of the sub-application system meets the standard, steps B21 to B22 are also included:

[0129] Step B21, when the core page performance index does not meet the standard, determine the key users that do not meet the personal dimension evaluation requirements, the core pages that do not meet the page dimension evaluation requirements, and the corresponding sub-application systems, and output the sub-application systems, key users, and core pages;

[0130] It should be noted that when the core page performance indicators do not meet the standards, the system needs to determine which key users, core pages, and sub-application systems do not meet the assessment requirements of the personal dimension and page dimension, and output the above data as the compliance details, including but not limited to key information such as sub-application systems, key users, core pages, etc. This information will be used for subsequent problem location and governance.

[0131] In addition, it should be noted that when the performance indicators of the core pages do not meet the standards and the details of meeting the standards are fed back, the details of meeting the standards may also include performance problems, solutions and page jump links. After the system determines that the abnormal core page has occurred, it detects the performance indicators of the core page and determines the performance indicators with unqualified indicator status to determine the performance problem, and searches for the corresponding solutions to the performance problems in the preset problem solution table, and outputs the performance problems, solutions and page jump links of the core pages whose performance does not meet the standards. Among them, the preset problem solution table combines the work experience of operation and maintenance engineers and expert suggestions, including common performance problems and solutions.

[0132] In addition, it should be noted that if the corresponding performance problem and solution are not matched in the preset problem solution table, the corresponding indicator status of each performance indicator of the core page that does not meet the performance standard will be pushed to the operation and maintenance engineer as a detail file. After the operation and maintenance engineer solves the problem, he will add the performance problem and solution to the preset problem solution table.

[0133] In addition, it should be noted that after determining the core page whose performance does not meet the requirements, the status of the core page can be evaluated through a preset problem analysis model to obtain the performance problems and recommended solutions of the core page. At the same time, a page jump link can be generated, and the performance problems, solutions and page jump links can be output to the operation and maintenance engineers.

[0134] For example, to help understand the technical concept or technical principle of this application, please refer to Figure 3 and Figure 4 , Figure 3 A schematic diagram of the target details page is provided, such as Figure 3As shown in the figure, the performance of this core page fails, and the actual deduction is 3 points, with an impact description and expert suggestions. By clicking the "Details" button A, you can jump to the core performance problem details page, as shown in the figure below. Figure 4 As shown, Figure 4 A schematic diagram of the core performance problem details page is provided, where "Page" corresponds to the core page with substandard performance, "Object" corresponds to the sub-application system to which the core page with substandard performance belongs, and "Jump Link" corresponds to the page details of the core page with substandard performance. Click "Page Details" to jump directly to the core page with substandard performance to troubleshoot and repair the problem.

[0135] Step B22: When the core page performance index reaches the target, output a target-reaching notification to each sub-application system.

[0136] It should be noted that when the core page performance indicators meet the standards, the system needs to output a compliance notification for each sub-application system. A compliance notification is a prompt message sent by the system to users or system administrators to inform them that the core page performance indicators of the sub-application system have met the preset evaluation standards.

[0137] In this implementation, by determining the details of compliance when the standards are not met, the system can provide users with specific and detailed non-compliance information, which helps users quickly understand the problem. By outputting compliance notifications, the system can provide users with an intuitive feedback mechanism, allowing users to understand the operating status of the system in a timely manner, which helps to improve user experience.

[0138] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the core page performance determination method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0139] The present application also provides a core page performance determination device, which is applied to a business integration management system, and the business integration management system is used to manage customer systems. Please refer to Figure 5 , the core page performance determination device includes:

[0140] The identification module 10 is used to identify the core pages in any sub-application system under the client system and determine the key users who use the sub-application system;

[0141] The judgment module 20 is used to determine whether the core page performance index of the sub-application system meets the standard based on the user behavior data of the sub-application system, each key user and each core page.

[0142] Optionally, the identification module 10 is further used for:

[0143] In the case where the sub-application system is a personalized system, the attribute tags of each page, the number of user visits to each page within the first preset period, and the number of page visits are collected;

[0144] A page whose user access number reaches a preset user number threshold and whose page access number reaches a preset page access number threshold, or whose attribute tag is a preset attribute, is determined as a core page.

[0145] Optionally, the identification module 10 is further used for:

[0146] Collect the number of system accesses and the number of access functions of each user to the sub-application system within the second preset period;

[0147] Users whose system access times reach a preset system access threshold and whose access functions reach a preset function number threshold are determined as key users.

[0148] Optionally, the judging module 20 is further configured to:

[0149] For any key user among the key users, the user behavior data of the sub-application system is used to determine whether the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system;

[0150] For any core page among the core pages, the user behavior data of the sub-application system is used to determine whether the core page meets the page dimension evaluation requirements when accessed by each user;

[0151] When each key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system, and each core page meets the page dimension evaluation requirements when accessed by each user, the core page performance indicators of the sub-application system are determined to have met the standards.

[0152] Optionally, the judging module 20 is further configured to:

[0153] For any one of the pages of the sub-application system, collect the number of timeouts during which the response time of a key user accessing the page exceeds a standard threshold within a third preset period, and the first total number of times the key user accesses the page within the third preset period;

[0154] When the ratio of the number of timeouts to the first total number of times reaches a first timeout ratio threshold, and the first total number of times reaches a first preset access threshold, it is determined that the key user meets the first sub-requirement of the personal dimension evaluation requirement when accessing each page in the sub-application system;

[0155] Determine a first satisfaction number of the first sub-demand being satisfied within a fourth preset period, and when the first satisfaction number reaches a first preset satisfaction threshold, determine that the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system.

[0156] Optionally, the judging module 20 is further configured to:

[0157] Collecting the number of requests for which the response time exceeds the standard threshold when the core page is accessed within the fifth preset period, and the second total number of times the core page is accessed within the fifth preset period;

[0158] When the ratio of the number of requests to the second total number of requests reaches the second timeout ratio threshold, and the second total number of requests reaches the second preset access threshold, it is determined that the core page meets the second sub-requirement of the page dimension evaluation requirement when accessed by each user;

[0159] Determine a second satisfaction number of times the second sub-demand is satisfied within a sixth preset period, and when the second satisfaction number reaches a second preset satisfaction threshold, determine that the core page satisfies the page dimension evaluation requirement when accessed by each user.

[0160] Optionally, the judging module 20 is further configured to:

[0161] When the core page performance indicators do not meet the standards, determine the key users that do not meet the individual dimension evaluation requirements, the core pages that do not meet the page dimension evaluation requirements, and the corresponding sub-application systems, and output the sub-application systems, key users, and core pages;

[0162] When the core page performance indicators meet the standards, notifications of compliance are output for each sub-application system.

[0163] The core page performance determination device provided by the present application adopts the core page performance determination method in the above embodiment, which can solve the technical problem of how to determine whether the core scene performance used by the core user is affected. Compared with the prior art, the beneficial effects of the core page performance determination device provided by the present application are the same as the beneficial effects of the core page performance determination method provided by the above embodiment, and other technical features in the core page performance determination device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0164] The present application provides an electronic device, which includes: 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 so that the at least one processor can execute the core page performance determination method in the above-mentioned embodiment one.

[0165] Reference below Figure 6, which shows a schematic diagram of the structure of an electronic device suitable for implementing an embodiment of the present application. The electronic device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, notebook computers, PADs (Portable Application Description: tablet computers), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0166] like Figure 6 As shown, the electronic device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the electronic device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a microphone, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows an electronic device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0167] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0168] The electronic device provided by the present application adopts the core page performance determination method in the above embodiment, which can solve the technical problem of how to determine whether the core scene performance used by the core user is affected. Compared with the prior art, the beneficial effects of the electronic device provided by the present application are the same as the beneficial effects of the core page performance determination method provided in the above embodiment, and the other technical features in the electronic device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0169] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0170] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0171] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, the computer-readable program instructions being used to execute the core page performance determination method in the above-mentioned embodiment.

[0172] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.

[0173] The computer-readable storage medium may be included in the electronic device, or may exist independently without being installed in the electronic device.

[0174] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by an electronic device, the core page performance determination device is applied to a business integration management system. The business integration management system is used to manage customer systems. For any sub-application system under the customer system, it can identify the core pages in the sub-application system and determine the key users who use the sub-application system; based on the user behavior data of the sub-application system, the key users and the core pages, it is determined whether the core page performance indicators of the sub-application system meet the standards.

[0175] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0176] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0177] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0178] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned core page performance determination method, and can solve the technical problem of how to determine whether the core scene performance used by the core user is affected. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the core page performance determination method provided by the above-mentioned embodiment, and will not be repeated here.

[0179] The present application also provides a computer program product, including a computer program, which implements the steps of the core page performance determination method as described above when the computer program is executed by a processor.

[0180] The computer program product provided by this application can solve the technical problem of how to determine whether the performance of the core scene used by the core user is affected. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the core page performance determination method provided by the above embodiment, which will not be repeated here.

[0181] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A method for determining core page performance, characterized in that: Applied to a business integration management system, the business integration management system is used to manage customer systems, the core page performance determination method includes: For any sub-application system under the client system, identify each core page in the sub-application system, and determine each key user who uses the sub-application system based on whether the number of system accesses and the number of accessed functions of each user in the second preset period reach the preset system access threshold and the preset function number threshold, respectively, wherein the number of accessed functions refers to the number of different functions accessed by the user in the second preset period, the core page also meets the prediction result of the core page evaluation model, and the key user also meets the prediction result of the key user evaluation model; Based on the user behavior data of the sub-application system, the key users and the core pages, it is determined whether the core page performance index of the sub-application system meets the standard.

2. The core page performance determination method according to claim 1, characterized in that: The step of identifying each core page in the sub-application system comprises: In the case where the sub-application system is a personalized system, collecting attribute tags of each page, the number of user visits to each page within a first preset period, and the number of page visits; The page whose user access quantity reaches a preset user quantity threshold and whose page access times reaches a preset page access times threshold, or whose attribute tag is a preset attribute, is determined as a core page.

3. The core page performance determination method according to claim 1, characterized in that: The step of determining whether the core page performance index of the sub-application system meets the standard based on the user behavior data of the sub-application system, the key users and the core pages comprises: For any one of the key users, judging whether the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system through the user behavior data of the sub-application system; For any one of the core pages, judging whether the core page meets the page dimension evaluation requirements when accessed by each user through the user behavior data of the sub-application system; When the individual dimension evaluation requirements are met when each key user accesses each page in the sub-application system, and when each core page meets the page dimension evaluation requirements when accessed by each user, it is determined that the core page performance index of the sub-application system meets the standard.

4. The core page performance determination method as claimed in claim 3, characterized in that: The step of determining whether the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system includes: For any one of the pages of the sub-application system, collecting the number of timeouts during which the response time of the key user accessing the page exceeds a standard threshold within a third preset period, and the first total number of times the key user accesses the page within the third preset period; When the ratio of the number of timeouts to the first total number of times reaches a first timeout ratio threshold, and the first total number of times reaches a first preset access threshold, it is determined that the key user meets the first sub-requirement of the personal dimension evaluation requirement when accessing each page in the sub-application system; Determine a first number of times the first sub-demand is satisfied within a fourth preset period, and when the first number of times reaches a first preset satisfaction threshold, determine that the key user meets the personal dimension evaluation requirements when accessing each page in the sub-application system.

5. The core page performance determination method as claimed in claim 3, characterized in that: The step of determining whether the core page meets the page dimension evaluation requirements when accessed by each user includes: Collecting the number of requests for which the response time exceeds the standard threshold when the core page is accessed within the fifth preset period, and the second total number of times the core page is accessed within the fifth preset period; When the ratio of the number of requests to the second total number of times reaches a second timeout ratio threshold, and the second total number of times reaches a second preset access threshold, it is determined that the core page meets the second sub-requirement of the page dimension evaluation requirement when accessed by each user; Determine a second number of times the second sub-demand is satisfied within a sixth preset period, and when the second number of times reaches a second preset satisfaction threshold, determine that the core page meets the page dimension evaluation requirement when accessed by each user.

6. The core page performance determination method as claimed in claim 3, characterized in that: After the step of determining whether the core page performance index of the sub-application system meets the standard, the following step is further performed: When the core page performance index does not meet the standard, determine the key users that do not meet the personal dimension evaluation requirements, the core pages that do not meet the page dimension evaluation requirements, and the corresponding sub-application systems, and output the sub-application systems, the key users, and the core pages; When the core page performance index reaches the standard, a standard-reaching notification of each sub-application system is output.

7. An electronic device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the core page performance determination method according to any one of claims 1 to 6.

8. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the core page performance determination method according to any one of claims 1 to 6 are implemented.

9. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the core page performance determination method according to any one of claims 1 to 6 are implemented.

Images