A method for monitoring the execution speed of an SDS storage domain and related components

Abstract

The application discloses a method for monitoring the execution speed of an SDS storage domain and related components, and relates to the field of SDS storage domains, which obtains the current execution time of the current operation of the SDS, and then judges that the current operation may have a problem when the current execution time is greater than the execution time threshold corresponding to the current operation, and controls the prompt module to send corresponding first prompt information. Since the current execution time in the application is recorded for a specific operation, the application can accurately determine which operation has a problem.

Description

Technical Field

[0001] This invention relates to the field of SDS storage domains, and in particular to a method and related components for monitoring the execution speed of an SDS storage domain. Background Technology

[0002] In cloud computing management platforms, Software Defined Storage (SDS) is an essential component of Hyper Converged Infrastructure (HCI). The performance of SDS directly determines the performance of HCI, therefore, monitoring the performance of SDS is indispensable.

[0003] In existing technologies, performance metrics for SDS typically only include the transmission rate and usage of the relevant hardware. For example, the utilization rate of SDS storage and cache resources, and the transmission rate of storage data migration and recovery. Since multiple different operations may be performed simultaneously during the execution of a current operation on an SDS, without indicators that directly reflect the execution status of a specific operation, it is difficult to determine which specific operation is experiencing a problem based solely on the transmission rate and usage of the relevant hardware.

[0004] In view of the above-mentioned technical problems, finding a solution to these problems is an urgent issue for those skilled in the art. Summary of the Invention

[0005] The purpose of this invention is to provide a method and related components for monitoring the execution speed of an SDS storage domain. By obtaining the current execution time of a specific operation and comparing the current execution time with an execution time threshold, it is possible to accurately determine which specific operation has a problem.

[0006] To address the aforementioned technical problems, this invention provides a method for monitoring the execution speed of an SDS storage domain, comprising:

[0007] Get the current execution time used by SDS to perform the current operation;

[0008] When the current execution time exceeds the execution time threshold, the control prompt module issues a corresponding first prompt message, wherein the execution time threshold corresponds one-to-one with the current operation.

[0009] Preferably, obtaining the current execution time used by the SDS to perform the current operation includes:

[0010] The first execution time taken by SDS from platform layer operation to calling the underlying layer when performing the current operation, the second execution time taken by the underlying layer operation, and the third execution time taken from the underlying layer back to the front end are obtained;

[0011] The sum of the first execution time, the second execution time, and the third execution time is determined as the current execution time.

[0012] Preferably, obtaining the current execution time used by the SDS to perform the current operation includes:

[0013] The first execution time taken by SDS from platform layer operation to calling the underlying layer when performing the current operation, the second execution time taken by the underlying layer operation, and the third execution time taken from the underlying layer back to the front end are obtained;

[0014] When the current execution time is greater than the execution time threshold, including:

[0015] If the first execution time is greater than the first execution time threshold, or the second execution time is greater than the second execution time threshold, or the third execution time is greater than the third execution time threshold, it is determined that the current execution time is greater than the execution time threshold.

[0016] The control prompt module issues the corresponding first prompt message, including:

[0017] The control prompt module issues the first prompt message corresponding to operations that exceed its own execution time threshold.

[0018] Preferably, the process of determining the execution time threshold includes:

[0019] Determine all historical execution times used by SDS to perform the current operation within the target historical time period;

[0020] The average execution time used by SDS to perform the current operation is determined based on all the historical execution times.

[0021] The execution time threshold is determined based on the average execution time.

[0022] Preferably, determining the execution time threshold based on the average execution time includes:

[0023] The execution time threshold is determined as N times the average execution time, where N is not less than 1.

[0024] Preferably, after the control prompt module issues the corresponding first prompt message, it further includes:

[0025] Upon receiving an instruction to draw an execution time distribution map, determine all optimized execution times used by SDS to perform the current operation within a preset time period prior to receiving the instruction;

[0026] Based on all the optimized execution times, an execution time distribution graph is plotted, where the horizontal axis of the execution time distribution graph is time and the vertical axis is the probability density corresponding to the time.

[0027] When the execution time distribution map does not conform to a normal distribution when the execution time is from 0 to N times the average execution time, the control prompt module issues a corresponding second prompt message.

[0028] Preferably, after obtaining the current execution time used by the SDS to perform the current operation, the method further includes:

[0029] Determine whether the current execution time is not greater than the maximum execution time threshold, wherein the maximum execution time threshold is greater than the execution time threshold;

[0030] If so, proceed to the step where the control prompt module issues a corresponding first prompt when the current execution time exceeds the execution time threshold;

[0031] If not, the control prompt module will issue a corresponding third prompt message.

[0032] To address the aforementioned technical problems, this invention also provides a system for monitoring the execution speed of an SDS storage domain, comprising:

[0033] The current execution time acquisition unit is used to acquire the current execution time used by SDS to perform the current operation.

[0034] The first prompting unit is used to control the prompting module to issue a corresponding first prompting message when the current execution time is greater than the execution time threshold, wherein the execution time threshold corresponds one-to-one with the current operation.

[0035] To address the aforementioned technical problems, the present invention also provides a device for monitoring the execution speed of an SDS storage domain, comprising:

[0036] Memory, used to store computer programs;

[0037] A processor, used to implement the steps of the method for monitoring the execution speed of an SDS storage domain as described in any of the preceding claims when executing the computer program.

[0038] To address the aforementioned technical problems, the present invention also provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the method for monitoring the execution speed of an SDS storage domain as described in any of the preceding claims.

[0039] This invention provides a method for monitoring the execution speed of an SDS storage domain. By obtaining the current execution time used by the SDS to perform the current operation, and then determining that there may be a problem with the current operation when the current execution time is greater than the execution time threshold corresponding to the current operation, the control prompt module issues the corresponding first prompt information. Since the current execution time in this invention is recorded for a specific operation, it can accurately determine which specific operation has a problem.

[0040] The present invention also provides a system, device and storage medium for monitoring the execution speed of an SDS storage domain, which has the same beneficial effects as the methods described above. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the prior art and embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 A flowchart illustrating a method for monitoring the execution speed of an SDS storage domain, provided in an embodiment of the present invention;

[0043] Figure 2 This is a structural diagram of a system for monitoring the execution speed of an SDS storage domain, provided in an embodiment of the present invention.

[0044] Figure 3 This is a structural diagram of a device for monitoring the execution speed of an SDS storage domain, provided as an embodiment of the present invention. Detailed Implementation

[0045] The core of this invention is to provide a method and related components for monitoring the execution speed of an SDS storage domain. By obtaining the current execution time of a specific operation and comparing the current execution time with an execution time threshold, it is possible to accurately determine which specific operation has a problem.

[0046] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0047] Please refer to Figure 1 , Figure 1A flowchart of a method for monitoring the execution speed of an SDS storage domain, provided as an embodiment of the present invention, is included in the following:

[0048] S11: Get the current execution time used by SDS to perform the current operation;

[0049] S12: When the current execution time exceeds the execution time threshold, the control prompt module issues the corresponding first prompt message. The execution time threshold corresponds one-to-one with the current operation.

[0050] In practical implementation, this method is applied to a cloud computing management platform. The execution entity for steps S11 and S12 is the server. Operations performed on the SDS can be divided into two types: query operations and operation operations. Query operations involve retrieving relevant information from the SDS, such as node information, SDS service information, SDS LUN information, and system virtual machine information. Operation operations involve creating, modifying, and deleting the aforementioned relevant information in the SDS. Generally, operation operations take longer to execute than query operations.

[0051] The current operation in step S11 can be a query operation or an operation operation. It can be one type of operation or multiple types of operations. To obtain the current execution time corresponding to the current operation, one can either set a probe on the code of the current operation to directly obtain the current execution time of the complete operation, or set probes on segments of the code of the current operation and add the execution times of different code segments of the same operation to obtain the current execution time. Further details regarding obtaining the current execution time can be found in the following embodiments.

[0052] For step S12, since the current execution time varies significantly for different operations within the same operation type, an execution time threshold corresponds one-to-one with each specific operation. The determination of the execution time threshold is illustrated in the following embodiment. When the current execution time exceeds the execution time threshold, the control prompt module issues a corresponding first prompt message. When the current execution time exceeds the execution time threshold, it is determined that the current operation is executing too slowly and may be abnormal. Issuing the first prompt message serves to alert administrators, allowing them to optimize the current operation. The first prompt message can be the name of the current operation and a message indicating an abnormality. The specific content of the prompt message is not limited; it can also include the specific value of the current execution time and the specific value of the execution time threshold. Furthermore, it can include the transmission rate and usage of relevant hardware, such as the utilization rate of SDS storage and cache resources, and the transmission rate of storage data migration and recovery.

[0053] The method for monitoring the execution speed of an SDS storage domain provided in this embodiment obtains the current execution time used by the SDS to perform the current operation, and then determines that there may be a problem with the current operation when the current execution time is greater than the execution time threshold corresponding to the current operation. The control prompt module issues the corresponding first prompt information. Since the current execution time in this invention is recorded for a specific operation, it can accurately determine which specific operation has a problem.

[0054] Based on the above embodiments:

[0055] As a preferred embodiment, obtaining the current execution time used by the SDS to perform the current operation includes:

[0056] Get the first execution time taken by SDS from platform layer operation to calling the underlying layer when performing the current operation, the second execution time taken by the underlying layer operation, and the third execution time taken from the underlying layer to return to the front end;

[0057] The sum of the first execution time, the second execution time, and the third execution time is determined as the current execution time.

[0058] It should be noted that the call process for operations executed on SDS is from the front end to the platform layer and then to the bottom layer, and the return process is from the bottom layer back to the platform layer and then back to the front end. Since the call time from the front end to the platform layer is basically not much different, it is not statistically significant. The execution time is concentrated in the first execution time used to call the bottom layer from the platform layer operation, the second execution time used for the bottom layer operation, and the third execution time used to return from the bottom layer to the front end. Therefore, the first execution time, the second execution time, and the third execution time are statistically analyzed in layers, and then the statistically significant execution times are added together to obtain the current execution time.

[0059] This embodiment provides a specific implementation method for obtaining the current execution time used by SDS to perform the current operation. By layering the current operation and excluding the execution time that is not statistically significant from the statistics of the current execution time, it makes it faster to obtain the current execution time corresponding to the current operation and improves the acquisition efficiency.

[0060] As a preferred embodiment, obtaining the current execution time used by the SDS to perform the current operation includes:

[0061] Get the first execution time taken by SDS from platform layer operation to calling the underlying layer when performing the current operation, the second execution time taken by the underlying layer operation, and the third execution time taken from the underlying layer to return to the front end;

[0062] When the current execution time is greater than the execution time threshold, including:

[0063] If a first execution time is greater than a first execution time threshold, a second execution time is greater than a second execution time threshold, or a third execution time is greater than a third execution time threshold, the current execution time is determined to be greater than the execution time threshold.

[0064] The control prompt module issues the corresponding first prompt message, including:

[0065] The control prompt module issues the first prompt message corresponding to operations that exceed its own execution time threshold.

[0066] It should be noted that the specific explanations of the first execution time used by the SDS to call the underlying layer from the platform layer operation to the underlying layer, the second execution time used by the underlying layer operation, and the third execution time used to return from the underlying layer to the front end when performing the current operation can be found in the above embodiments. The explanations of the first execution time threshold, the second execution time threshold, and the third execution time threshold are similar to the explanations of the execution time thresholds in the following embodiments, which can be found in the following embodiments.

[0067] The control prompt module issues a first prompt message corresponding to an operation whose execution time exceeds its own threshold. In other words, it provides separate prompts for the current operation after layering. For example, when the first execution time exceeds the first execution time threshold, the first prompt message may be a prompt that there is an abnormality in the process from the platform layer operation to the call to the underlying layer corresponding to the first execution time. Other explanations of the first prompt message can be found in the above embodiments.

[0068] This embodiment provides another specific implementation method for obtaining the current execution time used by SDS to execute the current operation. By layering the current operation, the current operation process is further subdivided, which can make the problem location accurate to a part of the current operation process.

[0069] As a preferred embodiment, the process of determining the execution time threshold includes:

[0070] Determine all historical execution times used by SDS to perform the current operation within the target historical time period;

[0071] Determine the average execution time of the current operation by SDS based on all historical execution times;

[0072] The execution time threshold is determined based on the average execution time.

[0073] In practice, the target historical time period can be set reasonably according to actual needs, such as a day or a month in history. The average execution time used by SDS to execute the current operation is determined based on all historical execution times. This means averaging all the historical execution times determined above and using this average as the average execution time corresponding to the current operation. There are no special restrictions on the specific method of determining the execution time threshold based on the average execution time. For example, N times the average execution time can be used as the execution time threshold.

[0074] This embodiment provides a specific implementation of the process for determining the execution time threshold, making full use of historical data to make the setting of the execution time threshold more reasonable.

[0075] As a preferred embodiment, determining the execution time threshold based on the average execution time includes:

[0076] The execution time threshold is determined as N times the average execution time, where N is not less than 1.

[0077] It should be noted that N is a real number not less than 1, but as a preferred embodiment, N is usually taken as 2.

[0078] This embodiment provides a specific implementation method for determining the execution time threshold based on the average execution time, which is relatively simple to implement.

[0079] In a preferred embodiment, after the control prompt module issues the corresponding first prompt message, it further includes:

[0080] Upon receiving an instruction to plot the execution time distribution, determine all optimized execution times used by the SDS to perform the current operation within a preset time period prior to receiving the instruction;

[0081] A time distribution graph is plotted based on all optimized execution times. The horizontal axis of the time distribution graph represents time, and the vertical axis represents the probability density corresponding to time.

[0082] When the execution time distribution graph from 0 to N times the average execution time does not conform to a normal distribution, the control prompt module issues a corresponding second prompt message.

[0083] In practice, after the control prompt module issues the corresponding first prompt information, the administrator optimizes the current operation with the problem based on the first prompt information. The optimization method can be to try to convert the synchronous call method with a long execution time in the operation into an asynchronous call method. Of course, there are other optimization methods, which are not limited here.

[0084] The instruction to send the execution time distribution chart can be sent periodically via program settings or manually by administrators. The specific explanations for the preset duration and the determination of optimized execution time are similar to those in the above embodiments, and will not be repeated here. The second prompt information can be all the content of the first prompt information in the above embodiments, or it can be the execution time distribution chart and / or the judgment result of whether the execution time distribution chart from 0 to N times the average execution time conforms to a normal distribution.

[0085] In this embodiment, after the control prompt module issues the corresponding first prompt message, it adds a judgment on whether the execution time distribution graph from 0 to N times the average execution time conforms to a normal distribution. When the execution time distribution graph from 0 to N times the average execution time does not conform to a normal distribution, it prompts the administrator that the current operation needs to be further optimized, ultimately achieving the effect of making the performance of SDS more stable.

[0086] In a preferred embodiment, after obtaining the current execution time used by the SDS to perform the current operation, the method further includes:

[0087] Determine if the current execution time is not greater than the maximum execution time threshold; if the maximum execution time threshold is greater than the execution time threshold.

[0088] If so, proceed to the step where the control prompt module issues the corresponding first prompt when the current execution time exceeds the execution time threshold;

[0089] If not, the control prompt module will issue a corresponding third prompt message.

[0090] In practice, the maximum execution time threshold can be set based on the different types of operations. For example, based on experience, the maximum execution time threshold can be set to 5 seconds for query operations and 30 minutes for operation operations. Of course, a corresponding maximum execution time threshold can also be set for each different operation. The description of the third prompt information is similar to that of the first prompt information in the above embodiment, and will not be repeated here.

[0091] This embodiment adds a preliminary judgment step after obtaining the current execution time used by SDS to perform the current operation. This step can achieve the preliminary judgment.

[0092] Please refer to Figure 2 , Figure 2 A structural diagram of a system for monitoring the execution speed of an SDS storage domain, provided in an embodiment of the present invention, is shown. The system includes:

[0093] Current execution time acquisition unit 1 is used to acquire the current execution time used by SDS to perform the current operation;

[0094] The first prompting unit 2 is used to control the prompting module to issue a corresponding first prompting message when the current execution time is greater than the execution time threshold. The execution time threshold corresponds one-to-one with the current operation.

[0095] As a preferred embodiment, the current execution time acquisition unit 1 includes:

[0096] The sub-execution time acquisition unit is used to acquire the first execution time taken by SDS from platform layer operation to calling the underlying layer when performing the current operation, the second execution time taken by the underlying layer operation, and the third execution time taken from the underlying layer to return to the front end.

[0097] The current execution time acquisition subunit is used to determine the sum of the first execution time, the second execution time, and the third execution time as the current execution time.

[0098] As a preferred embodiment, the current execution time acquisition unit 1 includes:

[0099] The sub-execution time acquisition unit is used to acquire the first execution time taken by SDS from platform layer operation to calling the underlying layer when performing the current operation, the second execution time taken by the underlying layer operation, and the third execution time taken from the underlying layer to return to the front end.

[0100] The first prompt unit 2 includes:

[0101] The determination unit is used to determine that the current execution time is greater than the execution time threshold when there is a first execution time greater than the first execution time threshold, a second execution time greater than the second execution time threshold, or a third execution time greater than the third execution time threshold;

[0102] The first prompt subunit is used to control the prompt module to issue the first prompt information corresponding to the operation that exceeds its own execution time threshold when it is determined that the current execution time is greater than the execution time threshold.

[0103] As a preferred embodiment, it also includes:

[0104] The historical execution time determination unit is used to determine all historical execution times used by SDS to execute the current operation within the target historical time period;

[0105] The average time determination unit is used to determine the average execution time used by the SDS to perform the current operation based on all historical execution times.

[0106] The execution time threshold determination unit is used to determine the execution time threshold based on the average execution time.

[0107] As a preferred embodiment, the execution time threshold determination unit includes:

[0108] The execution time threshold determination subunit is used to determine the execution time threshold as N times the average execution time, where N is not less than 1.

[0109] As a preferred embodiment, it also includes:

[0110] The optimized execution time determination unit is used to determine all the optimized execution time used by SDS to perform the current operation within a preset time before receiving the instruction to draw the execution time distribution map after the control prompt module issues the corresponding first prompt information.

[0111] The execution time distribution plotting unit is used to plot the execution time distribution based on all optimized execution times. The horizontal axis of the execution time distribution plot is time, and the vertical axis is the probability density corresponding to time.

[0112] The second prompting unit is used to control the prompting module to issue a corresponding second prompting message when the execution time distribution map from 0 to N times the average execution time does not conform to a normal distribution.

[0113] As a preferred embodiment, it also includes:

[0114] The judgment unit is used to determine whether the current execution time is not greater than the maximum execution time threshold after obtaining the current execution time used by SDS to perform the current operation. If the maximum execution time threshold is greater than the execution time threshold, the first prompt unit 2 is triggered; otherwise, the third prompt unit is triggered.

[0115] The third prompting unit is used to control the prompting module to issue corresponding third prompting information.

[0116] Since the embodiments of the system part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the system part, and they will not be repeated here.

[0117] Please refer to Figure 3 , Figure 3 This is a structural diagram of a device for monitoring the execution speed of an SDS storage domain, provided in an embodiment of the present invention. The device for monitoring the execution speed of an SDS storage domain includes:

[0118] Memory 20 is used to store computer programs;

[0119] The processor 21 is used to implement the steps of the method for monitoring the execution speed of the SDS storage domain as mentioned in the above embodiments when executing a computer program.

[0120] The device for monitoring the execution speed of the SDS storage domain provided in this embodiment may include, but is not limited to, smartphones, tablets, laptops, or desktop computers.

[0121] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one of the following hardware forms: Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as the central processing unit, is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a GPU, which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an Artificial Intelligence (AI) processor, which handles computational operations related to machine learning.

[0122] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory 20 is used to store at least the following computer program 201, which, after being loaded and executed by the processor 21, is capable of implementing the relevant steps of the method for monitoring the execution speed of the SDS storage domain disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, and the storage method may be temporary or permanent storage. The operating system 202 may include Windows, Unix, Linux, etc. The data 203 may include, but is not limited to, data related to the method for monitoring the execution speed of the SDS storage domain.

[0123] In some embodiments, the device for monitoring the execution speed of the SDS storage domain may further include a display screen 22, an input / output interface 23, a communication interface 24, a power supply 25, and a communication bus 26.

[0124] Those skilled in the art will understand that Figure 3 The structure shown does not constitute a limitation on the device for monitoring the execution speed of the SDS storage domain and may include more or fewer components than shown.

[0125] Finally, the present invention also provides an embodiment corresponding to a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps described in the above method embodiments.

[0126] It is understood that if the methods in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and executes all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0127] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0128] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for monitoring the execution speed of an SDS storage domain, characterized in that, include: Get the current execution time used by SDS to perform the current operation; When the current execution time exceeds the execution time threshold, the control prompt module issues a corresponding first prompt message, wherein the execution time threshold corresponds one-to-one with the current operation. The process of determining the execution time threshold includes: Determine all historical execution times used by SDS to perform the current operation within the target historical time period; The average execution time used by SDS to perform the current operation is determined based on all the historical execution times. The execution time threshold is determined based on the average execution time. Determining the execution time threshold based on the average execution time includes: The execution time threshold is determined as N times the average execution time, where N is not less than 1; After the control prompt module issues the corresponding first prompt message, it also includes: Upon receiving an instruction to draw an execution time distribution map, determine all optimized execution times used by SDS to perform the current operation within a preset time period prior to receiving the instruction; Based on all the optimized execution times, an execution time distribution graph is plotted, where the horizontal axis of the execution time distribution graph is time and the vertical axis is the probability density corresponding to the time. When the execution time distribution map does not conform to a normal distribution when the execution time is from 0 to N times the average execution time, the control prompt module issues a corresponding second prompt message.

2. The method for monitoring the execution speed of an SDS storage domain as described in claim 1, characterized in that, Get the current execution time used by SDS to perform the current operation, including: The first execution time taken by SDS from platform layer operation to calling the underlying layer when performing the current operation, the second execution time taken by the underlying layer operation, and the third execution time taken from the underlying layer back to the front end are obtained; The sum of the first execution time, the second execution time, and the third execution time is determined as the current execution time.

3. The method for monitoring the execution speed of an SDS storage domain as described in claim 1, characterized in that, Get the current execution time used by SDS to perform the current operation, including: The first execution time taken by SDS from platform layer operation to calling the underlying layer when performing the current operation, the second execution time taken by the underlying layer operation, and the third execution time taken from the underlying layer back to the front end are obtained; When the current execution time is greater than the execution time threshold, including: If the first execution time is greater than the first execution time threshold, or the second execution time is greater than the second execution time threshold, or the third execution time is greater than the third execution time threshold, it is determined that the current execution time is greater than the execution time threshold. The control prompt module issues the corresponding first prompt message, including: The control prompt module issues the first prompt message corresponding to operations that exceed its own execution time threshold.

4. The method for monitoring the execution speed of an SDS storage domain as described in any one of claims 1 to 3, characterized in that, After obtaining the current execution time used by SDS to perform the current operation, it also includes: Determine whether the current execution time is not greater than the maximum execution time threshold, wherein the maximum execution time threshold is greater than the execution time threshold; If so, proceed to the step where the control prompt module issues a corresponding first prompt when the current execution time exceeds the execution time threshold; If not, the control prompt module will issue a corresponding third prompt message.

5. A system for monitoring the execution speed of an SDS storage domain, characterized in that, include: The current execution time acquisition unit is used to acquire the current execution time used by SDS to perform the current operation. The first prompting unit is used to control the prompting module to issue a corresponding first prompting message when the current execution time is greater than the execution time threshold, wherein the execution time threshold corresponds one-to-one with the current operation; The system for monitoring the execution speed of SDS storage domains also includes: The historical execution time determination unit is used to determine all historical execution times used by the SDS to execute the current operation within the target historical time period. An average time determination unit is used to determine the average execution time used by the SDS to perform the current operation based on all the historical execution times. An execution time threshold determination unit is used to determine the execution time threshold based on the average execution time; The execution time threshold determination unit includes: An execution time threshold determination subunit is used to determine the execution time threshold as N times the average execution time, where N is not less than 1; The system for monitoring the execution speed of SDS storage domains also includes: The optimized execution time determination unit is used to determine all the optimized execution time used by SDS to perform the current operation within a preset time period before receiving the instruction to draw the execution time distribution map after the control prompt module issues the corresponding first prompt information. An execution time distribution plotting unit is used to plot an execution time distribution plot based on all the optimized execution times, wherein the horizontal axis of the execution time distribution plot is time, and the vertical axis is the probability density corresponding to the time. The second prompting unit is used to control the prompting module to issue a corresponding second prompting message when the execution time distribution map does not conform to a normal distribution within a time range of 0 to N times the average execution time.

6. A device for monitoring the execution speed of an SDS storage domain, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the method for monitoring the execution speed of an SDS storage domain as described in any one of claims 1 to 4 when executing the computer program.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method for monitoring the execution speed of an SDS storage domain as described in any one of claims 1 to 4.

Images