Test method for multiplexing computing node and related device

Abstract

The embodiment of the invention provides a testing method for multiplexing computing nodes and a related device. The method comprises the following steps: issuing a first traffic test task to a first computing link and issuing a second traffic test task to a second computing link; wherein the first flow test task and the second flow test task have different task identifiers; the first flow test task and the second flow test task comprise at least partially overlapped operation time periods; obtaining log data recorded corresponding to each traffic fragment in the process of executing the first traffic test task and the second traffic test task by the multiplexing computing node; wherein the processing result of the flow fragment is recorded in the log data of the multiplex computing node corresponding to the task identifier; the first flow test task and the second flow test task respectively comprise a plurality of flow fragments; and displaying a test result formed based on the log data. The test method and the related device for multiplexing the computing node can improve the test efficiency.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer software testing, and more particularly to a testing method and related apparatus for multiplexing computing nodes. Background Art

[0002] In the field of program testing, traditional automated testing methods are mainly based on the testing of a single computing node, which verifies the functions and performance of program modules by issuing test tasks to a single node and recording the test results.

[0003] In a distributed computing scenario, multiple computing links are usually composed of multiple computing nodes. Multiple computing links can process multiple task flows simultaneously.

[0004] In the prior art, each computing link is tested separately. For example, each computing node in the computing link is tested separately to reduce abnormal failures of the computing link. In some cases, different computing links may share the same computing node, which is used as a multiplexing computing node. The multiplexing computing node implements the operation logic used by multiple computing links. In the existing testing method, when testing a multiplexing computing node, it is necessary to use the test tasks corresponding to different computing links to test the multiplexing computing node.

[0005] Therefore, in the prior art, there is a problem of low testing efficiency for computing links in distributed computing scenarios. Summary of the invention

[0006] In view of this, multiple embodiments of the present application are dedicated to providing a testing method and related devices for multiplexing computing nodes, which can effectively improve the testing efficiency of computing links in distributed computing scenarios.

[0007] One embodiment of the present application provides a testing method for a multiplexed computing node, wherein the multiplexed computing node is applied to a first computing link and a second computing link, and the computing nodes included in the first computing link and the computing nodes included in the second computing link are partially different; the testing method comprises: issuing a first flow test task to the first computing link and issuing a second flow test task to the second computing link; wherein the first flow test task and the second flow test task have different task identifiers; the first flow test task and the second flow test task include at least partially overlapping running time periods; obtaining log data recorded for each flow slice during the execution of the first flow test task and the second flow test task by the multiplexed computing node; wherein the processing results of the flow slices are recorded corresponding to the task identifier in the log data of the multiplexed computing node; the first flow test task and the second flow test task respectively include multiple flow slices; and displaying the test results formed based on the log data.

[0008] One embodiment of the present application provides a testing device for a multiplexed computing node, wherein the multiplexed computing node is applied to a first computing link and a second computing link, and the computing nodes included in the first computing link and the computing nodes included in the second computing link are partially different; the testing device comprises: a task issuing module, used to issue a first flow test task to the first computing link and a second flow test task to the second computing link; wherein the first flow test task and the second flow test task have different task identifiers; the first flow test task and the second flow test task include at least partially overlapping running time periods; a log acquisition module, used to obtain log data recorded corresponding to each flow slice during the execution of the first flow test task and the second flow test task by the multiplexed computing node; wherein the processing results of the flow slices are recorded corresponding to the task identifier in the log data of the multiplexed computing node; the first flow test task and the second flow test task respectively include multiple flow slices; a display module, used to display the test results formed based on the log data.

[0009] One embodiment of the present application provides a computer device, which includes a memory and a processor, wherein the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the aforementioned test method for multiplexed computing nodes.

[0010] One embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores at least one computer program, and when the at least one computer program is executed by a processor, it can implement the aforementioned testing method for multiplexing computing nodes.

[0011] One embodiment of the present application provides a computer program product, which is used to implement the aforementioned testing method for multiplexing computing nodes.

[0012] In multiple implementations provided in the present application, by issuing traffic test tasks with different task identifiers to the first computing link and the second computing link, and obtaining log data corresponding to each traffic slice of the multiplexed computing node during the execution of each traffic test task during at least partially overlapping operating time periods, the processing results of the multiplexed computing node can be respectively associated with different task identifiers for recording and verification, thereby achieving efficient testing of the multiplexed computing nodes in a multi-computing link parallel scenario, and improving the test coverage and test efficiency in a distributed computing scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 A schematic diagram of an example application scenario of a test device for multiplexing computing nodes provided in accordance with an embodiment of the present application.

[0014] Figure 2 A schematic diagram of a flow test task configuration interface provided for one embodiment of the present application.

[0015] Figure 3 A schematic diagram of a testing method for multiplexing computing nodes provided in accordance with an embodiment of the present application.

[0016] Figure 4 A schematic diagram of a module of a testing device for multiplexing computing nodes provided in accordance with an embodiment of the present application.

[0017] Figure 5 A schematic diagram of a computer device provided for one embodiment of the present application. DETAILED DESCRIPTION

[0018] The technical solutions 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, rather than all of the embodiments.

[0019] In the description of the embodiments of the present application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0020] In the related art, in the field of program testing, traditional automated testing methods usually rely on independent testing of a single computing node, and verify the functions and performance of program modules through the test tasks and result records of a single node. However, with the widespread application of distributed computing, computing nodes in multiple computing links are often used to process multiple task flows in parallel, so the testing method of a single node is difficult to meet the testing requirements of distributed computing links.

[0021] Specifically, in a distributed computing environment, multiple computing links are composed of multiple computing nodes, and each computing link can process different traffic tasks in a parallel scenario to ensure the rapid processing and response efficiency of traffic tasks. However, in some cases, different computing links may include the same computing node, so that the computing node is reused by multiple computing links as a reused computing node. When testing reused computing nodes, traditional testing methods often need to issue test tasks to each computing link separately to verify the operation of the reused computing node in each computing link, but this testing method has low testing efficiency in a multi-link parallel environment.

[0022] As the complexity of distributed systems continues to increase, the number of multiplexed computing nodes will also increase, making the requirements for testing higher and higher. When multiplexed computing nodes perform multi-computing link tasks, they may process the traffic load of multiple computing links in overlapping time periods, and each traffic task includes different traffic shards. In this case, traditional sharding testing and single-link testing methods are difficult to fully cover the operation of the module, especially when multiplexed computing nodes process traffic tasks of multiple computing links. It takes a lot of testing time to improve the accuracy and coverage of the test.

[0023] Therefore, the existing technology still has the problem of low testing efficiency in distributed computing link testing.

[0024] In multiple implementations provided in the present application, the test method for multiplexing computing nodes can be applied to electronic devices with certain computing capabilities and network access capabilities. The electronic device can be a desktop computer, a laptop computer, a tablet computer, a smart phone, or a server. The electronic device can connect to each computing node through a network to perform the test task of the multiplexing computing node. Specifically, the electronic device includes a processor, a memory, and a network access module for network communication.

[0025] See also Figure 1. One embodiment of the present application provides an example of an application scenario of a test device for a multiplexed computing node. The test device can test the processing performance and task execution of the multiplexed computing node by assigning traffic test tasks to multiple computing links, so as to more efficiently verify the performance of the multiplexed computing node in a distributed system. The following uses a financial data processing system as an example to illustrate the test application of multiplexed computing nodes.

[0026] In this scenario example, the two computing links in the financial data processing system are responsible for different data processing tasks. For example, the first computing link is mainly used for customer information processing, and the second computing link is used for real-time risk control. The reuse computing node is deployed in the shared computing node and is responsible for providing data cleaning services for the two computing links.

[0027] The test requirements may be: the first computing link needs to process the cleaning task of customer data within a specific period of time, and the second computing link needs to execute the cleaning task for real-time transaction data in parallel. To this end, the test device generates a flow test task containing different task identifiers, and issues the first flow test task and the second flow test task to the first computing link and the second computing link respectively, ensuring that the flow test tasks overlap in part of the running period to simulate the workload of multiplexed computing nodes under the parallel operation of multiple computing links.

[0028] See also Figure 2 During the task configuration phase, the test device displays the flow test task configuration interface, where the user can view link information (such as link name and link type) and create corresponding flow test tasks. For example, if the user selects "customer data link" and generates the first flow test task, and selects "transaction data link" and generates the second flow test task, the test device can automatically assign different task identifiers 01 and 02 to the two flow test tasks in order to distinguish their respective processing results in the log data.

[0029] To facilitate log management in computing nodes, the test device provides a log switch control, which enables users to choose whether to enable the logging function during the test. When the log switch control is turned on, the computing nodes of the first computing link and the second computing link record the log data of their respective tasks, including the processing results, execution status and other necessary information of each traffic slice; when the log switch control is turned off, the log data is not recorded, thereby saving storage resources.

[0030] During the test, the test device collects log data of multiplexed computing nodes from computing nodes in different computing containers through a synchronization mechanism. Assuming that the computing nodes of the first computing link run in a Docker container and the computing nodes of the second computing link run in a virtual machine, the test device collects the log data of the two computing containers to the log collection system through a synchronization mechanism for unified display and analysis. The processing results of each traffic slice will be recorded in the log data for traceability and analysis.

[0031] In the test result display stage, the test device displays the test results of the first flow test task and the second flow test task based on the log data. For example, the result display of the first flow test task includes the success rate and processing time of each flow segment in the customer data cleaning process; while the display content of the second flow test task includes the accuracy and execution efficiency of transaction data cleaning. Users can intuitively view and compare the processing performance of the reused computing nodes under different link parallel loads through the result interface to identify potential performance bottlenecks.

[0032] In this scenario example, the test device effectively improved the test efficiency through multi-link parallel traffic testing and real-time display of log data.

[0033] See also Figure 3 . An embodiment of the present application provides a test method for a multiplexed computing node. The multiplexed computing node is applied to a first computing link and a second computing link, and the computing nodes included in the first computing link and the computing nodes included in the second computing link are partially different. The test method for a multiplexed computing node can be applied to a test device, and the test device can be the aforementioned electronic device or a program module running in the electronic device. The test method includes the following steps.

[0034] Step S110: issuing a first flow test task to the first computing link and issuing a second flow test task to the second computing link; wherein the first flow test task and the second flow test task have different task identifiers; and the first flow test task and the second flow test task include at least partially overlapping running time periods.

[0035] Step S120: Obtain the log data corresponding to each traffic shard recorded by the multiplexing computing node during the execution of the first traffic test task and the second traffic test task; wherein the processing result of the traffic shard recorded in the log data of the multiplexing computing node corresponds to the task identifier; the first traffic test task and the second traffic test task respectively include multiple traffic shards.

[0036] Step S130: displaying the test results formed based on the log data.

[0037] In this embodiment, the test device executes the test task of the multiplexed computing node by issuing the first flow test task and the second flow test task to the first computing link and the second computing link respectively. The first computing link and the second computing link respectively include multiple computing nodes, some of which are different. The program modules running in the computing nodes implement the corresponding processing logic. There is a computing node commonly used by the first computing link and the second computing link, and the computing node serves as a multiplexed computing node. During the test, the first flow test task and the second flow test task have different task identifiers and include at least partially overlapping running time periods to simulate the workload of the multiplexed computing node in a multi-link parallel environment.

[0038] In this embodiment, a computing node may refer to an independent computing unit in a distributed system. Each computing node may perform specific functions such as data processing, task execution, or computing operations. A computing node may have certain computing capabilities and storage capabilities. For example, a computing node may be a server, a virtual machine, or a container. Of course, a computing node may also refer to a program module running in a computing container.

[0039] In this embodiment, the computing node can process the flow test task assigned to the computing node. In this embodiment, the program of the computing node can be used to execute the specified operation logic to complete the corresponding function. Further, the program module can record log data, and the processing result of the program module executing the task is recorded in the log data. Of course, the log data can also record the execution process of the task.

[0040] In this embodiment, multiple computing nodes form a first computing link and a second computing link. The test device can control the first computing link and the second computing link to perform parallel testing to improve the overall test efficiency. In the process of executing the flow test task, the computing node records the processing results of each flow segment in the log data, which is convenient for tracking the execution of the flow segment.

[0041] In this embodiment, the first flow test task and the second flow test task generate multiple flow slices during operation. The flow slices are subtask units divided according to the task identifier and the flow load, which facilitates distributed parallel processing. The log data generated by each flow slice during the execution of the multiplexing computing node records the processing results of the flow slice and its execution status in the multiplexing computing node. The log data will be associated with the task identifier during the execution process for easy identification and used for subsequent test result analysis.

[0042] In this embodiment, the first flow test task and the second flow test task have at least partially overlapping running time periods, which means that the two flow test tasks are run in parallel in the same time period to simulate the execution performance of the reused computing node under the parallel load of multiple computing links. Through the design of such overlapping running time periods, the situation where multiple computing links in a distributed computing environment call the reused computing node at the same time can be more realistically simulated, thereby testing the stability and performance of the reused computing node under high-load parallel processing.

[0043] In this embodiment, the test device collects log data after the reused computing node completes the processing of the traffic slice. The log data includes the execution status, processing results, exception information, etc. of the traffic slice, which can help the test device to comprehensively evaluate the performance and stability of the reused computing node. By recording the processing of different task identifiers and traffic slices, the test device can achieve slice-level tracking of the reused computing node to accurately evaluate the processing capability of the reused computing node in a multi-link task scenario.

[0044] In this embodiment, the test device forms test results based on the collected log data, and displays the test results on the front-end platform through the display module, so that the tester can intuitively check the abnormal conditions during the test. The test results can show the execution path of traffic slicing, the performance of multiplexed computing nodes in different computing links, and the completion of tasks processed in parallel by multiple computing links.

[0045] In multiple implementations provided in the present application, by issuing traffic test tasks with different task identifiers to the first computing link and the second computing link, and obtaining log data corresponding to each traffic slice of the multiplexed computing node during the execution of each traffic test task during at least partially overlapping operating time periods, the processing results of the multiplexed computing node can be respectively associated with different task identifiers for recording and verification, thereby achieving efficient testing of the multiplexed computing nodes in a multi-computing link parallel scenario, and improving the test coverage and test efficiency in a distributed computing scenario.

[0046] In some embodiments, see Figure 2. The test device can display a flow test task configuration interface; wherein the flow test task configuration interface displays link information of the computing link and a task creation control corresponding to the link information; when the task creation control is triggered, a task configuration details interface is provided, and the task configuration details interface is used to configure the flow test task of the computing link represented by the link information; receive a user operation to generate a first flow test task for the first computing link and a second flow test task for the second computing link; when the designated task issuing control of the flow test task configuration interface is triggered, the first flow test task is issued to the first computing link, and the second flow test task is issued to the second computing link.

[0047] In this embodiment, the test device can provide a flow test task configuration interface for conveniently configuring and issuing flow test tasks for the first computing link and the second computing link. The flow test task configuration interface can be used to display the link information of the computing link that currently needs to be tested, and display it together with the task creation controls corresponding to each link information. Link information can be used to represent the computing link. Specifically, the link information can be the link identifier or link name of the computing link. In some embodiments, the link information can also include the specific configuration and structure of the computing link so that the user can identify and select the computing link to create a test task.

[0048] In this embodiment, when the user triggers the task creation control on the flow test task configuration interface, the test device provides a task configuration details interface. The task configuration details interface provides the user with more detailed parameter options so that the user can configure a suitable flow test task according to the link information. Specifically, the user can set the flow task quantity, flow slicing configuration and other parameters of the flow test task in the task configuration details interface to match the test requirements of different computing links. By providing the task configuration details interface, it is convenient for the user to set the flow test task as needed.

[0049] In this embodiment, after the task configuration is completed, the user can issue the flow test task through the designated task issuing control on the flow test task configuration interface. When the user triggers the designated task issuing control, the test device will automatically issue the configured first flow test task to the first computing link and issue the second flow test task to the second computing link. In this way, the test device can ensure that different links perform flow test tasks under the configuration conditions specified by the user, so as to efficiently test the reused computing nodes in a multi-link parallel environment.

[0050] In some embodiments, a log switch control is also provided in the flow test task configuration interface; when the log switch control is in an on state, the computing nodes in the first computing link and the computing nodes in the second computing link are allowed to record log data; or, when the log switch control is in a off state, the computing nodes in the first computing link and the computing nodes in the second computing link are not allowed to record log data.

[0051] In this embodiment, a log switch control is provided in the flow test task configuration interface, which is used to flexibly control the log data recording function of the first computing link and the second computing link, so as to reasonably utilize the limited storage space of the computing node. The log switch control allows the user to decide whether each computing node records log data through switch operation when configuring and issuing the flow test task. Specifically, when the log switch control is in the open state, the computing nodes in the first computing link and the second computing link are allowed to record log data. At this time, the computing node will record the processing results, execution status and other necessary operation information of each traffic slice in the log data during the execution of the flow test task, so as to track and analyze the execution of the traffic slice later. Correspondingly, when the log switch control is in the closed state, the computing nodes in the first computing link and the second computing link will not record log data, thereby avoiding unnecessary log information occupying the limited storage space in the computing node. In this way, when log recording is not required, the storage resources of the computing node will not be occupied unreasonably, which helps to improve the resource management efficiency of the overall system.

[0052] In some implementations, the computing nodes included in the first computing link each have different data processing logics, and the computing nodes included in the second computing link each have different data processing logics; the multiplexed computing nodes are applied to computing nodes in the first computing link and the second computing link that have the same data processing logic.

[0053] In this embodiment, the computing nodes in the first computing link and the second computing link have different data processing logics. Specifically, the data processing logic refers to the operation method and processing flow adopted by the computing node when performing traffic slicing or other tasks. For example, in the first computing link, one computing node can be used to process user information verification tasks to ensure that the user information in the traffic slicing is valid; while another computing node focuses on performing fatigue calculations to determine whether each traffic slicing meets the fatigue requirements. Similarly, in the second computing link, one computing node may be used to perform membership verification for a specific scenario, while another computing node is used to filter blacklisted users.

[0054] In this embodiment, the reused computing nodes can be deployed on computing nodes that require the same data processing logic in the first computing link and the second computing link. For example, if some computing nodes in both computing links need to perform the "send SMS" function, the computing node will deploy the same reused computing node to handle the sending task. In this embodiment, by reusing computing nodes, task processing consistency across computing links is achieved, avoiding the duplication of developing and maintaining the same functional modules for each link separately.

[0055] In some implementations, the computing nodes in the first computing link and the computing nodes in the second computing link respectively record log data, and the log data respectively records a processing result corresponding to each traffic slice.

[0056] In this embodiment, the computing nodes in the first computing link and the second computing link respectively record log data to track the operation of the multiplexed computing node during the execution of the flow test task. The log data is recorded in units of flow slices, and the processing results of each flow slice are independently stored in the log data for easy traceability analysis. Specifically, after receiving different flow test tasks, the computing nodes in the first computing link and the second computing link will process the flow slices one by one according to the task identifier, and record their respective processing results in the log data. The processing results may include information such as whether the processing is successful or not, the execution status, and the runtime performance, so as to better analyze the processing process of each flow slice in the multiplexed computing node in the subsequent process. For example, a computing node may record the processing of multiple flow slices, including its specific processing steps, abnormal information, and interaction information with other nodes. By storing the processing results of each flow slice independently in the log data, accurate recording of the processing process at the flow slice level is achieved, which is convenient for comprehensive and accurate analysis of the test results. Furthermore, log data combined with task identification and traffic sharding information helps to achieve shard-level tracking in scenarios where multiple computing links run in parallel, making it easier for testers to identify and analyze the processing behaviors of multiplexed computing nodes in different computing links.

[0057] In some embodiments, the computing nodes in the first computing link are at least partially located in different computing containers, and the computing nodes in the second computing link are at least partially located in different computing containers. The testing device can obtain log data of the program module from the computing nodes in multiple computing containers through a synchronization mechanism.

[0058] In this embodiment, the computing nodes in the first computing link and the second computing link are respectively located in different computing containers so as to perform the flow test task in an isolated environment. Specifically, the computing container refers to a virtualization unit, such as a container or a virtual machine, for providing an independent computing space for the computing node. In a distributed system, deploying computing nodes in independent computing containers can ensure that the task processing and data management of each computing node are isolated from each other, while improving the stability of task execution during the test.

[0059] In this embodiment, the test device can collect log data from computing nodes located in multiple computing containers through a synchronization mechanism. Specifically, the computing container can synchronously send the log data to the test device during the process of the program module recording the log data, so that the test device can quickly collect the log data recorded by multiple program modules. Of course, a log collection system can also be provided, and a data synchronization mechanism can be provided between the multiple computing containers and the log collection system, so that the computing container can send the log data recorded by the program module to the log collection system in real time. Furthermore, the log collection system can collect and organize multiple log data and provide them to the test device to display the test results.

[0060] In some implementations, the log data recorded by different program modules may adopt a unified content format, so as to facilitate data analysis after the log data is collected by the corresponding task identifier.

[0061] In some implementations, the testing device may display the test results of the first flow test task and the test results of the second flow test task respectively based on the log data of the multiplexed computing node.

[0062] In this embodiment, the test device can display the test results of the first flow test task and the second flow test task based on the log data of the multiplexed computing node. Specifically, the task identifier contained in the log data and the processing results of the flow slices are summarized separately to form independent test result displays for the first flow test task and the second flow test task. Through this independent display mode, the test device can display the execution status and processing performance of each flow test task respectively, thereby helping the tester to more intuitively analyze the performance of the multiplexed computing node under different test tasks. In some embodiments, during the display process, the test results can include detailed data such as the execution path, abnormal information, and processing time of each flow slice, which helps to identify the response behavior of the multiplexed computing node under different computing links and traffic loads. For example, the test device can display the execution of the first flow test task in detail in the display interface, display the specific processing results of the task on each flow slice on multiple computing nodes, and can also display the execution details of the second flow test task in another part of the interface, so as to directly compare the processing performance and stability of different tasks.

[0063] In some implementations, the test result display module can also provide filtering and sorting functions, so that testers can quickly locate and analyze according to task identification, traffic slicing execution status or abnormal conditions. In addition, the test device can further summarize and analyze the log data of different test tasks, generate charts or data reports, so as to evaluate the overall processing performance of the reused computing nodes in a multi-link parallel scenario, thereby improving the efficiency of the test process and the comprehensiveness of information display.

[0064] See also Figure 4 One embodiment of the present application also provides a test device for multiplexing computing nodes. The multiplexing computing nodes are applied to a first computing link and a second computing link, and the computing nodes included in the first computing link and the computing nodes included in the second computing link are partially different. The test device includes: a task issuing module, a log acquisition module and a display module.

[0065] A task issuing module is used to issue a first flow test task to the first computing link and a second flow test task to the second computing link; wherein the first flow test task and the second flow test task have different task identifiers; and the first flow test task and the second flow test task include at least partially overlapping running time periods.

[0066] A log acquisition module is used to obtain the log data corresponding to each traffic shard recorded during the execution of the first traffic test task and the second traffic test task by the multiplexing computing node; wherein the processing result of the traffic shard recorded in the log data of the multiplexing computing node corresponds to the task identifier; the first traffic test task and the second traffic test task respectively include multiple traffic shards.

[0067] The display module is used to display the test results formed based on the log data.

[0068] In this embodiment, the specific functions and effects achieved by the test device for multiplexing computing nodes can be explained with reference to other embodiments of the present application and will not be repeated here.

[0069] The embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the processor implements the aforementioned testing method for multiplexing computing nodes.

[0070] The embodiment of the present application also provides a computer program product including instructions, and when the computer program product is executed by a processor, the test method for multiplexing computing nodes as described above is implemented.

[0071] See also Figure 5 The present description embodiment may provide a computer device, the computer device comprising: a memory, and one or more processors communicatively connected to the memory; the memory stores instructions executable by the one or more processors, the instructions are executed by the one or more processors, so that the one or more processors implement the aforementioned test method for multiplexing computing nodes.

[0072] In some embodiments, the computer device may include a processor, a non-volatile storage medium, an internal memory, a communication interface, a display device, and an input device connected by a system bus. The non-volatile storage medium may store an operating system and related computer programs.

[0073] The user information or user account information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, etc.) involved in multiple implementation methods of the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0074] It should be understood that the specific examples in this article are only intended to help those skilled in the art to better understand the embodiments of the present application, rather than to limit the scope of the present invention.

[0075] It can be understood that in the various implementations of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the implementation methods of the present application.

[0076] It can be understood that the various embodiments described in this application can be implemented individually or in combination, and the embodiments of this application are not limited to this.

[0077] Unless otherwise stated, all technical and scientific terms used in the embodiments of the present application have the same meaning as those generally understood by those skilled in the art of the technical field of the present application. The terms used in the present application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the present application. The term "and / or" used in the present application includes any and all combinations of one or more related listed items. The singular forms of "a kind of", "above" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0078] It can be understood that the processor of the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method implementation can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (DigitalSignal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiment of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0079] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0080] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0081] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method implementation methods and will not be repeated here.

[0082] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0083] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0084] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0085] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0086] The above is only a specific implementation of the present application, but the protection scope of the present invention 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 invention should be based on the protection scope of the claims.

Claims

1. A test method for multiplexing computing nodes, characterized in that: The multiplexed computing node is applied to a first computing link and a second computing link, and the computing nodes included in the first computing link and the computing nodes included in the second computing link are partially different; the testing method includes: issuing a first flow test task to the first computing link and issuing a second flow test task to the second computing link; wherein the first flow test task and the second flow test task have different task identifiers; and the first flow test task and the second flow test task include at least partially overlapping running time periods; Obtain log data corresponding to each traffic slice recorded by the multiplexing computing node during the execution of the first traffic test task and the second traffic test task; wherein the processing result of the traffic slice is recorded corresponding to the task identifier in the log data of the multiplexing computing node; the first traffic test task and the second traffic test task respectively include multiple traffic slices; The test results formed based on the log data are displayed.

2. The testing method according to claim 1, characterized in that: The step of issuing a first flow test task to the first computing link and issuing a second flow test task to the second computing link includes: Displaying a flow test task configuration interface; wherein the flow test task configuration interface displays link information of a computing link and a task creation control corresponding to the link information; when the task creation control is triggered, providing a task configuration details interface, wherein the task configuration details interface is used to configure a flow test task for the computing link represented by the link information; Receive a user operation to generate a first flow test task for the first computing link and a second flow test task for the second computing link; When the designated task issuing control of the flow test task configuration interface is triggered, the first flow test task is issued to the first computing link, and the second flow test task is issued to the second computing link.

3. The testing method according to claim 2, characterized in that: The flow test task configuration interface is also provided with a log switch control; When the log switch control is in the on state, the computing nodes in the first computing link and the computing nodes in the second computing link are allowed to record log data; or, When the log switch control is in the off state, the computing nodes in the first computing link and the computing nodes in the second computing link are not allowed to record log data.

4. The testing method according to claim 1, characterized in that: The computing nodes included in the first computing link have different data processing logics respectively, and the computing nodes included in the second computing link have different data processing logics respectively; the multiplexed computing nodes are applied to the computing nodes with the same data processing logic in the first computing link and the second computing link.

5. The testing method according to claim 1, characterized in that: The computing nodes in the first computing link and the computing nodes in the second computing link respectively record log data, and the log data respectively records processing results corresponding to each traffic slice.

6. The testing method according to claim 5, characterized in that: The computing nodes in the first computing link are at least partially located in different computing containers, and the computing nodes in the second computing link are at least partially located in different computing containers; The step of obtaining log data recorded for each traffic slice respectively during the execution of the first traffic test task and the second traffic test task by the multiplexing computing node includes: Through the synchronization mechanism, the log data of the program module is obtained from the computing nodes in multiple computing containers.

7. The testing method according to claim 1, characterized in that: The step of displaying the test results formed based on the log data comprises: Based on the log data of the multiplexed computing node, the test results of the first flow test task and the test results of the second flow test task are displayed respectively.

8. A test device for multiplexing computing nodes, characterized in that: The multiplexed computing nodes are applied to the first computing link and the second computing link, and the computing nodes included in the first computing link and the computing nodes included in the second computing link are partially different; The testing device comprises: A task issuing module, used for issuing a first flow test task to the first computing link and issuing a second flow test task to the second computing link; wherein the first flow test task and the second flow test task have different task identifiers; the first flow test task and the second flow test task include at least partially overlapping running time periods; A log acquisition module, used to obtain log data recorded for each traffic slice respectively during the execution of the first traffic test task and the second traffic test task by the multiplexing computing node; wherein the processing result of the traffic slice is recorded corresponding to the task identifier in the log data of the multiplexing computing node; the first traffic test task and the second traffic test task respectively include multiple traffic slices; The display module is used to display the test results formed based on the log data.

9. A computer device, characterized in that: The computer device includes a memory and a processor, wherein at least one computer program is stored in the memory, and the at least one computer program is loaded and executed by the processor to implement the test method for a multiplexed computing node as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one computer program, and when the at least one computer program is executed by a processor, the method for testing a multiplexed computing node according to any one of claims 1 to 7 can be implemented.

11. A computer program product, characterized in that The computer program product is used to implement the test method for a multiplexed computing node as claimed in any one of claims 1 to 7.

Images