技术领域technical field
本申请涉及计算机技术领域，尤其涉及一种业务执行的方法及装置。The present application relates to the field of computer technology, and in particular to a method and device for service execution.
背景技术Background technique
为了满足人们的日常生活需求，当前，诸多的线上平台为用户提供了多种多样的业务模式，用户可通过这些线上平台提供的业务模式，来完成一些先前需要去线下完成的业务，从而极大的提高了用户处理业务的效率，为用户的日常生活带来了方便。In order to meet people's daily needs, many online platforms currently provide users with a variety of business models. Users can use the business models provided by these online platforms to complete some businesses that previously needed to be completed offline. Thereby, the efficiency of the user's business processing is greatly improved, and the daily life of the user is brought convenience.
在实际应用中，线上平台提供的诸多业务通常可分别核心业务与非核心业务，例如，对于微博业务来说，浏览微博这项业务就属于核心业务，而微博业务中涉及的广告推送业务则属于非核心业务，换句话说，核心业务应是整个业务中最重要的业务之一，而非核心业务对于整个业务的影响则不大。因此，当服务器处于高负载的情况时，为了保证核心业务的正常运行，通常会将非核心的业务进行降级，例如，将非核心业务的超时时间进行缩短，或直接关闭该非核心业务，这样一来，由于非核心业务得到了降级，使得非核心业务减少或不再占用服务器的资源，因此，服务器可将大部分的资源分配给核心业务，从而有效的保证了核心业务在服务器处于高负载运行情况下的正常运行。In practical applications, many businesses provided by online platforms can usually be divided into core business and non-core business. The push business is a non-core business. In other words, the core business should be one of the most important businesses in the whole business, and the non-core business has little impact on the whole business. Therefore, when the server is under high load, in order to ensure the normal operation of the core business, the non-core business is usually downgraded, for example, the timeout period of the non-core business is shortened, or the non-core business is directly closed, so that First, since the non-core business has been downgraded, the non-core business reduces or no longer occupies server resources. Therefore, the server can allocate most of the resources to the core business, thus effectively ensuring that the core business is under high load on the server. Normal operation under operating conditions.
然而，在现有技术中，通常都是采用人工的方式来对非核心业务进行降级的，即，当服务器处于高负载运行的情况时，线上业务的维护人员需要手动的去将非核心业务的超时时间进行修改，或停用该非核心业务，这样一来，就给线上业务的维护人员在维护线上业务的正常运行工作中带来了不便，不仅如此，若线上业务的维护人员在服务器出现高负载运行的情况时，没有及时的将非核心业务的超时时间进行修改或停用该非核心业务，则将会对核心业务的运行造成影响，进而给用户在使用该核心业务的过程中带来不便。However, in the prior art, the non-core business is usually downgraded manually, that is, when the server is running under high load, the maintenance personnel of the online business need to manually downgrade the non-core business Modify the timeout period of the online business, or disable the non-core business. In this way, it will bring inconvenience to the maintenance personnel of the online business in maintaining the normal operation of the online business. Not only that, if the maintenance of the online business If the personnel fail to modify the timeout period of the non-core business or disable the non-core business in a timely manner when the server is running under a high load, the operation of the core business will be affected, and the user's use of the core business will be affected. inconvenience in the process.
发明内容Contents of the invention
本申请实施例提供一种业务执行的方法，用于解决现有技术中非核心业务的降级过程中会给线上业务的维护人员带来不便的问题。The embodiment of the present application provides a method for service execution, which is used to solve the problem in the prior art that the maintenance personnel of online services will be inconvenienced during the process of degrading non-core services.
本申请实施例提供一种业务执行的装置，用于解决现有技术中非核心业务的降级过程中会给线上业务的维护人员带来不便的问题。The embodiment of the present application provides a service execution device, which is used to solve the problem in the prior art that the maintenance personnel of online services will be inconvenienced during the process of degrading non-core services.
本申请实施例采用下述技术方案：The embodiment of the application adopts the following technical solutions:
本申请实施例提供一种业务执行的方法，包括：The embodiment of this application provides a method for service execution, including:
根据针对业务预设的用于调整超时时间的各个调整周期，在当前调整周期到来时，确定所述业务在各历史调整周期对应的各历史超时时间；According to each adjustment cycle preset for adjusting the time-out time for the business, when the current adjustment cycle arrives, determine each historical time-out time corresponding to each historical adjustment cycle of the business;
根据所述各历史超时时间，确定所述业务在当前调整周期对应的超时时间；According to each historical time-out time, determine the time-out time corresponding to the service in the current adjustment period;
根据所述业务在当前调整周期对应的超时时间，执行所述业务。The service is executed according to the timeout period corresponding to the service in the current adjustment period.
本申请实施例提供一种业务执行的装置，包括：The embodiment of this application provides a service execution device, including:
第一确定模块，用于根据针对业务预设的用于调整超时时间的各个调整周期，在当前调整周期到来时，确定所述业务在各历史调整周期对应的各历史超时时间；The first determination module is configured to determine each historical timeout time corresponding to each historical adjustment period of the business when the current adjustment period arrives according to each adjustment period preset for the service for adjusting the timeout period;
第二确定模块，用于根据所述各历史超时时间，确定所述业务在当前调整周期对应的超时时间；The second determination module is configured to determine the timeout time corresponding to the service in the current adjustment period according to the historical timeout time;
执行模块，用于根据所述业务在当前调整周期对应的超时时间，执行所述业务。An execution module, configured to execute the service according to the timeout period corresponding to the service in the current adjustment period.
本申请实施例提供了一种业务执行的方法及装置，该方法中服务器可根据针对业务预设的调整超时时间的各调整周期，确定当前周期到来时，确定出该业务在各历史调整周期对应的各历史超时时间，而后，服务器可根据确定出的各历史超时时间，确定出该业务在当前调整周期对应的超时时间，继而根据确定出的当前调整周期对应的超时时间，对该业务进行执行。从上述方法中可以看出，由于服务器可根据该业务的历史超时时间，确定出该业务在当前调整周期对应的超时时间，因此，当服务器出现高负载运行的状况时，服务器可根据以往在这一时段出现高负载时该业务所对应的历史超时时间，确定出该业务在当前高负载时段所对应的超时时间，进而完成了该业务在当前高负载时段的自动调整，相对于现有技术而言，服务器在对业务进行降级时无需线上业务的维护人员亲自手段来修改该业务的超时时间，从而极大的提高了线上业务的维护人员在对业务进行降级过程中的便利性。The embodiment of the present application provides a method and device for service execution. In this method, the server can determine the arrival of the current period according to each adjustment period of the preset adjustment timeout period for the service, and determine that the service corresponds to each historical adjustment period. Each historical timeout time, then, the server can determine the timeout time corresponding to the current adjustment period of the business according to each determined historical timeout time, and then execute the business according to the determined timeout time corresponding to the current adjustment period . It can be seen from the above method that since the server can determine the timeout period corresponding to the service in the current adjustment cycle based on the historical timeout period of the service, when the server is running under high load, the server can The historical timeout time corresponding to the business when a period of high load occurs, determine the timeout time corresponding to the business in the current high load period, and then complete the automatic adjustment of the business in the current high load period, compared with the existing technology In other words, when the server downgrades the service, the maintenance personnel of the online service do not need to personally modify the timeout period of the service, thereby greatly improving the convenience of the maintenance personnel of the online service in the process of downgrading the service.
附图说明Description of drawings
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：The drawings described here are used to provide a further understanding of the application and constitute a part of the application. The schematic embodiments and descriptions of the application are used to explain the application and do not constitute an improper limitation to the application. In the attached picture:
图1为本申请实施例提供的业务执行的过程；Figure 1 is the process of service execution provided by the embodiment of the present application;
图2为本申请实施例提供的一种业务执行的系统示意图；FIG. 2 is a schematic diagram of a service execution system provided by an embodiment of the present application;
图3为本申请实施例提供的业务执行的装置示意图。Fig. 3 is a schematic diagram of a device for executing a service provided by an embodiment of the present application.
具体实施方式detailed description
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments of the present application and corresponding drawings. Apparently, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.
以下结合附图，详细说明本申请各实施例提供的技术方案。The technical solutions provided by various embodiments of the present application will be described in detail below in conjunction with the accompanying drawings.
图1为本申请实施例提供的业务执行的过程，具体包括以下步骤：Figure 1 is the process of service execution provided by the embodiment of the present application, which specifically includes the following steps:
S101：根据针对业务预设的用于调整超时时间的各个调整周期，在当前调整周期到来时，确定所述业务在各历史调整周期对应的各历史超时时间。S101: According to each adjustment period preset for the service for adjusting the timeout time, when the current adjustment period arrives, determine each historical timeout time corresponding to each historical adjustment period of the service.
在实际应用中，当服务器在一些特定的时段或节假日会出现高负载运行的情况，线上业务的维护人员为了保证高负载情况出现时，服务器中的核心业务能够顺利运行，通常情况下，都是将非核心业务进行降级，以使服务器更多的资源能够分配到核心业务中去，从而保证核心业务的顺利运行，其中，将非核心业务进行降级通常所采用的手段是将非核心业务在高负载时段的超时时间缩短，这样一来，服务器在出现高负载运行的情况时，用户针对非核心业务发送的业务请求的响应时间一旦超出了非核心业务在高负载时段的超时时间，服务器将不会在对该业务请求进行处理，所以，非核心业务在高负载时段的超时时间的缩短将会导致服务器拒绝更多的用户针对该非核心业务发送的业务请求，这样就使得在高负载时段，服务器可将更多的资源分配给核心业务，以保证核心业务在此时段的顺利运行。In practical applications, when the server runs under high load during some specific time periods or holidays, in order to ensure that the core business of the server can run smoothly when the high load occurs, the online business maintenance personnel usually It is to downgrade the non-core business, so that more resources of the server can be allocated to the core business, so as to ensure the smooth operation of the core business. The timeout period of the high-load period is shortened. In this way, when the server is running under high load, once the response time of the service request sent by the user for the non-core business exceeds the timeout period of the non-core business during the high-load period, the server will The business request will not be processed, so the shortening of the timeout period of the non-core business during the high-load period will cause the server to reject more service requests sent by users for the non-core business, so that during the high-load period , the server can allocate more resources to the core business to ensure the smooth operation of the core business during this time period.
然而，现有技术中通常都是线上业务的维护人员手动来对非核心业务进行降级的，这样就增加了线上业务维护人员的工作量，从而给线上业务的维护人员在进行非核心业务的降级工作时带来了极大的不便。为此，在本申请实施例中，服务器可根据业务的历史超时时间，确定出该业务在当前时段的超时时间，从而实现了该业务在各个时段的自动调整，因此，在本申请实施例中，服务器在确定该业务在当前时段的超时时间之前，可先根据针对该业务预先设置的调整超时时间的各调整周期，确定出当该业务当前调整周期到达时，该业务在各历史调整周期对应的各历史超时时间，其中，这里提到的调整周期可以服务器针对该业务预设的一天中的各个时段，该时段的划分尺度可以以小时、分钟、秒、毫秒等单位进行划分。However, in the prior art, the maintenance personnel of the online business usually downgrade the non-core business manually, which increases the workload of the maintenance personnel of the online business, thus causing problems for the maintenance personnel of the online business to perform non-core operations. It was a great inconvenience when the downgraded work of the business. Therefore, in this embodiment of the application, the server can determine the timeout time of the service in the current period according to the historical timeout time of the service, thereby realizing the automatic adjustment of the service in each period. Therefore, in the embodiment of the application , before the server determines the timeout time of the service in the current period, it can first determine, according to the adjustment periods of the timeout period preset for the service, that when the current adjustment period of the service arrives, the corresponding Each historical timeout time, wherein, the adjustment period mentioned here can be each period of the day preset by the server for the business, and the division scale of this period can be divided in units such as hours, minutes, seconds, milliseconds, etc.
当然，服务器也可根据该业务执行周期来对各调整周期进行设定，其中，这里提到的业务的执行周期是指，该业务根据服务器确定出的超时时间完成一次完整运行的时间即为该业务的执行周期，即，该业务在接收到业务请求开始后到完成该业务请求的处理所用的时间。服务器在针对该业务预先设置的调整超时时间的各调整周期时，可将各调整周期设置为该业务执行周期的正整数倍。Of course, the server can also set each adjustment period according to the service execution period, wherein the service execution period mentioned here refers to the time for the service to complete a complete operation according to the timeout determined by the server. The execution cycle of a service, that is, the time it takes for the service to complete the processing of the service request after it receives the service request. When the server adjusts each adjustment period of the timeout period preset for the service, each adjustment period may be set as a positive integer multiple of the service execution period.
S102：根据所述各历史超时时间，确定所述业务在当前调整周期对应的超时时间。S102: Determine the timeout time corresponding to the service in the current adjustment period according to the historical timeout times.
当监测到业务到达当前调整周期后确定出需要确定该业务在各历史调整周期对应的各历史超时时间时，服务器可根据当前调整周期确定出各历史时段，而后，针对每个历史时段，根据所述业务在该历史时段中的每个历史调整周期对应的历史超时时间，确定出平均超时时间，而后，根据可根据针对每个历史时段确定出的平均超时时间，确定出该业务在当前调整周期对应的超时时间。When it is detected that the business has reached the current adjustment cycle and it is determined that the historical timeout time corresponding to the business in each historical adjustment cycle needs to be determined, the server can determine each historical time period according to the current adjustment cycle, and then, for each historical time period, according to the According to the historical timeout time corresponding to each historical adjustment period of the business in the historical period, the average timeout time is determined, and then, according to the average timeout time that can be determined for each historical period, the business is determined in the current adjustment period. The corresponding timeout period.
具体的，在实际应用中，服务器出现高负载运行的情况通常都是在相同时段出现的，例如，有些服务器可能会在晚间的8点到9点出现高负载的情况，有些服务器可能会在中午的11点到12点间出现高负载的情况，因此，对于同一服务器来说，该服务器每天在高负载时段运行后得到的数据信息通常都是相关的，换句话说，服务器在对各项业务配置信息时可以使用过去在相同时段所产生的数据信息作参考的，同理，对于同一业务来说，该业务每天在相同时段所对应的各超时时间往往也是相关的，例如，对于某项业务来说，该业务所对应的服务器基本上在每天晚间的9点到11点之间将会出现高负载运行的情况，所以，对于该业务来说，不同日期晚间9点到11点之间该业务所对应的超时时间往往都是相关的，因此，为了能够使服务器根据该业务的历史超时时间而确定出的该业务当前调整周期对应的超时时间能够更加合理(即，对于处于高负载时段的核心业务来说，服务器针对该业务确定出的超时时间能够尽可能的保证该核心业务在此时段能够正常运行，而对于非核心业务来说，服务器针对该业务确定出的超时时间应尽可能的使该非核心业务拒绝更多的业务请求，从而保证服务器在高负载时段可将更多的资源分配给核心业务)，服务器可在确定该业务当前调整周期到达时，根据该当前调整周期在过去设定时间长度内的每天中，确定包含与该当前调整周期对应相同时段的时间间隔，作为每个历史时段，其中，过去设定时间长度可以是以天为单位，也可以周、月、年为单位，而对于包含与该当前调整周期对应相同时段的时间间隔来说，该时间间隔可以是仅包含与该当前调整周期对应的相同时段的时间间隔，即，该时间间隔与当前调整周期在时间长度上相同，也可以是包含有与该当前调整周期对应的相同时段的一段时间间隔。Specifically, in practical applications, the high-load operation of the server usually occurs at the same time. For example, some servers may experience high load from 8:00 to 9:00 in the evening, and some servers may experience high load at noon. There is a high load between 11 o'clock and 12 o'clock, so for the same server, the data information obtained after the server runs during the high-load period every day is usually related. When configuring information, you can use the data information generated in the same time period in the past as a reference. Similarly, for the same business, the timeout times corresponding to the same time period for the business every day are often related. For example, for a certain business Generally speaking, the server corresponding to this business will basically run under high load between 9:00 and 11:00 every night. Therefore, for this business, the server between 9:00 and 11:00 p. The timeout period corresponding to the business is often related. Therefore, in order to enable the server to determine the timeout period corresponding to the current adjustment period of the service based on the historical timeout period of the service, it can be more reasonable (that is, for the high-load period) For core business, the timeout time determined by the server for this business can ensure that the core business can run normally during this period as much as possible; for non-core business, the timeout time determined by the server for this business should be as short as possible. Make the non-core business reject more business requests, so as to ensure that the server can allocate more resources to the core business during high-load periods), the server can determine that the current adjustment period of the business arrives, according to the current adjustment period in the past In each day within the set time length, determine the time interval that includes the same time period corresponding to the current adjustment cycle as each historical time period, wherein the past set time length can be in units of days, or weeks, months, or years is the unit, and for the time interval containing the same time period corresponding to the current adjustment cycle, the time interval may only contain the same time interval corresponding to the current adjustment cycle, that is, the time interval is the same as the current adjustment cycle in The time lengths are the same, and may also be a period of time including the same time period corresponding to the current adjustment period.
例如，假设业务A所在的服务器通常在晚间的20:00～22:00之间会出现高负载的运行情况，而该业务A当前所处的调整周期为20:15～20:20，服务器为了能够自动、准确的完成该业务A在高负载时段的相应调整，可根据该业务A的当前调整周期20:15～20:20，将昨天20:15～20:20这一时段(时间间隔)确定为该业务A的历史时段，不仅如此，服务器也可将上周每天20:15～20:20这一时段分别确定为该业务A的各历史时段。除此之外，服务器也可将昨天包含有20:15～20:20这一时段的20:10～20:25时间间隔确定为该业务A的历史时段，同理，服务器也可将上周每天包含有20:15～20:20这一时段的20:10～20:25时间间隔分别确定为该业务A的各历史时段。For example, suppose that the server where service A is located usually runs under high load between 20:00 and 22:00 in the evening, and the current adjustment cycle of service A is 20:15 to 20:20. It can automatically and accurately complete the corresponding adjustment of the business A during the high-load period. According to the current adjustment cycle of the business A, 20:15-20:20, the period (time interval) of yesterday 20:15-20:20 Not only that, the server may also determine the time period of 20:15-20:20 every day last week as each historical time period of the service A. In addition, the server can also determine the time interval from 20:10 to 20:25 including the time period of 20:15 to 20:20 yesterday as the historical time period of the service A. Similarly, the server can also determine the time interval of last week The time intervals from 20:10 to 20:25 including the time period from 20:15 to 20:20 every day are respectively determined as the historical time periods of the service A.
在实际应用中，业务当前调整周期对应的超时时间除了与过去相同时段(即过去与当前调整周期相同的时段)对应的超时时间具有紧密关系外，还与当前调整周期之前的若干个调整周期对应的超时时间具有紧密关系，这是因为，通常情况下，服务器的负载并不是跳跃性增加或降低的，而是有一个增加或降低的过程，因此，对于一个业务来说，若该业务当前调整周期正处于服务器高负载运行的时间段时，该业务相对于当前调整周期的上一个调整周期也应是处于服务器的高负载运行时段的，如此一来，该业务当前调整周期对应的超时时间与该业务上一个调整周期对应的超时时间两者也应是具有紧密关系的，换句话说，这两个超时时间在一定程度上能够反映出服务器的负载的走势，所以，服务器在确定该业务当前周期所对应的超时时间时，可根据该当前调整周期，确定出该当前调整周期的前N个调整周期，作为该业务的历史时段，其中N为正整数，即，服务器可将与该当前调整周期对应的上一个调整周期对应的时段确定为该业务的历史时段，也可将相对于该当前调整周期的前两个、三个等调整周期对应的一整个时段，作为该业务的历史时段。In practical applications, the timeout time corresponding to the current adjustment period of the business is not only closely related to the timeout time corresponding to the same period in the past (that is, the same period as the current adjustment period in the past), but also corresponds to several adjustment periods before the current adjustment period There is a close relationship between the timeout period of the server, because, usually, the load of the server does not increase or decrease by jumps, but has a process of increasing or decreasing. Therefore, for a business, if the business is currently adjusted When the cycle is in the period of high-load operation of the server, the previous adjustment period of the business relative to the current adjustment period should also be in the period of high-load operation of the server. The timeout period corresponding to the last adjustment cycle of this service should also have a close relationship. In other words, these two timeout periods can reflect the load trend of the server to a certain extent. When the period corresponds to the timeout period, according to the current adjustment period, the first N adjustment periods of the current adjustment period can be determined as the historical period of the business, where N is a positive integer, that is, the server can use the current adjustment period The time period corresponding to the previous adjustment cycle corresponding to the cycle is determined as the historical time period of the service, and an entire time period corresponding to the previous two, three, etc. adjustment cycles relative to the current adjustment cycle may also be used as the historical time period of the business.
继续沿用上例，业务A当前调整周期对应的时段为20:15～20:20，因此，服务器可将业务A上一个调整周期对应的时段20:10～20:15确定为该业务A的历史时段。当然，服务器也可根据相对于当前调整周期之前的前两个调整周期对应的时段20:05～20:10、20:10～20:15，将时段20:05～20:15确定为该业务A的历史时段。Continuing with the above example, the time period corresponding to the current adjustment cycle of business A is 20:15~20:20, therefore, the server can determine the time period 20:10~20:15 corresponding to the previous adjustment cycle of business A as the history of business A time period. Of course, the server may also determine the time period 20:05-20:15 as the service according to the time periods 20:05-20:10 and 20:10-20:15 corresponding to the previous two adjustment periods before the current adjustment period. A's historical period.
需要说明的是，由于业务当前调整周期对应的超时时间通常都是与该当前调整周期临近的几个调整周期对应的超时时间具有较强的紧密型，因此，为了使服务器确定出的该业务的历史时段对应的超时时间能够与该业务当前调整周期对应的超时时间具有紧密的联系，N的取值不应过大，可控制在1～4左右。It should be noted that, since the timeout period corresponding to the current adjustment period of the service is usually relatively close to the timeout period corresponding to several adjustment periods adjacent to the current adjustment period, in order to make the service determined by the server The timeout time corresponding to the historical period can be closely related to the timeout time corresponding to the current adjustment cycle of the service, and the value of N should not be too large, and can be controlled at about 1-4.
对于在过去设定时间长度内包含与该业务当前调整周期对应相同时段的时间间隔来说，由于这个过去设定时间长度内可能包含有多个与当前调整周期对应相同时段的时间间隔，因此，在本申请实施例中，针对每个历史时段，服务器可根据该业务在该历史时段中的每个历史调整周期对应的历史超时时间，确定平均超时时间，并将该平均超时时间确定为该业务在该历史时段内的超时时间。For the time interval corresponding to the same time period corresponding to the current adjustment cycle of the service in the past set time length, since the past set time length may contain multiple time intervals corresponding to the same time period corresponding to the current adjustment cycle, therefore, In this embodiment of the application, for each historical period, the server can determine the average timeout time according to the historical timeout time corresponding to each historical adjustment cycle of the business in the historical period, and determine the average timeout time as the service The timeout period for this historical period.
例如，假设在过去的一周中，业务A每天在20:15～20:20这一调整周期所对应的超时时间如表1所示。For example, assuming that in the past week, the timeout time corresponding to the adjustment period of business A every day from 20:15 to 20:20 is shown in Table 1.
表1Table 1
表1示出了上一周业务A在20:15～20:20这一调整周期对应的各超时时间，服务器在根据表1确定业务A针对2016年5月30日～2016年6月5日这段历史时段对应的超时时间时，可将表1中的这个7个超时时间进行加和，然后再将加和结果进行平均，得到平均超时时间23s，进而将该平均超时时间23s就确定为业务A上一周在调整周期20:15～20:20对应的历史超时时间。Table 1 shows the timeout times corresponding to the adjustment cycle of business A in the previous week from 20:15 to 20:20. The server determines that business A is targeted for the period from May 30, 2016 to June 5, 2016 according to Table 1. When the timeout time corresponding to a historical period is selected, the seven timeout times in Table 1 can be summed up, and then the summed results can be averaged to obtain an average timeout time of 23s, and then the average timeout time of 23s can be determined as the business A's historical timeout time corresponding to the adjustment cycle 20:15~20:20 in the previous week.
同理，相对于该业务当前调整周期的前N个调整周期所组成的历史时段来说，服务器也可将每个历史调整周期对应的历史超时时间进行加和，并将加和结果进行平均，得到对应该历史时间间隔的超时时间。Similarly, with respect to the historical period formed by the first N adjustment periods of the current adjustment period of the business, the server can also sum up the historical timeout times corresponding to each historical adjustment period, and average the summation results, Get the timeout time corresponding to the historical time interval.
例如，假设业务A在当前调整周期20:15～20:20的前4个历史调整周期对应的超时时间如表2所示。For example, it is assumed that the timeout times corresponding to the first 4 historical adjustment periods of service A in the current adjustment period 20:15-20:20 are shown in Table 2.
表2Table 2
表2中示出了位于业务A当前调整周期20:10～20:15之前的前4个历史调整周期对应的超时时间，服务器在确定这段历史时间间隔(19:55～20:10)对应的超时时间时，可将表2中示出的4个超时时间进行加和，并将加和结果进行平均，从而将得到的平均超时时间20s作为业务A在该历史时间间隔(19:55～20:10)对应的历史超时时间。Table 2 shows the timeout period corresponding to the first 4 historical adjustment periods before the current adjustment period of service A from 20:10 to 20:15. When the timeout time is specified, the four timeout times shown in Table 2 can be summed up, and the summation results can be averaged, so that the obtained average timeout time of 20s can be used as the service A in the historical time interval (19:55～ 20:10) corresponds to the historical timeout time.
除此之外，服务器在确定该业务在历史时段对应的历史超时时间时，也可将该历史时段中包含的每个历史调整周期对应的各历史超时时间进行排序，并将排序结果中处于预设位置的历史超时时间作为该业务在该历史时间间隔对应的历史超时时间。In addition, when the server determines the historical timeout time corresponding to the business in the historical time period, it can also sort the historical timeout times corresponding to each historical adjustment cycle contained in the historical time period, and sort the results in the predetermined The historical timeout time of the location is set as the historical timeout time corresponding to the service in the historical time interval.
例如，对于表2中所示的业务A在当前调整周期20:15～20:20的前4个历史调整周期对应的超时时间来说，服务器可将这4个超时时间进行排序，得到超时时间的排序结果为“19s、19s、20s、22s”，而后，服务器可将该排序结果中处于第三位置的20s作为业务A在历史时段(19:55～20:10)对应的历史超时时间。For example, for the timeout period corresponding to the first 4 historical adjustment periods of service A in the current adjustment period 20:15-20:20 shown in Table 2, the server can sort these 4 timeout periods to obtain the timeout period The sorting result is "19s, 19s, 20s, 22s", and then, the server can use the 20s in the third position in the sorting result as the historical timeout time corresponding to service A in the historical period (19:55-20:10).
需要说明的是，服务器在确定包含有与该业务当前调整周期相同时段的过去设定时间长度的历史时段来说，也可将该历史时段中包含的各历史调整周期对应的各超时时间进行排序，并将排序结果中处于预设位置的历史超时时间作为该业务在该历史时段对应的历史超时时间。具体过程与上述说明的确定方式相同，在此就不进行详细赘述了。It should be noted that, when the server determines the historical time period that contains the same time period as the current business adjustment period, it can also sort the timeout times corresponding to the historical adjustment periods included in the historical time period , and use the historical timeout time at the preset position in the sorting result as the historical timeout time corresponding to the business in the historical time period. The specific process is the same as the determination method described above, and will not be described in detail here.
服务器为了使确定出的业务当前调整周期对应的超时时间能够尽可能的满足该业务所处服务器在当前调整周期对应的时间段的需要，服务器在确定出该业务的各历史超时时间后，可根据预先设置的各历史超时时间分别对应的权重以及各历史超时时间，得到加权和值，并将该加权和值确定为该业务在当前调整周期对应的超时时间。In order for the server to make the determined timeout time corresponding to the current adjustment cycle of the business meet the needs of the server where the business is located in the time period corresponding to the current adjustment cycle as much as possible, after determining the historical timeout time of the business, the server can according to The preset weights corresponding to each historical timeout time and each historical timeout time are used to obtain a weighted sum value, and the weighted sum value is determined as the timeout time corresponding to the service in the current adjustment period.
例如，假设服务器确定出对于业务A当前调整周期的3个历史超时时间分别为20s、24s、23s，其中，20s的超时时间为业务A当前调整周期之前的前4个历史调整周期所对应的平均超时时间，24s的超时时间为业务A在昨天同一时段(即昨天与当前调整周期相同的时段)对应的历史超时时间，23s的超时时间为业务A在过去一周的同一时段(即过去一周内每天与当前调整周期相同的时段)内对应的平均历史超时时间，而后，服务器可将各历史超时时间与各历史超时时间对应的各预设权重进行相乘并相加，即：For example, suppose the server determines that the three historical timeout periods for the current adjustment period of service A are 20s, 24s, and 23s respectively, where the timeout period of 20s is the average value corresponding to the previous four historical adjustment periods before the current adjustment period of service A Timeout time, the timeout time of 24s is the historical timeout time corresponding to the same time period of business A yesterday (that is, the same time period as yesterday and the current adjustment period), and the timeout time of 23s is the timeout time of business A in the same time period in the past week (that is, every day in the past week The corresponding average historical timeout time in the same period as the current adjustment period), and then, the server can multiply and add each historical timeout time and each preset weight corresponding to each historical timeout time, that is:
20×30％+24×40％+23×30％＝22.5，并将加权和值22.5作为业务A当前调整周期对应的超时时间。20×30%+24×40%+23×30%=22.5, and the weighted sum value 22.5 is used as the timeout period corresponding to the current adjustment period of service A.
需要说明的是，各历史超时时间对应的预设权重可以是固定的，也可是不固定的，其中，对于不固定的情况来说，服务器可针对不同的时段分别设置对应各历史超时时间的预设权重，例如，对于时段T1来说，服务器可针对昨天的历史超时时间设置预设权重a1，可针对上周的历史超时时间设置预设权重a2，而对于时段T2来说，服务器可针对昨天的历史超时时间设置预设权重b1，可针对上周的历史超时时间设置预设权重b2。It should be noted that the preset weights corresponding to each historical timeout time may be fixed or not fixed. Wherein, in the case of not being fixed, the server may respectively set the preset weights corresponding to each historical timeout time for different time periods. Set weights, for example, for time period T1, the server can set a preset weight a1 for yesterday’s historical timeout time, and a preset weight a2 for last week’s historical timeout time, and for time period T2, the server can set a preset weight for yesterday’s timeout time The preset weight b1 can be set for the historical timeout time of last week, and the preset weight b2 can be set for the historical timeout time of last week.
S103：根据所述业务在当前调整周期对应的超时时间，执行所述业务。S103: Execute the service according to the timeout period corresponding to the service in the current adjustment period.
当服务器确定出该业务在当前调整周期对应的超时时间后，可根据该超时时间执行该业务，其中，由于在实际应用中，业务通常都可分为核心业务以及非核心业务，对于核心业务来说，当服务器出现高负载运行的情况时，为了保证核心业务在高负载期间也能够顺利的运行，核心业务在高负载期间所对应的超时时间应尽可能的大一些，这样，超时时间越长，该核心业务处理用户发送的业务请求所用耗时也将会尽可能的小于该核心业务在高负载期间所对应的超时时间，从而可使该核心业务能够在高负载期间尽可能的对用户发送的业务请求进行处理，相应的，该核心业务在这段时间内的超时率也将越小。After the server determines the timeout period corresponding to the service in the current adjustment period, it can execute the service according to the timeout period. In practical applications, services can usually be divided into core services and non-core services. For core services, That is to say, when the server is running under high load, in order to ensure that the core business can run smoothly during the high load period, the timeout period corresponding to the core business during the high load period should be as large as possible, so that the longer the timeout period , the time taken by the core business to process the service requests sent by users will also be as small as possible less than the timeout period corresponding to the core business during high load periods, so that the core business can send as much as possible to users during high load periods Correspondingly, the timeout rate of the core business during this period will be smaller.
然而，通常情况下，该核心业务在高负载期间所对应的超时时间不能无限制的增大，因为在实际应用中，该核心业务的超时时间在到达一定数值时，已经能够尽可能的保证该核心业务在高负载期间的正常运行，若超时时间进一步的增大，将会占用服务器的额外资源，从而造成了服务器的资源浪费，不仅如此，核心业务的超时时间到达一定数值后，若该核心业务在高负载期间内一直都是以这一数值对应的超时时间运行，则服务器除了可保证该核心业务在高负载期间的顺利运行外，还可将一些闲置的资源分配给非核心业务，从而使非核心业务在不影响核心业务顺利运行的前提下，也能在高负载期间得到运行。因此，在本申请实施例中，服务器可针对各核心业务，分别设置对应各调整周期的第一超时阈值，该第一超时阈值可通过服务器执行该核心业务后保存的历史数据经过统计、分析得出。而服务器针对核心业务确定出的该核心业务在当前调整周期对应的超时时间大于针对该核心业务在当前调整周期预设的第一超时阈值时，则可将该第一超时阈值重新作为该核心业务在当前调整周期对应的超时时间，并根据重新确定的超时时间执行该核心业务。由于服务器可将大于第一超时阈值的超时时间替换为该第一超时阈值，因此，服务器在保证了核心业务顺利运行的前提下，还降低了服务器资源的浪费。However, under normal circumstances, the timeout period corresponding to the core business cannot be increased without limit during the high load period, because in practical applications, when the timeout time of the core business reaches a certain value, the timeout period of the core business can be guaranteed as much as possible. The normal operation of the core business during the high-load period, if the timeout time is further increased, it will occupy additional resources of the server, resulting in a waste of server resources. Not only that, after the timeout time of the core business reaches a certain value, if the core The business has always been running with the timeout time corresponding to this value during the high load period. In addition to ensuring the smooth operation of the core business during the high load period, the server can also allocate some idle resources to non-core business. So that non-core business can also be run during high-load periods without affecting the smooth operation of core business. Therefore, in this embodiment of the application, the server can set the first timeout threshold corresponding to each adjustment cycle for each core business, and the first timeout threshold can be obtained through statistics and analysis of the historical data saved after the server executes the core business. out. And when the timeout time corresponding to the core business in the current adjustment cycle determined by the server for the core business is greater than the first time-out threshold preset for the core business in the current adjustment cycle, the first time-out threshold can be re-used as the core business The timeout period corresponding to the current adjustment period is currently adjusted, and the core business is executed according to the re-determined timeout period. Since the server can replace the timeout time greater than the first timeout threshold with the first timeout threshold, the server also reduces the waste of server resources on the premise of ensuring the smooth operation of the core business.
而对于非核心业务来说，当服务器处在高负载运行的这段时间时，为了保证核心业务的顺利运行，通常需要将非核心业务在这段时间内的超时时间进行降低，使得非核心业务的超时时间尽可能的小，这样，超时时间越小，该非核心业务处理用户发送的业务请求所用的耗时也将尽可能的大于该非核心业务在高负载期间所对应的超时时间，从而使得该非核心业务在高负载期间能够将尽可能多的服务器资源让给核心业务，而该非核心业务在这段时间内的超时率也将越大。For non-core business, when the server is running under high load, in order to ensure the smooth operation of the core business, it is usually necessary to reduce the timeout period of the non-core business during this period, so that the non-core business The timeout period of the service should be as small as possible. In this way, the smaller the timeout period, the time spent by the non-core business processing the service request sent by the user will also be longer than the corresponding timeout period of the non-core business during the high load period, thus This enables the non-core business to give as much server resources as possible to the core business during the period of high load, and the timeout rate of the non-core business during this period will also be greater.
在实际应用中，服务器确定出的非核心业务的超时时间应与服务器的负载情况相对应，即，当服务器的负载逐步增加时，非核心业务的超时时间应逐步减小，而当服务器的负载逐步降低时，非核心业务的超时时间应逐步增大，然而在服务器实际运行的过程中，确定出的非核心业务的超时时间相对于正常情况下可能已经是一个较小的超时时间了，但是，非核心业务根据这一超时时间进行执行时，可能还会对核心业务的顺利运行造成影响，如，和核心业务争抢服务器的资源等，从而使得当服务器处于高负载运行期间，核心业务无法顺利执行。In practical applications, the timeout period of non-core business determined by the server should correspond to the load of the server, that is, when the load of the server gradually increases, the timeout time of non-core business should gradually decrease, and when the load of the server When gradually decreasing, the timeout period of the non-core business should gradually increase. However, during the actual operation of the server, the determined timeout period of the non-core business may already be a relatively small timeout period compared with the normal situation, but , when the non-core business is executed according to this timeout period, it may also affect the smooth operation of the core business, such as competing with the core business for server resources, etc., so that when the server is under high load operation, the core business cannot Executed smoothly.
为了避免上述情况的发生，在本申请实施例中，服务器可针对非核心业务也设置一个第二超时阈值，该第二超时阈值也可通过服务器以往执行该非核心业务后保存的历史数据而得出，该第二超时阈值可保证当服务器处于高负载时段时，非核心业务基于该第二超时阈值的运行不会影响到核心业务在此时段(高负载时段)的正常运行。而服务器在设置该第二超时阈值时，可针对不同的调整周期，分别设置对应各调整周期的各第二超时阈值。这样一来，当服务器确定非核心业务在当前调整周期对应的超时时间大于针对该核心业务在当前调整周期预设的第二超时阈值时，则可将该第二超时阈值重新作为该非核心业务在当前调整周期对应的超时时间，并根据重新确定的超时时间执行该非核心业务。当然，当服务器确定非核心业务在当前调整周期对应的超时时间大于针对该非核心业务在当前调整周期预设的第二超时阈值时，可停止执行该非核心业务，这样，非核心业务将不会在此期间(服务器处于高负载的期间)与核心业务争抢服务器的资源，从而实现了非核心业务的自动降级，保证了核心业务服务器处于高负载期间的顺利运行。In order to avoid the occurrence of the above situation, in the embodiment of the present application, the server can also set a second timeout threshold for non-core business, and the second timeout threshold can also be obtained from the historical data saved by the server after executing the non-core business in the past It can be seen that the second timeout threshold can ensure that when the server is in a high load period, the operation of the non-core business based on the second timeout threshold will not affect the normal operation of the core business during this period (high load period). When setting the second timeout threshold, the server may respectively set the second timeout thresholds corresponding to the adjustment periods for different adjustment periods. In this way, when the server determines that the timeout period corresponding to the non-core business in the current adjustment period is greater than the second timeout threshold preset for the core business in the current adjustment period, the second timeout threshold can be re-used as the non-core business The timeout time corresponding to the current adjustment period is currently adjusted, and the non-core business is executed according to the re-determined timeout time. Of course, when the server determines that the timeout period corresponding to the non-core business in the current adjustment cycle is greater than the second time-out threshold preset for the non-core business in the current adjustment cycle, it can stop executing the non-core business. In this way, the non-core business will not During this period (when the server is under high load), it will compete with the core business for server resources, thereby realizing the automatic downgrade of non-core business and ensuring the smooth operation of the core business server during high load.
需要说明的是，上述说明的核心业务与非核心业务分别对应的第一超时阈值和第二超时阈值应是不同的超时阈值，其中，通常情况下，核心业务的第一超时阈值应远大于非核心业务的第二超时阈值，例如，对于核心业务来说，其第一超时阈值可以为40s，而非核心业务对应的第二超时阈值可以为3ms。It should be noted that the first timeout threshold and the second timeout threshold respectively corresponding to the core business and the non-core business explained above should be different timeout thresholds, wherein, usually, the first timeout threshold of the core business should be much larger than the non-core business. The second timeout threshold of the core service, for example, for the core service, the first timeout threshold may be 40s, and the second timeout threshold corresponding to the non-core service may be 3ms.
还需说明的是，服务器在针对非核心业务设置第二超时阈值时，也可根据核心业务在同一调整周期的超时阈值来进行设置，例如，当核心业务在t1调整周期对应的第一超时阈值为40s时，服务器可将非核心业务在此调整周期对应的第二超时阈值设置为1s，而当核心业务在t1调整周期对应的第一超时阈值为30s时，则服务器可将非核心业务在此调整周期对应的第二超时阈值设置为3s，即，为了尽可能的避免在高负载期间与核心业务争抢服务器的资源，非核心业务的第二超时阈值可与核心业务的第一超时阈值成反比。It should also be noted that when the server sets the second timeout threshold for non-core business, it can also be set according to the timeout threshold of the core business in the same adjustment period, for example, when the core business is in the t1 adjustment period corresponding to the first timeout threshold When t1 is 40s, the server can set the second timeout threshold corresponding to the adjustment period of non-core business to 1s, and when the first timeout threshold corresponding to the adjustment period of core business at t1 is 30s, the server can set the non-core business in The second timeout threshold corresponding to this adjustment period is set to 3s, that is, in order to avoid competing with the core business for server resources during high load periods as much as possible, the second timeout threshold of the non-core business can be compared with the first timeout threshold of the core business Inversely proportional.
另外，在本申请实施例中，服务器可根据针对上述业务预设的各监控周期，监控该业务在每个监控周期内的超时率，此举的目的在于，在实际应用中，超时率的大小能够反映出该业务在一段时间内超时时间的大小，以及该业务所处的服务器在此期间的负载情况，例如，当该业务在一段超时时间内运行后得到的超时率较大时，则可在一定程度上表明该业务在此期间运行所基于的超时时间是一个较小的超时时间，继而可在一定程度上表明该服务器在此期间负载较大。In addition, in this embodiment of the application, the server can monitor the timeout rate of the service in each monitoring period according to the preset monitoring periods for the above services. The purpose of this is that in practical applications, the size of the timeout rate It can reflect the size of the timeout time of the business within a certain period of time, and the load of the server where the business is located during this period. To a certain extent, it indicates that the timeout period based on which the business operates during this period is a relatively small timeout period, which in turn indicates to a certain extent that the server is heavily loaded during this period.
而服务器在预设的各监控周期，监控该业务在每个监控周期内的超时率发现，连续若干个监控周期内的超时率均不是线上业务维护人员所期望达到的超时率，换句话说，该业务在这些监控周期内的运行情况可能均没有到达线上业务维护人员所期望的运行状态，因此，为了能够使该业务能够尽快的达到线上业务维护人员所期望的运行状态，线上业务维护人员可通过服务器针对该业务的各个调整周期，分别预设对应各调整周期的超时率阈值，这样一来，当服务器发现该业务在连续M个监控周期内的超时率均没有到达预设的超时率阈值时，服务器可将针对该业务预设的超时阈值确定为该业务在下一个调整周期对应的超时时间，其中，对于业务类型为核心业务类型的核心业务来说，当服务器监控到该核心业务在连续M个监控周期内的超时率均大于预设的第一超时率阈值时，则可将针对该核心业务预设的第一超时阈值确定为该核心业务在下一个调整周期对应的超时时间，而对于非核心业务来说，当服务器监控到该非核心业务在连续M个监控周期内的超时率均小于预设的第二超时率阈值时，则可将针对该非核心业务预设的第二超时阈值确定为该非核心业务在下一个调整周期对应的超时时间。However, the server monitors the timeout rate of the business in each monitoring period in each preset monitoring period, and finds that the timeout rate in several consecutive monitoring periods is not the timeout rate expected by the online service maintenance personnel. In other words , the running status of the business during these monitoring periods may not have reached the expected running status of the online business maintenance personnel. Service maintenance personnel can use the server to preset the timeout rate thresholds corresponding to each adjustment cycle for each adjustment cycle of the business. In this way, when the server finds that the time-out rate of the business has not reached the preset value in M consecutive monitoring cycles When the timeout rate threshold is set, the server may determine the preset timeout threshold for the service as the timeout period corresponding to the service in the next adjustment period, wherein, for a core service whose service type is a core service type, when the server monitors that the When the timeout rate of the core business in consecutive M monitoring periods is greater than the preset first timeout rate threshold, then the first timeout threshold preset for the core business can be determined as the corresponding timeout of the core business in the next adjustment period time, and for non-core business, when the server monitors that the time-out rate of the non-core business in consecutive M monitoring periods is less than the preset second time-out rate threshold, the non-core business preset The second timeout threshold is determined as the timeout period corresponding to the non-core business in the next adjustment period.
需要说明的是，上述说明的监控周期可以与业务的调整周期相同，也可包含在该业务的调整周期之中，例如，假设业务A的一个调整周期为20:35～20:40，则服务器在设置监控周期时，可将该业务A的调整周期20:35～20:40以一分钟为单位进行五等分，继而得到20:35～20:36、20:36～20:37、20:37～20:38、20:38～20:39、20:39～20:40五个监控周期。It should be noted that the monitoring period described above can be the same as the adjustment period of the service, or included in the adjustment period of the service. For example, assuming that an adjustment period of service A is 20:35-20:40, the server When setting the monitoring cycle, you can divide the adjustment cycle of service A from 20:35 to 20:40 into five equal parts in one minute, and then get 20:35 to 20:36, 20:36 to 20:37, and 20 :37～20:38, 20:38～20:39, 20:39～20:40 five monitoring cycles.
从上述方法中可以看出，由于服务器可根据该业务的历史超时时间，确定出该业务在当前调整周期对应的超时时间，因此，当服务器出现高负载运行的状况时，服务器可根据以往在这一时段出现高负载时该业务所对应的历史超时时间，确定出该业务在当前高负载时段所对应的超时时间，进而完成了该业务在当前高负载时段的自动调整，相对于现有技术而言，服务器在对业务进行降级时无需线上业务的维护人员亲自手段来修改该业务的超时时间，从而极大的提高了线上业务的维护人员在对业务进行降级过程中的便利性。It can be seen from the above method that since the server can determine the timeout period corresponding to the service in the current adjustment cycle based on the historical timeout period of the service, when the server is running under high load, the server can The historical timeout time corresponding to the business when a period of high load occurs, determine the timeout time corresponding to the business in the current high load period, and then complete the automatic adjustment of the business in the current high load period, compared with the existing technology In other words, when the server downgrades the service, the maintenance personnel of the online service do not need to personally modify the timeout period of the service, thereby greatly improving the convenience of the maintenance personnel of the online service in the process of downgrading the service.
在本申请实施例还提供了一种业务执行的系统，如图2所示。The embodiment of the present application also provides a service execution system, as shown in FIG. 2 .
图2为本申请实施例提供的一种业务执行的系统示意图。FIG. 2 is a schematic diagram of a service execution system provided by an embodiment of the present application.
在图2中，该系统中的业务执行模块在确定上述业务到达当前调整周期时，可通知业务日志确定模块确定该业务的历史超时时间所对应的日志信息，业务日志确定模块在接收到业务执行模块发送的指示后，可从预先保存的各日志信息中确定出与该业务当前调整周期相关的历史日志信息，并将确定出的各历史日志信息发送至实时传输消息队列中，而后，历史超时时间计算模块可从实时传输消息队列中读取这些历史日志信息，并根据这些历史日志信息确定出该业务的各历史超时时间，并将确定出的各历史超时时间发送给Zookeeper中，其中，这里提到的Zookeeper是一个分布式的、开放源码的分布式应用程序协调服务，该Zookeeper可以相当于能够实现数据存储、数据处理的一个服务器或系统。Zookeeper在接收到各历史超时时间后，可将各历史超时时间同步传输到Zookeeper agent(相当于Zookeeper中的内存)中，系统中的业务当前超时时间确定模块可从Zookeeper agent中读取中各历史超时时间，并根据从规则、参数配置模块中获取到的计算规则(即各历史超时时间的预设权重)，确定出该业务当前调整周期对应的超时时间，并将该超时时间发送给业务降级模块，业务降级模块在接收到该超时时间后，可根据从规则、参数配置模块获取到的该业务在当前调整周期对应的超时阈值，判断是否将该超时时间替换为该超时阈值，并当完成判别后，将最终确定的超时时间发送给业务执行模块，使业务执行模块根据该超时时间来执行。In Fig. 2, when the business execution module in the system determines that the above-mentioned business has reached the current adjustment cycle, it can notify the business log determination module to determine the log information corresponding to the historical timeout time of the business, and the business log determination module receives the business execution After the instruction sent by the module, the historical log information related to the current adjustment cycle of the business can be determined from the pre-saved log information, and the determined historical log information can be sent to the real-time transmission message queue, and then the history timeout The time calculation module can read these historical log information from the real-time transmission message queue, and determine each historical timeout time of the business according to these historical log information, and send each historical timeout time determined to Zookeeper, wherein, here The mentioned Zookeeper is a distributed, open-source distributed application coordination service, and the Zookeeper can be equivalent to a server or system capable of data storage and data processing. After Zookeeper receives each historical timeout time, it can synchronously transmit each historical timeout time to the Zookeeper agent (equivalent to the memory in Zookeeper), and the business current timeout time determination module in the system can read each historical timeout time from the Zookeeper agent. timeout time, and according to the calculation rules (that is, the preset weights of each historical timeout time) obtained from the rules and parameter configuration modules, determine the timeout time corresponding to the current adjustment cycle of the business, and send the timeout time to the business downgrade module, after receiving the timeout period, the business downgrading module can judge whether to replace the timeout period with the timeout threshold value according to the timeout threshold value corresponding to the service in the current adjustment cycle obtained from the rule and parameter configuration module, and when completed After the judgment, the final timeout time is sent to the service execution module, so that the service execution module executes according to the timeout time.
以上为本申请实施例提供的业务执行的方法，基于同样的思路，本申请实施例还提供了业务执行的装置，如图3所示。The above is the service execution method provided by the embodiment of the present application. Based on the same idea, the embodiment of the present application also provides a service execution device, as shown in FIG. 3 .
图3为本申请实施例提供的一种业务执行的装置示意图，具体包括：Fig. 3 is a schematic diagram of a service execution device provided in the embodiment of the present application, specifically including:
第一确定模块301，用于根据针对业务预设的用于调整超时时间的各个调整周期，在当前调整周期到来时，确定所述业务在各历史调整周期对应的各历史超时时间；The first determination module 301 is configured to determine each historical timeout time corresponding to each historical adjustment period of the business when the current adjustment period arrives according to each adjustment period preset for the service for adjusting the timeout period;
第二确定模块302，用于根据所述各历史超时时间，确定所述业务在当前调整周期对应的超时时间；The second determination module 302 is configured to determine the timeout time corresponding to the service in the current adjustment period according to the historical timeout time;
执行模块303，用于根据所述业务在当前调整周期对应的超时时间，执行所述业务。The execution module 303 is configured to execute the service according to the timeout period corresponding to the service in the current adjustment period.
所述第二确定模块302具体用于，根据所述当前调整周期确定各历史时段；针对每个历史时段，根据所述业务在该历史时段中的每个历史调整周期对应的历史超时时间，确定平均超时时间；根据针对每个历史时间间隔确定的平均超时时间，确定所述业务在当前调整周期对应的超时时间。The second determining module 302 is specifically configured to determine each historical period according to the current adjustment period; for each historical period, according to the historical timeout time corresponding to each historical adjustment period of the business in the historical period, determine Average timeout time: according to the average timeout time determined for each historical time interval, determine the timeout time corresponding to the service in the current adjustment period.
针对业务预设的用于调整超时时间的各个调整周期包括：针对所述业务预设的一天中的各个时段；Each adjustment period preset for the business for adjusting the timeout period includes: each time period of the day preset for the business;
所述第二确定模块302具体用于，根据当前调整周期，在过去设定时间长度内的每天中，确定包含与所述当前调整周期对应相同时段的时间间隔，作为每个历史时段；和/或The second determining module 302 is specifically configured to, according to the current adjustment period, determine a time interval including the same time period corresponding to the current adjustment period as each historical period in each day within the past set time length; and/or or
根据当前调整周期，确定所述当前调整周期的前N个调整周期，作为历史时段，其中N为正整数。According to the current adjustment period, N adjustment periods before the current adjustment period are determined as historical periods, where N is a positive integer.
所述第二确定模块302具体用于，根据各历史超时时间以及各历史超时时间分别对应的权重，得到加权和值，并将所述加权和值确定为所述业务在当前调整周期对应的超时时间。The second determination module 302 is specifically configured to obtain a weighted sum value according to each historical timeout time and the weight corresponding to each historical timeout time, and determine the weighted sum value as the timeout value corresponding to the service in the current adjustment period time.
所述执行模块303具体用于，当所述业务的业务类型为核心业务类型时，若确定出的所述业务在当前调整周期对应的超时时间大于针对所述业务在当前调整周期预设的第一超时阈值，则将所述第一超时阈值重新作为所述业务在当前调整周期对应的超时时间，并根据重新确定的超时时间执行所述业务；当所述业务的业务类型为非核心业务类型时，若确定出的所述业务在当前调整周期对应的超时时间大于针对所述业务在当前调整周期预设的第二超时阈值，则将所述第二超时阈值重新作为所述业务在当前调整周期对应的超时时间，并根据重新确定的超时时间执行所述业务，或，停止执行所述业务；其中，所述第一超时阈值大于所述第二超时阈值。The execution module 303 is specifically configured to, when the service type of the service is a core service type, if the determined timeout period corresponding to the service in the current adjustment period is greater than the preset first timeout period for the service in the current adjustment period a timeout threshold, then re-use the first timeout threshold as the timeout period corresponding to the service in the current adjustment period, and execute the service according to the re-determined timeout period; when the service type of the service is a non-core service type , if the determined timeout time corresponding to the service in the current adjustment period is greater than the second timeout threshold preset for the service in the current adjustment period, the second timeout threshold will be re-used as the service in the current adjustment period period corresponding to the timeout period, and execute the service according to the re-determined timeout period, or stop executing the service; wherein, the first timeout threshold is greater than the second timeout threshold.
所述装置还包括：The device also includes:
监控模块304，用于根据针对所述业务预设的各监控周期，监控所述业务在每个监控周期内的超时率；当监控到所述业务的业务类型为核心业务类型，且连续M个监控周期内的超时率均大于预设第一超时率阈值时，则指示所述第二确定模块302将所述第一超时阈值确定为所述业务在下一个调整周期对应的超时时间；当监控到所述业务的业务类型为非核心业务类型，且连续M个监控周期内的超时率均小于预设第二超时率阈值时，则指示所述第二确定模块302将所述第二超时阈值确定为所述业务在下一个调整周期对应的超时时间；其中，M为正整数。The monitoring module 304 is configured to monitor the timeout rate of the service in each monitoring period according to the monitoring periods preset for the service; when the monitored service type is a core service type, and there are M consecutive When the timeout rates in the monitoring period are all greater than the preset first timeout rate threshold, instruct the second determination module 302 to determine the first timeout threshold as the timeout time corresponding to the service in the next adjustment period; When the business type of the business is a non-core business type, and the time-out rates in consecutive M monitoring periods are all less than the preset second time-out rate threshold, instruct the second determination module 302 to determine the second time-out threshold is the timeout period corresponding to the service in the next adjustment period; wherein, M is a positive integer.
本申请实施例提供了一种业务执行的方法及装置，该方法中服务器可根据针对业务预设的调整超时时间的各调整周期，确定当前周期到来时，确定出该业务在各历史调整周期对应的各历史超时时间，而后，服务器可根据确定出的各历史超时时间，确定出该业务在当前调整周期对应的超时时间，继而根据确定出的当前调整周期对应的超时时间，对该业务进行执行。从上述方法中可以看出，由于服务器可根据该业务的历史超时时间，确定出该业务在当前调整周期对应的超时时间，因此，当服务器出现高负载运行的状况时，服务器可根据以往在这一时段出现高负载时该业务所对应的历史超时时间，确定出该业务在当前高负载时段所对应的超时时间，进而完成了该业务在当前高负载时段的自动调整，相对于现有技术而言，服务器在对业务进行降级时无需线上业务的维护人员亲自手段来修改该业务的超时时间，从而极大的提高了线上业务的维护人员在对业务进行降级过程中的便利性。The embodiment of the present application provides a method and device for service execution. In this method, the server can determine the arrival of the current period according to each adjustment period of the preset adjustment timeout period for the service, and determine that the service corresponds to each historical adjustment period. Each historical timeout time, then, the server can determine the timeout time corresponding to the current adjustment period of the business according to each determined historical timeout time, and then execute the business according to the determined timeout time corresponding to the current adjustment period . It can be seen from the above method that since the server can determine the timeout period corresponding to the service in the current adjustment cycle based on the historical timeout period of the service, when the server is running under high load, the server can The historical timeout time corresponding to the business when a period of high load occurs, determine the timeout time corresponding to the business in the current high load period, and then complete the automatic adjustment of the business in the current high load period, compared with the existing technology In other words, when the server downgrades the service, the maintenance personnel of the online service do not need to personally modify the timeout period of the service, thereby greatly improving the convenience of the maintenance personnel of the online service in the process of downgrading the service.
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow diagram procedure or procedures and/or block diagram procedures or blocks.
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。Memory may include non-permanent storage in computer readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read only memory (ROM) or flash RAM. Memory is an example of computer readable media.
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems or computer program products. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。The above descriptions are only examples of the present application, and are not intended to limit the present application. For those skilled in the art, various modifications and changes may occur in this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610466985.6ACN105939225B (en) | 2016-06-23 | 2016-06-23 | A kind of method and device that business executes |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610466985.6ACN105939225B (en) | 2016-06-23 | 2016-06-23 | A kind of method and device that business executes |
| Publication Number | Publication Date |
|---|---|
| CN105939225Atrue CN105939225A (en) | 2016-09-14 |
| CN105939225B CN105939225B (en) | 2019-04-02 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610466985.6AActiveCN105939225B (en) | 2016-06-23 | 2016-06-23 | A kind of method and device that business executes |
| Country | Link |
|---|---|
| CN (1) | CN105939225B (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106686627A (en)* | 2016-12-07 | 2017-05-17 | 广东欧珀移动通信有限公司 | Method and device for opening WiFi/hot spot |
| CN107040566A (en)* | 2016-09-19 | 2017-08-11 | 阿里巴巴集团控股有限公司 | Method for processing business and device |
| CN107426328A (en)* | 2017-08-08 | 2017-12-01 | 百度在线网络技术（北京）有限公司 | Information-pushing method and device |
| CN109088828A (en)* | 2018-08-03 | 2018-12-25 | 网宿科技股份有限公司 | server overload control method and system |
| CN109388552A (en)* | 2017-08-07 | 2019-02-26 | 中兴通讯股份有限公司 | Start the determination method, apparatus and storage medium of the duration of application program |
| CN109491769A (en)* | 2017-09-11 | 2019-03-19 | 华为技术有限公司 | A kind of business reorganization method, apparatus and chip |
| CN109543988A (en)* | 2018-11-16 | 2019-03-29 | 中国银行股份有限公司 | The method, apparatus and storage medium of optimization transaction overtime threshold |
| CN110012093A (en)* | 2019-04-02 | 2019-07-12 | 北京奇艺世纪科技有限公司 | A kind of method and device of adjustment connection time-out time |
| CN110166572A (en)* | 2019-06-06 | 2019-08-23 | 北京达佳互联信息技术有限公司 | Network processing method, device, electronic equipment and storage medium |
| CN111598487A (en)* | 2020-06-22 | 2020-08-28 | 拉扎斯网络科技（上海）有限公司 | Data processing and model training method, apparatus, electronic device and storage medium |
| CN112118329A (en)* | 2020-08-31 | 2020-12-22 | 北京奇艺世纪科技有限公司 | Network request processing method and device, electronic equipment and storage medium |
| CN112330151A (en)* | 2020-11-05 | 2021-02-05 | 河北中废通网络技术有限公司 | Service processing method, terminal device and storage medium |
| CN112637362A (en)* | 2020-12-30 | 2021-04-09 | 北京奇艺世纪科技有限公司 | Request result determining method, device and system, electronic equipment and storage medium |
| CN113411829A (en)* | 2020-03-17 | 2021-09-17 | 中国联合网络通信集团有限公司 | Carrier configuration method, device, apparatus and storage medium |
| CN113873026A (en)* | 2021-09-24 | 2021-12-31 | 深圳市元征科技股份有限公司 | Dynamic timeout response method, device, terminal equipment and storage medium |
| CN115225503A (en)* | 2022-05-16 | 2022-10-21 | 北京邮电大学 | OpenFlow flow table item dynamic timeout allocation method and related equipment |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070294124A1 (en)* | 2006-06-14 | 2007-12-20 | John Charles Crotts | Hospitality performance index |
| CN102638457A (en)* | 2012-03-23 | 2012-08-15 | 苏州阔地网络科技有限公司 | Method and system for automatically allocating server resource |
| CN102741768A (en)* | 2010-02-09 | 2012-10-17 | 罗伯特·博世有限公司 | Method for predicting the duration of a future time interval |
| CN103646670A (en)* | 2013-12-05 | 2014-03-19 | 华为技术有限公司 | Method and device for evaluating performances of storage system |
| CN104217091A (en)* | 2013-06-05 | 2014-12-17 | 北京齐尔布莱特科技有限公司 | Website page view prediction method based on historical tendency weights |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070294124A1 (en)* | 2006-06-14 | 2007-12-20 | John Charles Crotts | Hospitality performance index |
| CN102741768A (en)* | 2010-02-09 | 2012-10-17 | 罗伯特·博世有限公司 | Method for predicting the duration of a future time interval |
| CN102638457A (en)* | 2012-03-23 | 2012-08-15 | 苏州阔地网络科技有限公司 | Method and system for automatically allocating server resource |
| CN104217091A (en)* | 2013-06-05 | 2014-12-17 | 北京齐尔布莱特科技有限公司 | Website page view prediction method based on historical tendency weights |
| CN103646670A (en)* | 2013-12-05 | 2014-03-19 | 华为技术有限公司 | Method and device for evaluating performances of storage system |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107040566A (en)* | 2016-09-19 | 2017-08-11 | 阿里巴巴集团控股有限公司 | Method for processing business and device |
| CN107040566B (en)* | 2016-09-19 | 2020-01-31 | 阿里巴巴集团控股有限公司 | Service processing method and device |
| CN106686627A (en)* | 2016-12-07 | 2017-05-17 | 广东欧珀移动通信有限公司 | Method and device for opening WiFi/hot spot |
| CN109388552A (en)* | 2017-08-07 | 2019-02-26 | 中兴通讯股份有限公司 | Start the determination method, apparatus and storage medium of the duration of application program |
| CN109388552B (en)* | 2017-08-07 | 2024-03-26 | 中兴通讯股份有限公司 | Method, device and storage medium for determining duration of application startup |
| CN107426328A (en)* | 2017-08-08 | 2017-12-01 | 百度在线网络技术（北京）有限公司 | Information-pushing method and device |
| CN109491769A (en)* | 2017-09-11 | 2019-03-19 | 华为技术有限公司 | A kind of business reorganization method, apparatus and chip |
| CN109088828A (en)* | 2018-08-03 | 2018-12-25 | 网宿科技股份有限公司 | server overload control method and system |
| CN109088828B (en)* | 2018-08-03 | 2022-07-26 | 网宿科技股份有限公司 | Server overload control method and system |
| CN109543988A (en)* | 2018-11-16 | 2019-03-29 | 中国银行股份有限公司 | The method, apparatus and storage medium of optimization transaction overtime threshold |
| CN110012093B (en)* | 2019-04-02 | 2021-12-24 | 北京奇艺世纪科技有限公司 | Method and device for adjusting connection timeout |
| CN110012093A (en)* | 2019-04-02 | 2019-07-12 | 北京奇艺世纪科技有限公司 | A kind of method and device of adjustment connection time-out time |
| CN110166572A (en)* | 2019-06-06 | 2019-08-23 | 北京达佳互联信息技术有限公司 | Network processing method, device, electronic equipment and storage medium |
| CN113411829A (en)* | 2020-03-17 | 2021-09-17 | 中国联合网络通信集团有限公司 | Carrier configuration method, device, apparatus and storage medium |
| CN111598487A (en)* | 2020-06-22 | 2020-08-28 | 拉扎斯网络科技（上海）有限公司 | Data processing and model training method, apparatus, electronic device and storage medium |
| CN111598487B (en)* | 2020-06-22 | 2024-03-15 | 拉扎斯网络科技（上海）有限公司 | Data processing and model training methods, devices, electronic equipment and storage media |
| CN112118329A (en)* | 2020-08-31 | 2020-12-22 | 北京奇艺世纪科技有限公司 | Network request processing method and device, electronic equipment and storage medium |
| CN112330151A (en)* | 2020-11-05 | 2021-02-05 | 河北中废通网络技术有限公司 | Service processing method, terminal device and storage medium |
| CN112637362A (en)* | 2020-12-30 | 2021-04-09 | 北京奇艺世纪科技有限公司 | Request result determining method, device and system, electronic equipment and storage medium |
| CN112637362B (en)* | 2020-12-30 | 2022-10-25 | 北京奇艺世纪科技有限公司 | Request result determining method, device and system, electronic equipment and storage medium |
| CN113873026A (en)* | 2021-09-24 | 2021-12-31 | 深圳市元征科技股份有限公司 | Dynamic timeout response method, device, terminal equipment and storage medium |
| CN115225503A (en)* | 2022-05-16 | 2022-10-21 | 北京邮电大学 | OpenFlow flow table item dynamic timeout allocation method and related equipment |
| CN115225503B (en)* | 2022-05-16 | 2023-07-04 | 北京邮电大学 | OpenFlow flow entry dynamic timeout allocation method and related equipment |
| Publication number | Publication date |
|---|---|
| CN105939225B (en) | 2019-04-02 |
| Publication | Publication Date | Title |
|---|---|---|
| CN105939225A (en) | Method and device for executing service | |
| US9104498B2 (en) | Maximizing server utilization within a datacenter | |
| EP3789876B1 (en) | Dynamic capacity optimization for shared computing resources | |
| WO2016119412A1 (en) | Resource scaling method on cloud platform and cloud platform | |
| US20160378570A1 (en) | Techniques for Offloading Computational Tasks between Nodes | |
| US20140325524A1 (en) | Multilevel load balancing | |
| CN112579304A (en) | Resource scheduling method, device, equipment and medium based on distributed platform | |
| TW201816692A (en) | Risk identification method, client device, and risk identification system | |
| KR20190015370A (en) | Adaptive resource allocation method and apparatus | |
| CN109739627B (en) | Task scheduling method, electronic device and medium | |
| CN106817499A (en) | A kind of resources for traffic dispatching method and forecast dispatching device | |
| US11966273B2 (en) | Throughput-optimized, quality-of-service aware power capping system | |
| HoseinyFarahabady et al. | Q-flink: A qos-aware controller for apache flink | |
| WO2022057001A1 (en) | Device management method and system, and management cluster | |
| TWI671708B (en) | Flow rate control method and device | |
| CN114143327A (en) | Cluster resource quota allocation method, device and electronic device | |
| CN106464733A (en) | Method and device for adjusting virtual resources in cloud computing | |
| CN113542027B (en) | Flow isolation method, device and system based on distributed service architecture | |
| US9128754B2 (en) | Resource starvation management in a computer system | |
| CN114281479A (en) | A container management method and device | |
| CN105404554B (en) | Method and device for Storm streaming computing framework | |
| CN110659108B (en) | A cloud system virtual machine task migration method, device and server | |
| CN107315636A (en) | A kind of resource availability method for early warning and device | |
| US11681353B1 (en) | Power capping in a composable computing system | |
| CN107203256B (en) | Energy-saving distribution method and device under network function virtualization scene |
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |