WO2019206033A1 - 服务器配置的方法和装置 - Google Patents

服务器配置的方法和装置 Download PDF

Info

Publication number
WO2019206033A1
WO2019206033A1 PCT/CN2019/083423 CN2019083423W WO2019206033A1 WO 2019206033 A1 WO2019206033 A1 WO 2019206033A1 CN 2019083423 W CN2019083423 W CN 2019083423W WO 2019206033 A1 WO2019206033 A1 WO 2019206033A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain name
bandwidth
server
threshold
servers
Prior art date
Application number
PCT/CN2019/083423
Other languages
English (en)
French (fr)
Inventor
余志文
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to EP19793601.6A priority Critical patent/EP3787231B1/en
Priority to JP2020559432A priority patent/JP2021522583A/ja
Publication of WO2019206033A1 publication Critical patent/WO2019206033A1/zh
Priority to US17/079,231 priority patent/US11431669B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/58—Caching of addresses or names
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • the present invention relates to the field of Internet technology applications, and in particular, to a method and apparatus for server configuration.
  • the traffic is usually spread to multiple servers. How many servers a domain name uses in a region may be randomly specified by the scheduling system.
  • the operation and maintenance personnel find that the service quality is poor, manual operation measures are taken to avoid the problem; the domain name configuration file or the default value of the scheduling system may be used. After the business changes, the operation and maintenance personnel need to modify the configuration content.
  • the access speed will be slow; but it is not the more servers, the better; in the CDN system, it is usually best to store the accessed domain name in the cache, so that the client directly calls the cache when accessing, so that The fastest speed; if the accessed domain name is not stored in the cache, then the Domain Name System (DNS) is required to recursively request the domain name, but the access speed will be slower.
  • DNS Domain Name System
  • the number of servers configured in a domain is usually randomly assigned or configured. These need to be adjusted according to actual conditions according to experience or manual. In addition, the operation cost is high and the accuracy of the configuration cannot be guaranteed.
  • the embodiment of the present invention provides a method and a device for configuring a server, so as to at least solve the problem that the number of servers configured in one domain in a region is required to be adjusted according to actual conditions according to experience or manual in real time, resulting in high operation and maintenance cost. There is no technical problem with the accuracy of the configuration.
  • a method for configuring a server includes: performing data mining according to a first domain name bandwidth and a server local cache hit ratio, and obtaining a threshold corresponding to a bandwidth of the first domain name; according to the threshold and the second domain name The size of the bandwidth, the number of servers to be allocated.
  • the method further includes: adjusting, according to a preset proportion, a bandwidth of the first domain name on the server cluster; and obtaining, according to the adjusted state change of the first domain name bandwidth and the server local cache hit ratio,
  • the adjusted threshold is such that the number of servers to be allocated is obtained according to the adjusted threshold.
  • performing data mining according to the first domain name bandwidth and the server local cache hit ratio, and obtaining a threshold corresponding to the first domain name bandwidth includes: obtaining a first domain name bandwidth of any domain name from the user access log, and obtaining a server local cache hit ratio And determining a threshold according to a correspondence between a change in the value of the first domain name bandwidth and a state change of the server local cache hit ratio.
  • obtaining the first domain name bandwidth of any domain name from the user access log, and obtaining the server local cache hit ratio includes: obtaining the first domain name bandwidth of any domain name from the user access log according to a preset period, and obtaining Server local cache hit ratio.
  • determining the threshold according to the relationship between the change of the value of the bandwidth of the first domain name and the state change of the local cache hit ratio of the server includes: changing according to the value of the first domain name bandwidth and the state change of the server local cache hit ratio, When the value of the first domain name bandwidth is a specific value, the specific value when the server local cache hit ratio is no longer raised or slightly increased is determined as a threshold.
  • the number of servers to be allocated is obtained according to the threshold and the size of the bandwidth of the second domain name, where the number of servers to be allocated is obtained according to the current domain name bandwidth and the threshold, where the second domain name bandwidth includes the current domain name bandwidth;
  • the current domain name bandwidth is obtained in real time through the traffic collection device.
  • obtaining the current number of servers to be allocated includes: dividing the current domain name bandwidth by a threshold to obtain the current number of servers to be allocated.
  • the number of servers to be allocated is obtained according to the threshold and the size of the second domain name bandwidth.
  • the predicted number of servers to be allocated is obtained according to the domain name bandwidth prediction value and the threshold.
  • obtaining the predicted number of servers to be allocated includes: dividing the domain name bandwidth prediction value by the threshold value to obtain a predicted number of servers to be allocated.
  • the first domain name bandwidth includes: a server bandwidth; and the second domain name bandwidth includes: a bandwidth purchased from a provider.
  • adjusting the first domain name bandwidth according to a preset ratio on the server cluster includes: enlarging or reducing the first domain name bandwidth according to a preset ratio on the server cluster.
  • the server cluster includes: at least one server.
  • an apparatus for configuring a server includes: an obtaining module, configured to perform data mining according to a first domain name bandwidth and a server local cache hit ratio, to obtain a threshold corresponding to a first domain name bandwidth.
  • the first configuration module is configured to obtain the number of servers to be allocated according to the threshold and the size of the second domain name bandwidth.
  • the device configured by the server further includes: an adjustment module, configured to adjust a first domain name bandwidth according to a preset ratio on the server cluster after obtaining the number of servers to be allocated; and a second configuration module, configured to adjust The state of the first domain name bandwidth and the server local cache hit rate change, and the adjusted threshold is obtained, so that the number of servers to be allocated is obtained according to the adjusted threshold.
  • an adjustment module configured to adjust a first domain name bandwidth according to a preset ratio on the server cluster after obtaining the number of servers to be allocated
  • a second configuration module configured to adjust The state of the first domain name bandwidth and the server local cache hit rate change, and the adjusted threshold is obtained, so that the number of servers to be allocated is obtained according to the adjusted threshold.
  • a storage medium includes a stored program, where the device that controls the storage medium is executed during the running of the program: performing according to the first domain name bandwidth and the server local cache hit ratio.
  • Data mining obtains a threshold corresponding to the bandwidth of the first domain name; and according to the threshold and the size of the bandwidth of the second domain name, the number of servers to be allocated is obtained.
  • a processor is further provided, where the processor is configured to run a program, where the running of the program is performed: performing data mining according to the first domain name bandwidth and the server local cache hit ratio, and obtaining the first domain name
  • the threshold corresponding to the bandwidth; the number of servers to be allocated is obtained according to the threshold and the size of the bandwidth of the second domain name.
  • the threshold of the first domain name bandwidth is obtained by performing data mining according to the first domain name bandwidth and the server local cache hit ratio by using the relationship between the domain name bandwidth and the server local cache hit ratio.
  • the number of servers to be allocated is obtained, thereby achieving the purpose of reducing the pressure of manual operation and maintenance, thereby realizing the technical effect of improving the configuration accuracy rate, thereby solving the problem that the domain name is in a region due to the prior art.
  • the number of servers to be configured needs to be adjusted according to the actual situation according to experience or manual, resulting in high technical cost of operation and maintenance and the technical accuracy of the configuration.
  • FIG. 1 is a block diagram showing the hardware structure of a computer terminal of a server configuration method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for server configuration according to a first embodiment of the present invention
  • FIG. 3 is a flowchart of another method of server configuration according to Embodiment 1 of the present invention.
  • FIG. 5 is a schematic structural diagram of an apparatus for configuring a server according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic structural diagram of another apparatus configuration apparatus according to Embodiment 2 of the present invention.
  • CDN Content Distribution Network, Content Delivery Network.
  • FIG. 1 is a hardware block diagram of a computer terminal of a server configuration method according to an embodiment of the present invention.
  • computer terminal 10 may include one or more (only one shown) processor 102 (processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
  • processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
  • a memory 104 for storing data
  • a transmission module 106 for communication functions.
  • computer terminal 10 may also include more or fewer components than those shown in FIG. 1, or have a different configuration than that shown in FIG.
  • the memory 104 can be used to store software programs and modules of the application software, such as program instructions/modules corresponding to the method of the server configuration in the embodiment of the present invention, and the processor 102 executes each of the software programs and modules stored in the memory 104.
  • a functional application and data processing that is, a method of implementing server configuration of the above application.
  • Memory 104 may include high speed random access memory, and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 104 may further include memory remotely located relative to processor 102, which may be coupled to computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 106 is for receiving or transmitting data via a network.
  • the network specific examples described above may include a wireless network provided by a communication provider of the computer terminal 10.
  • the transmission device 106 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 106 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF Radio Frequency
  • the present application provides a method of server configuration as shown in FIG. 2.
  • 2 is a flow chart of a method of server configuration according to a first embodiment of the present invention.
  • the method for configuring the server provided by this application is as follows:
  • Step S202 Perform data mining according to the first domain name bandwidth and the server local cache hit ratio, and obtain a threshold corresponding to the bandwidth of the first domain name;
  • step S202 of the present application in order to avoid the fact that a domain name is configured in a region according to the prior art, it needs to be adjusted according to actual conditions according to experience or manual real time, resulting in high operation and maintenance cost and incapability of ensuring accurate configuration. Rate problem
  • the server configuration method provided by the present application obtains the domain name bandwidth size of any domain name from the user access log (that is, the first domain name bandwidth provided by the application, wherein the first domain name bandwidth includes: server bandwidth), and the server local
  • the cache hit rate is obtained according to the relationship between the first domain name bandwidth of the domain name and the server local cache hit ratio.
  • the principle of the threshold is: when the first domain name bandwidth is greater than the threshold, the server locally caches the hit. The rate is no longer increased or only slightly increased; this threshold can be obtained according to this rule.
  • the reason why the server's local cache hit rate is no longer improved or only slightly increased is that, when a user accesses a file, for example, if a user accesses a file with a probability of n%, when the number of users is more than a certain degree, a file is The cache will have a large probability. Therefore, when the user reaches a certain level, the threshold is reflected in the domain name bandwidth. After the file exists in the cache with a high probability, the server local cache hit rate is no longer increased, that is, the access volume is increased. Will "dilute" the server local cache "non-hit rate".
  • the thresholds are different for different domain names. For example, the thresholds for the unpopular and popular websites are different, and the thresholds for the portal and the video website are also different. As an example, for a webpage and a picture service, the reference single-band bandwidth threshold is 20M, and for live and on-demand services, the reference single-machine bandwidth threshold is 50M.
  • Step S204 obtaining the number of servers to be allocated according to the threshold and the size of the second domain name bandwidth
  • step S204 of the present application based on the threshold obtained in step S202 and the size of the second domain name bandwidth (the second domain name bandwidth in the present application may include: the bandwidth purchased from the provider), according to the second domain name bandwidth and the threshold
  • the mathematical relationship can be obtained corresponding to the number of servers to be allocated, that is, the number of servers to be allocated provided by the present application.
  • the second domain name bandwidth can be understood as the bandwidth purchased from the supplier, for example, the video website A purchases 10G bandwidth from the CDN provider B.
  • the number of servers to be allocated can be obtained.
  • the server configuration method provided by the present application is to quantize the relationship between the domain name bandwidth and the number of servers in CDN traffic scheduling. For example, if a portal has 10G bandwidth, how many servers need to achieve optimal effect, so that the traffic is not too scattered. The impact on the local cache hit rate is not too concentrated and affects high availability (the more concentrated the traffic, the more users affected by the single machine failure, the greater the damage to the overall service quality), achieving the goal of both quality and high availability. .
  • FIG. 3 is a flowchart of another method for configuring a server according to the first embodiment of the present invention
  • FIG. 3 is a flowchart of a method for configuring a server according to the first embodiment of the present invention. Also includes:
  • Step S206 adjusting the first domain name bandwidth according to a preset ratio on the server cluster
  • step S206 of the present application the number of servers to be allocated is obtained based on step S204.
  • step S204 in order to improve the accuracy of obtaining the threshold, the threshold value is further mined, that is, the first step is adjusted according to the preset ratio in step S206. Domain name bandwidth.
  • the adjusting the first domain name bandwidth according to the preset ratio on the server cluster in step S206 includes: enlarging or reducing the first domain name bandwidth according to a preset ratio on the server cluster.
  • the preset ratio is 20%
  • the bandwidth of the first domain name is X
  • X is adjusted by a float of 20%.
  • Step S208 Obtain an adjusted threshold according to the state change of the adjusted first domain name bandwidth and the server local cache hit ratio, so that the number of servers to be allocated is obtained according to the adjusted threshold.
  • the adjusted threshold is obtained based on the adjusted state of the first domain name bandwidth and the server local cache hit ratio, that is, the server corresponding to the first domain name bandwidth observation is enlarged or reduced according to the preset ratio.
  • the cache hit rate state change is obtained according to the principle of the threshold value obtained in step S202, and the adjusted threshold value is obtained, and after the adjusted threshold value is obtained in the process of configuring the number of servers for the second time, according to step S204, according to the adjusted step Threshold configured number of servers to be allocated.
  • a small number of servers are randomly selected from the total server cluster, and the amplification refers to an amount larger than the bandwidth of the first domain name in the process of obtaining the threshold in step S202, and whether the server local cache hit ratio is improved; or
  • the reduction refers to a smaller value than the bandwidth of the first domain name in the process of obtaining the threshold in step S202, and observes whether the local cache hit rate of the server is decreased, thereby dynamically determining the threshold according to the state change of the server local cache hit ratio.
  • the threshold of the first domain name bandwidth is obtained by using the relationship between the domain name bandwidth and the server local cache hit rate to obtain the threshold according to the first domain name bandwidth and the server local cache hit ratio;
  • the threshold value and the size of the second domain name bandwidth are obtained by the number of servers to be allocated, thereby achieving the purpose of reducing the pressure of manual operation and maintenance, thereby achieving the technical effect of improving the configuration accuracy rate, thereby solving the problem that the domain name is configured in one area due to the prior art.
  • the number of servers needs to be adjusted according to the actual situation according to experience or manual, resulting in high technical cost of operation and maintenance and the technical accuracy of the configuration cannot be guaranteed.
  • step S202 performing data mining according to the first domain name bandwidth and the server local cache hit ratio, and obtaining a threshold corresponding to the first domain name bandwidth includes:
  • step S2021 the first domain name bandwidth of any domain name is obtained from the user access log, and the server local cache hit ratio is obtained.
  • Step S2022 Determine a threshold according to a correspondence between a change in the value of the first domain name bandwidth and a state change of the server local cache hit ratio.
  • the server local cache hit ratio is no longer increased or only slightly increased, and the threshold is determined according to the law.
  • determining the threshold includes: changing the value of the bandwidth of the first domain name and the state change of the local cache hit ratio of the server, and the first domain name
  • the value of the bandwidth is a specific value
  • the specific value when the server local cache hit ratio is no longer raised or slightly increased is determined as a threshold.
  • obtaining the first domain name bandwidth of any domain name from the user access log in step S2021, and obtaining the server local cache hit ratio includes:
  • step S20211 the first domain name bandwidth of any domain name is obtained from the user access log according to the preset period, and the server local cache hit ratio is obtained.
  • the server configuration method provided by the present application can obtain not only the number of servers to be allocated currently, but also the number of servers to be allocated.
  • Solution 1 Obtain the current number of servers to be allocated
  • the number of servers to be allocated includes:
  • Step S2041 If the second domain name bandwidth includes the current domain name bandwidth, the current number of servers to be allocated is obtained according to the current domain name bandwidth and the threshold.
  • the current domain name bandwidth is obtained by the traffic collection device in real time.
  • the number of servers to be allocated according to the current domain name bandwidth and the threshold includes: dividing the current domain name bandwidth by a threshold to obtain the current number of servers to be allocated.
  • the calculation is performed according to the threshold and the current domain name bandwidth, and the current number of servers to be allocated is obtained, where the calculation according to the threshold and the current domain name bandwidth includes:
  • the current number of servers to be allocated is the current domain name bandwidth/threshold.
  • the current domain name bandwidth is obtained by the traffic collection device in real time.
  • the traffic collection device may include a routing device.
  • the number of servers to be allocated includes:
  • Step S2041 in the case that the second domain name bandwidth includes the domain name bandwidth prediction value, the predicted number of servers to be allocated is obtained according to the domain name bandwidth prediction value and the threshold.
  • the predicting the number of servers to be allocated according to the domain name bandwidth prediction value and the threshold value includes: dividing the domain name bandwidth prediction value by the threshold value to obtain a predicted number of servers to be allocated.
  • the calculation is performed according to the threshold value and the domain name bandwidth prediction value, and the number of servers to be allocated is obtained, wherein the calculation according to the threshold value and the domain name bandwidth prediction value includes:
  • Predicting the number of servers to be allocated domain name bandwidth prediction value/threshold value; wherein the domain name bandwidth prediction value can be obtained by machine learning prediction, that is, predicting the upcoming domain name bandwidth according to historical data, and obtaining a domain name bandwidth prediction value, wherein, historical data It can include the domain name bandwidth that history has purchased from the vendor.
  • the server cluster includes: at least one server.
  • the server configuration method provided by the present application implements the dynamic allocation of the server according to the obtained threshold, combined with the current bandwidth size or the future bandwidth prediction value.
  • the minimum number of servers directly used is less than the minimum number of servers required for the domain name.
  • FIG. 4 is a flowchart of still another method for server configuration according to the first embodiment of the present invention, that is,
  • Step 1 Query the relationship between the traffic (domain name bandwidth) and the server local cache hit ratio from the log to obtain a threshold.
  • Step 2 According to the threshold dynamic and the domain name bandwidth, obtain the number of servers to be allocated;
  • Step 3 Deliberately scale the bandwidth of a domain name on a small number of machines to create a condition for mining the threshold for step 1.
  • the method for configuring the server provided by the present application can be implemented by looping steps 1 to 3, thereby achieving the purpose of reducing the pressure of manual operation and maintenance, thereby achieving the technical effect of improving the configuration accuracy rate, thereby solving the existing
  • the number of servers configured in a domain needs to be adjusted according to experience or manual real-time according to actual conditions, resulting in high technical cost of operation and maintenance, and the technical accuracy of the configuration cannot be guaranteed.
  • the method of server configuration provided by the present application clarifies the quantitative basis, that is, from the perspective of the relationship between the server local cache hit ratio and the traffic size, how many servers are used for how much bandwidth is used.
  • the system can intelligently decide how many machines should be used in an area, without the follow-up of operation and maintenance personnel, which greatly saves labor costs.
  • the method of server configuration according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, hardware, but in many cases.
  • the former is a better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • FIG. 5 is a schematic structural diagram of a device configured by a server according to Embodiment 2 of the present invention. As shown in FIG. The acquisition module 52 and the first configuration module 54 are included.
  • the obtaining module 52 is configured to perform data mining according to the first domain name bandwidth and the server local cache hit ratio, and obtain a threshold corresponding to the bandwidth of the first domain name.
  • the first configuration module 54 is configured to use the threshold and the bandwidth of the second domain name. Get the number of servers to be assigned.
  • the method for obtaining the threshold by using the relationship between the domain name bandwidth and the server local cache hit ratio is used by the obtaining module to perform data mining according to the first domain name bandwidth and the server local cache hit ratio to obtain the first domain name.
  • the threshold corresponding to the bandwidth; the first configuration module is configured to obtain the number of servers to be allocated according to the threshold and the size of the second domain name bandwidth, thereby achieving the purpose of reducing the pressure of manual operation and maintenance, thereby achieving the technical effect of improving the configuration accuracy rate, and further
  • the technical problem that the prior art is configured in a domain name in one area needs to be adjusted according to actual conditions according to experience or manual real time, which results in high operation and maintenance cost and cannot guarantee the accuracy of configuration.
  • the foregoing obtaining module 52 and the first configuration module 54 correspond to step S202 and step S204 in the first embodiment.
  • the two modules are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the above.
  • the foregoing module may be implemented in the server provided in the first embodiment as a part of the device, and may be implemented by software or by hardware.
  • FIG. 6 is a schematic structural diagram of another server configuration apparatus according to Embodiment 2 of the present invention. As shown in FIG. 6, the apparatus further includes: an adjustment module 56 and a second configuration module 58.
  • the adjusting module 56 is configured to adjust the first domain name bandwidth according to a preset ratio on the server cluster after obtaining the number of servers to be allocated; the second configuration module 58 is configured to adjust the first domain name bandwidth and the server local cache according to the preset The state of the hit rate changes, and the adjusted threshold is obtained, so that the number of servers to be allocated is obtained according to the adjusted threshold.
  • the foregoing adjustment module 56 and the second configuration module 58 correspond to step S206 and step S208 in the first embodiment.
  • the two modules are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the above.
  • the foregoing module may be implemented in the server provided in the first embodiment as a part of the device, and may be implemented by software or by hardware.
  • a storage medium includes a stored program, where the device that controls the storage medium is executed during the running of the program: performing according to the first domain name bandwidth and the server local cache hit ratio.
  • Data mining the threshold corresponding to the bandwidth of the first domain name is obtained; the number of servers to be allocated is obtained according to the threshold and the bandwidth of the second domain name; the bandwidth of the first domain name is adjusted according to a preset ratio on the server cluster; and the bandwidth of the first domain name is adjusted according to the preset And the state change of the server local cache hit ratio, and the adjusted threshold is obtained.
  • a processor is further provided, where the processor is configured to run a program, where the running of the program is performed: performing data mining according to the first domain name bandwidth and the server local cache hit ratio, and obtaining the first domain name
  • the threshold corresponding to the bandwidth; the number of servers to be allocated is obtained according to the threshold and the bandwidth of the second domain name; the bandwidth of the first domain name is adjusted according to a preset ratio on the server cluster; and the bandwidth of the first domain name and the local cache hit ratio of the server are adjusted according to the adjusted first domain name bandwidth
  • the state changes and the adjusted threshold is obtained.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be used to save the program code executed by the method of the server configuration provided in Embodiment 1 above.
  • the foregoing storage medium may be located in any one of the computer terminal groups in the computer network, or in any one of the mobile terminal groups.
  • the storage medium is configured to store program code for performing the following steps: performing data mining according to the first domain name bandwidth and the server local cache hit ratio, and obtaining a threshold corresponding to the first domain name bandwidth; The threshold and the size of the second domain name bandwidth, and the number of servers to be allocated.
  • the storage medium is configured to store program code for performing the following steps: after obtaining the number of servers to be allocated, adjusting the first domain name bandwidth according to a preset ratio on the server cluster; The state of the first domain name bandwidth and the server local cache hit rate change, and the adjusted threshold is obtained, so that the number of servers to be allocated is obtained according to the adjusted threshold.
  • the storage medium is configured to store program code for performing the following steps: performing data mining according to the first domain name bandwidth and the server local cache hit ratio, and obtaining a threshold corresponding to the first domain name bandwidth includes: The first domain name bandwidth of any domain name is obtained from the user access log, and the server local cache hit ratio is obtained. The threshold is determined according to the correspondence between the value change of the first domain name bandwidth and the state change of the server local cache hit ratio.
  • the storage medium is configured to store program code for performing the following steps: obtaining a first domain name bandwidth of any domain name from the user access log, and obtaining a server local cache hit ratio including : Obtain the first domain name bandwidth of any domain name from the user access log according to the preset period, and obtain the server local cache hit ratio.
  • the storage medium is configured to store program code for performing the following steps: determining the threshold according to the correspondence between the change of the value of the first domain name bandwidth and the state change of the server local cache hit ratio includes: According to the change of the value of the bandwidth of the first domain name and the state change of the local cache hit ratio of the server, if the value of the bandwidth of the first domain name is a specific value, the specific value of the server local cache hit ratio is no longer increased or slightly increased. Is the threshold.
  • the number of servers to be allocated is obtained according to the threshold and the size of the bandwidth of the second domain name, where the number of servers to be allocated is obtained according to the current domain name bandwidth and the threshold, where the second domain name bandwidth includes the current domain name bandwidth;
  • the current domain name bandwidth is obtained in real time through the traffic collection device.
  • the storage medium is configured to store program code for performing the following steps: according to the current domain name bandwidth and the threshold, obtaining the current number of servers to be allocated includes: dividing the current domain name bandwidth by the threshold , get the current number of servers to be allocated.
  • the storage medium is configured to store program code for performing the following steps: according to the threshold and the size of the second domain name bandwidth, obtaining the number of servers to be allocated includes: including the domain name bandwidth in the second domain name bandwidth In the case of the predicted value, the number of servers to be allocated is obtained based on the predicted value of the domain name bandwidth and the threshold.
  • the storage medium is configured to store program code for performing the following steps: according to the domain name bandwidth prediction value and the threshold, obtaining the predicted number of servers to be allocated includes: dividing by the domain name bandwidth prediction value With the threshold, the number of servers to be allocated is predicted.
  • the storage medium is configured to store program code for performing the following steps: the first domain name bandwidth includes: server bandwidth; and the first domain name bandwidth includes: bandwidth purchased from the vendor.
  • the storage medium is configured to store program code for performing the following steps: adjusting the first domain name bandwidth according to a preset ratio on the server cluster comprises: enlarging according to a preset ratio on the server cluster or Reduce the bandwidth of the first domain name.
  • the storage medium is configured to store program code for performing the following steps:
  • the server cluster includes: at least one server.
  • the disclosed technical contents may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, unit or module, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明公开了一种服务器配置的方法和装置。其中，该方法包括：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；依据阈值和第二域名带宽的大小，得到待分配服务器数量。本发明解决了由于现有技术在一个域名在一个地区配置服务器数量上，需要依据经验或人工实时的根据实际情况调整，导致运维成本高且无法保障配置的精确率的技术问题。

Description

服务器配置的方法和装置
本申请要求2018年4月25日递交的申请号为201810377843.1、发明名称为“服务器配置的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及互联网技术应用领域，具体而言，涉及一种服务器配置的方法和装置。
背景技术
内容分发网络(Content Delivery Network，简称CDN)流量调度中，为了避免单机故障影响过多的用户，通常将流量打散到多台服务器上。一个域名在一个地区使用多少台服务器，可能由调度系统随机指定，运维人员发现服务质量较差时，采取人工调度措施来规避问题；也可能以域名的配置文件或者调度系统默认值为准，业务变化后，运维人员需要跟着修改配置内容。
其中，如果服务器过少，会导致访问速度慢；但是也并非是服务器越多越好；在CDN体系中，通常最好是被访问域名储存在缓存中，使得客户在访问时直接调用缓存，这样速度最快；如果被访问域名没有存储在缓存中，那么需要向上层域名系统(Domain Name System，简称DNS)递归请求域名，但是访问速度就会变慢。
现有技术在一个域名在一个地区配置服务器数量上，通常都是随机指定或配置指定，这些需要依据经验或人工实时的根据实际情况调整，不仅运维成本高还无法保障配置的精确率。
针对上述由于在一个域名在一个地区配置服务器数量上，需要依据经验或人工实时的根据实际情况调整，导致运维成本高且无法保障配置的精确率的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种服务器配置的方法和装置，以至少解决由于现有技术在一个域名在一个地区配置服务器数量上，需要依据经验或人工实时的根据实际情况调整，导致运维成本高且无法保障配置的精确率的技术问题。
根据本发明实施例的一个方面，提供了一种服务器配置的方法，包括：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；依据阈 值和第二域名带宽的大小，得到待分配服务器数量。
可选的，在得到待分配服务器数量之后，该方法还包括：在服务器集群上根据预设比例调整第一域名带宽；根据调整后的第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值，以使得根据调整后的阈值得到待分配服务器数量。
可选的，根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值包括：从用户访问日志中获取任意域名的第一域名带宽，并获取服务器本地缓存命中率；根据第一域名带宽的数值变化与服务器本地缓存命中率的状态变化的对应关系，确定阈值。
进一步地，可选的，从用户访问日志中获取任意域名的第一域名带宽，并获取服务器本地缓存命中率包括：依据预设周期从用户访问日志中获取任意域名的第一域名带宽，并获取服务器本地缓存命中率。
可选的，根据第一域名带宽的数值变化与服务器本地缓存命中率的状态变化的对应关系，确定阈值包括：依据第一域名带宽的数值的变动与服务器本地缓存命中率的状态变化，将在第一域名带宽的数值为特定值的情况下，服务器本地缓存命中率不再提升或小幅提升时的特定值确定为阈值。
可选的，依据阈值和第二域名带宽的大小，得到待分配服务器数量包括：在第二域名带宽包括当前域名带宽的情况下，根据当前域名带宽与阈值，得到当前待分配服务器数量；其中，当前域名带宽通过流量采集设备实时获取。
进一步地，可选的，根据当前域名带宽与阈值，得到当前待分配服务器数量包括：通过当前域名带宽除以阈值，得到当前待分配服务器数量。
可选的，依据阈值和第二域名带宽的大小，得到待分配服务器数量包括：在第二域名带宽包括域名带宽预测值的情况下，根据域名带宽预测值与阈值，得到预测待分配服务器数量。
进一步地，可选的，根据域名带宽预测值与阈值，得到预测待分配服务器数量包括：通过域名带宽预测值除以阈值，得到预测待分配服务器数量。
可选的，第一域名带宽包括：服务器带宽；第二域名带宽包括：向供应商购买的带宽。
可选的，在服务器集群上根据预设比例调整第一域名带宽包括：在服务器集群上根据预设比例放大或缩小第一域名带宽。
进一步地，可选的，服务器集群包括：至少一台服务器。
根据本发明实施例的另一方面，还提供了一种服务器配置的装置，包括：获取模块，用于根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；第一配置模块，用于依据阈值和第二域名带宽的大小，得到待分配服务器数量。
可选的，所述服务器配置的装置还包括：调整模块，用于在得到待分配服务器数量之后，在服务器集群上根据预设比例调整第一域名带宽；第二配置模块，用于根据调整后的第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值，以使得根据调整后的阈值得到待分配服务器数量。
根据本发明实施例的又一方面，还提供了一种存储介质，存储介质包括存储的程序，其中，在程序运行时控制存储介质所在设备执行：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；依据阈值和第二域名带宽的大小，得到待分配服务器数量。
根据本发明实施例的再一方面，还提供了一种处理器，处理器用于运行程序，其中，程序运行时执行：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；依据阈值和第二域名带宽的大小，得到待分配服务器数量。
在本发明实施例中，采用域名带宽和服务器本地缓存命中率之间的关系获取阈值的方式，通过根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；依据阈值和第二域名带宽的大小，得到待分配服务器数量，达到了减轻人工运维压力的目的，从而实现了提升配置精确率的技术效果，进而解决了由于现有技术在一个域名在一个地区配置服务器数量上，需要依据经验或人工实时的根据实际情况调整，导致运维成本高且无法保障配置的精确率的技术问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是本发明实施例的一种服务器配置的方法的计算机终端的硬件结构框图；
图2是根据本发明实施例一的一种服务器配置的方法的流程图；
图3是根据本发明实施例一的另一种服务器配置的方法的流程图；
图4是根据本发明实施例一的又一种服务器配置的方法的流程图；
图5是根据本发明实施例二的一种服务器配置的装置的结构示意图；
图6是根据本发明实施例二的另一种服务器配置的装置的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请涉及的技术名称：
CDN：内容分发网络，Content Delivery Network。
实施例1
根据本发明实施例，还提供了一种服务器配置的方法实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本申请实施例一所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在计算机终端上为例，图1是本发明实施例的一种服务器配置的方法的计算机终端的硬件结构框图。如图1所示，计算机终端10可以包括一个或多个(图中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)、用于存储数据的存储器104、以及用于通信功能的传输模块106。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述电子装置的结构造成限定。例如，计算机终端10还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储应用软件的软件程序以及模块，如本发明实施例中的服务器 配置的方法对应的程序指令/模块，处理器102通过运行存储在存储器104内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的应用程序的服务器配置的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端10的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通讯。
在上述运行环境下，本申请提供了如图2所示的服务器配置的方法。图2是根据本发明实施例一的一种服务器配置的方法的流程图。本申请提供的服务器配置的方法具体如下：
步骤S202，根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；
本申请上述步骤S202中，基于CDN网络，为了避免由于现有技术一个域名在一个地区配置服务器数量上，需要依据经验或人工实时的根据实际情况调整，导致运维成本高且无法保障配置的精确率的问题；
本申请提供的服务器配置的方法通过从用户访问日志中获取任意一个域名的域名带宽大小(即，本申请提供的第一域名带宽，其中，该第一域名带宽包括：服务器带宽)，以及服务器本地缓存命中率，并根据该域名的第一域名带宽大小和服务器本地缓存命中率之间的关系，得到阈值，其中，该获取阈值的原理在于：当第一域名带宽大于阈值后，服务器本地缓存命中率不再提升或者只有小幅提升；根据该规律则可以得到该阈值。
该服务器本地缓存命中率不再提升或者只有小幅提升的原因在于，以一个用户访问一个文件为例，如果一个用户访问一个文件的概率为n％，当用户数多到一定程度后，一个文件在缓存中会以大概率存在，因此当用户多到一定程度时，反映在域名带宽上就是阈值，文件以大概率存在于缓存后，服务器本地缓存命中率就不再提升，即，访问量的增加会“稀释”掉服务器本地缓存“非命中率”。
其中，对于不同的域名，其阈值亦不同，例如对于冷门网站和热门网站的阈值是不同的，对于门户网站和视频网站的阈值亦是不同的。作为示例，对于网页及图片业务，参考单机带宽阈值为20M，而对于直播及点播业务，参考单机带宽阈值为50M。
步骤S204，依据阈值和第二域名带宽的大小，得到待分配服务器数量；
本申请上述步骤S204中，基于步骤S202中得到阈值和第二域名带宽的大小(本申请中的第二域名带宽可以包括：向供应商购买的带宽)，根据第二域名带宽和阈值之间的数学关系可以得到对应待分配服务器的数量，即本申请提供的待分配服务器数量。
这里第二域名带宽可以理解为向供应商购买的带宽，例如视频网站A向CDN供应商B购买10G带宽。
其中，该数学关系可以包括：待分配服务器数量＝第二域名带宽/阈值；
根据该数学关系可得到待分配的服务器数量。本申请提供的服务器配置的方法旨在CDN流量调度中，量化域名带宽与服务器数量的关系，例如，某门户网站有10G带宽，那么需要多少台服务器会达到最优效果，使得流量不至于太分散而影响本地缓存命中率，也不至于太集中而影响高可用性(流量越集中，单机故障影响的用户越多，对整体服务质量的伤害也就越大)，达到同时兼顾质量与高可用性的目的。
在得到待分配服务器数量之后，为了提升阈值的获取精度，图3是根据本发明实施例一的另一种服务器配置的方法的流程图，如图3所示，本申请提供的服务器配置的方法还包括：
步骤S206，在服务器集群上根据预设比例调整第一域名带宽；
本申请上述步骤S206中，基于步骤S204得到待分配服务器数量，在步骤S204之后，为了提升阈值的获取精确度，对阈值将进行进一步地挖掘，即，在步骤S206中根据预设比例调整第一域名带宽。
可选的，步骤S206在服务器集群上根据预设比例调整第一域名带宽包括：在服务器集群上根据预设比例放大或缩小第一域名带宽。
具体的，假设预设比例为20％，第一域名带宽为X，因此以20％的浮动调整X。
步骤S208，根据调整后的第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值，以使得根据调整后的阈值得到待分配服务器数量。
本申请上述步骤S208中，基于调整后的第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值，即，根据预设比例放大或缩小该第一域名带宽观察对应的服务器本地缓存命中率状态变化，依据步骤S202中的获取阈值的原理，得到调整后的阈 值，进而在第二次配置服务器数量的过程中在得到调整后的阈值后，根据步骤S204，得到根据调整后的阈值配置的待分配服务器数量。
其中，通过在小部分服务器上，刻意地放大或者缩小某个域名的带宽，为阈值挖掘创造条件，即，更好的进行数据挖掘，从而确定阈值，提升了阈值获取精度。
本申请中小部分服务器是从总的服务器集群中随机挑选出来的，放大是指比步骤S202中的得到阈值过程中第一域名带宽更大的量，观察服务器本地缓存命中率是否有提升；或，缩小是指比步骤S202中的得到阈值过程中第一域名带宽更小的量值，观察服务器本地缓存命中率是否有下降，以此动态的根据服务器本地缓存命中率的状态变化，确定阈值。
在本发明实施例中，采用域名带宽和服务器本地缓存命中率之间的关系获取阈值的方式，通过根据第一域名带宽和服务器本地缓存命中率进行挖掘，得到第一域名带宽对应的阈值；依据阈值和第二域名带宽的大小，得到待分配服务器数量，达到了减轻人工运维压力的目的，从而实现了提升配置精确率的技术效果，进而解决了由于现有技术在一个域名在一个地区配置服务器数量上，需要依据经验或人工实时的根据实际情况调整，导致运维成本高且无法保障配置的精确率的技术问题。
可选的，步骤S202中根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值包括：
步骤S2021，从用户访问日志中获取任意域名的第一域名带宽，并获取服务器本地缓存命中率；
步骤S2022，根据第一域名带宽的数值变化与服务器本地缓存命中率的状态变化的对应关系，确定阈值。
其中，当第一域名带宽大于阈值后，服务器本地缓存命中率不再提升或者只有小幅提升，依照该规律确定阈值。
这里根据第一域名带宽的数值变化与服务器本地缓存命中率的状态变化的对应关系，确定阈值包括：依据第一域名带宽的数值的变动与服务器本地缓存命中率的状态变化，将在第一域名带宽的数值为特定值的情况下，服务器本地缓存命中率不再提升或小幅提升时的特定值确定为阈值。
进一步地，可选的，步骤S2021中从用户访问日志中获取任意域名的第一域名带宽，并获取服务器本地缓存命中率包括：
步骤S20211，依据预设周期从用户访问日志中获取任意域名的第一域名带宽，并获 取服务器本地缓存命中率。具体的，本申请提供的服务器配置的方法不仅能够得到当前待分配服务器数量，还可以得到预测待分配服务器数量；
方案一：获取当前待分配服务器数量
可选的，步骤S204中依据阈值和第二域名带宽的大小，得到待分配服务器数量包括：
步骤S2041，在第二域名带宽包括当前域名带宽的情况下，根据当前域名带宽与阈值，得到当前待分配服务器数量；其中，当前域名带宽通过流量采集设备实时获取。
其中，根据当前域名带宽与阈值，得到当前待分配服务器数量包括：通过当前域名带宽除以阈值，得到当前待分配服务器数量。
具体的，根据阈值和当前域名带宽进行计算，得到当前待分配服务器数量，其中，根据阈值和当前域名带宽进行计算包括：
当前待分配服务器数量＝当前域名带宽/阈值；其中，当前域名带宽通过流量采集设备实时获取，这里流量采集设备可以包括路由设备。
方案二：获取预测待分配服务器数量
可选的，步骤S204中依据阈值和第二域名带宽的大小，得到待分配服务器数量包括：
步骤S2041’，在第二域名带宽包括域名带宽预测值的情况下，根据域名带宽预测值与阈值，得到预测待分配服务器数量。
其中，根据域名带宽预测值与阈值，得到预测待分配服务器数量包括：通过域名带宽预测值除以阈值，得到预测待分配服务器数量。
具体的，根据阈值和域名带宽预测值进行计算，得到预测待分配服务器数量，其中，根据阈值和域名带宽预测值进行计算包括：
预测待分配服务器数量＝域名带宽预测值/阈值；其中，域名带宽预测值可以通过机器学习预测得到，即，根据历史数据对即将得到的域名带宽进行预测，得到域名带宽预测值，其中，历史数据可以包括历史向供应商购买的域名带宽。
进一步地，可选的，服务器集群包括：至少一台服务器。
综上，结合方案一和方案二，本申请提供的服务器配置的方法根据取得的阈值，结合当前带宽大小或未来的带宽预测值，实现了动态分配服务器数量。
除此之外，小于域名最低服务器数量要求的直接使用最低服务器数量。
需要说明的是，通过循环步骤S202至步骤S208，如图4所示，图4是根据本发明实施例一的又一种服务器配置的方法的流程图，即，
步骤1，从日志中挖掘流量(域名带宽)与服务器本地缓存命中率的关系，得到阈 值；
步骤2，根据阈值动态和域名带宽，得到待分配的服务器数量；
步骤3，在小部分机器上刻意的缩放某个域名的带宽，从而为步骤1创建挖掘阈值的条件。
如图3所示，通过循环步骤1至3可实现本申请提供的服务器配置的方法，达到了减轻人工运维压力的目的，从而实现了提升配置精确率的技术效果，进而解决了由于现有技术在一个域名在一个地区配置服务器数量上，需要依据经验或人工实时的根据实际情况调整，导致运维成本高且无法保障配置的精确率的技术问题。
本申请提供的服务器配置的方法明确了量化依据，即从服务器本地缓存命中率与流量大小的关系这个角度来量化多大的带宽使用多少台服务器。针对具体的域名，系统可智能地决策一个地区应该使用多少台机器，无需运维人员的跟进，极大地节约了人力成本。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的服务器配置的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例2
根据本发明实施例，还提供了一种用于实施上述服务器配置的方法的装置，图5是根据本发明实施例二的一种服务器配置的装置的结构示意图，如图5所示，该装置包括：获取模块52和第一配置模块54。
其中，获取模块52，用于根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；第一配置模块54，用于依据阈值和第二域名带宽的大小， 得到待分配服务器数量。
在本发明实施例中，采用域名带宽和服务器本地缓存命中率之间的关系获取阈值的方式，通过获取模块，用于根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；第一配置模块，用于依据阈值和第二域名带宽的大小，得到待分配服务器数量，达到了减轻人工运维压力的目的，从而实现了提升配置精确率的技术效果，进而解决了由于现有技术在一个域名在一个地区配置服务器数量上，需要依据经验或人工实时的根据实际情况调整，导致运维成本高且无法保障配置的精确率的技术问题。
此处需要说明的是，上述获取模块52和第一配置模块54对应于实施例一中的步骤S202和步骤S204，两个模块与对应的步骤所实现的示例和应用场景相同，但不限于上述实施例一所公开的内容。需要说明的是，上述模块作为装置的一部分可以运行在实施例一提供的服务器中，可以通过软件实现，也可以通过硬件实现。
可选的，图6是根据本发明实施例二的另一种服务器配置的装置的结构示意图，如图6所示，该装置还包括：调整模块56和第二配置模块58。
其中，调整模块56，用于在得到待分配服务器数量之后，在服务器集群上根据预设比例调整第一域名带宽；第二配置模块58，用于根据调整后的第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值，以使得根据调整后的阈值得到待分配服务器数量。
此处需要说明的是，上述调整模块56和第二配置模块58对应于实施例一中的步骤S206和步骤S208，两个模块与对应的步骤所实现的示例和应用场景相同，但不限于上述实施例一所公开的内容。需要说明的是，上述模块作为装置的一部分可以运行在实施例一提供的服务器中，可以通过软件实现，也可以通过硬件实现。
实施例3
根据本发明实施例的又一方面，还提供了一种存储介质，存储介质包括存储的程序，其中，在程序运行时控制存储介质所在设备执行：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；依据阈值和第二域名带宽的大小，得到待分配服务器数量；在服务器集群上根据预设比例调整第一域名带宽；根据调整后的第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值。
实施例4
根据本发明实施例的再一方面，还提供了一种处理器，处理器用于运行程序，其中，程序运行时执行：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；依据阈值和第二域名带宽的大小，得到待分配服务器数量；在服务器集群上根据预设比例调整第一域名带宽；根据调整后的第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值。
实施例5
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以用于保存上述实施例一所提供的服务器配置的方法所执行的程序代码。
可选地，在本实施例中，上述存储介质可以位于计算机网络中计算机终端群中的任意一个计算机终端中，或者位于移动终端群中的任意一个移动终端中。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值；依据阈值和第二域名带宽的大小，得到待分配服务器数量。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：在得到待分配服务器数量之后，在服务器集群上根据预设比例调整第一域名带宽；根据调整后的第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值，以使得根据调整后的阈值得到待分配服务器数量。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到第一域名带宽对应的阈值包括：从用户访问日志中获取任意域名的第一域名带宽，并获取服务器本地缓存命中率；根据第一域名带宽的数值变化与服务器本地缓存命中率的状态变化的对应关系，确定阈值。
进一步地，可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：从用户访问日志中获取任意域名的第一域名带宽，并获取服务器本地缓存命中率包括：依据预设周期从用户访问日志中获取任意域名的第一域名带宽，并获取服务器本地缓存命中率。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：根据第一域名带宽的数值变化与服务器本地缓存命中率的状态变化的对应关系，确定阈值包括：依据第一域名带宽的数值的变动与服务器本地缓存命中率的状态变化，将在第一域名带宽的数值为特定值的情况下，服务器本地缓存命中率不再提升或小幅提升时的特 定值确定为阈值。可选的，依据阈值和第二域名带宽的大小，得到待分配服务器数量包括：在第二域名带宽包括当前域名带宽的情况下，根据当前域名带宽与阈值，得到当前待分配服务器数量；其中，当前域名带宽通过流量采集设备实时获取。
进一步地，可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：根据当前域名带宽与阈值，得到当前待分配服务器数量包括：通过当前域名带宽除以阈值，得到当前待分配服务器数量。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：依据阈值和第二域名带宽的大小，得到待分配服务器数量包括：在第二域名带宽包括域名带宽预测值的情况下，根据域名带宽预测值与阈值，得到预测待分配服务器数量。
进一步地，可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：根据域名带宽预测值与阈值，得到预测待分配服务器数量包括：通过域名带宽预测值除以阈值，得到预测待分配服务器数量。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：第一域名带宽包括：服务器带宽；第一域名带宽包括：向供应商购买的带宽。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：在服务器集群上根据预设比例调整第一域名带宽包括：在服务器集群上根据预设比例放大或缩小第一域名带宽。
进一步地，可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：服务器集群包括：至少一台服务器。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
在本发明的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的技术内容，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个 网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述仅是本发明的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本发明的保护范围。

Claims (16)

  1. 一种服务器配置的方法，其特征在于，包括：
    根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到所述第一域名带宽对应的阈值；
    依据所述阈值和第二域名带宽的大小，得到待分配服务器数量。
  2. 根据权利要求1所述的服务器配置的方法，其特征在于，在得到待分配服务器数量之后，所述方法还包括：
    在服务器集群上根据预设比例调整所述第一域名带宽；
    根据调整后的所述第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值，以使得根据所述调整后的阈值得到待分配服务器数量。
  3. 根据权利要求1所述的服务器配置的方法，其特征在于，所述根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到所述第一域名带宽对应的阈值包括：
    从用户访问日志中获取任意域名的所述第一域名带宽，并获取所述服务器本地缓存命中率；
    根据所述第一域名带宽的数值变化与所述服务器本地缓存命中率的状态变化的对应关系，确定所述阈值。
  4. 根据权利要求3所述的服务器配置的方法，其特征在于，所述从用户访问日志中获取任意域名的所述第一域名带宽，并获取所述服务器本地缓存命中率包括：
    依据预设周期从用户访问日志中获取任意域名的所述第一域名带宽，并获取所述服务器本地缓存命中率。
  5. 根据权利要求3所述的服务器配置的方法，其特征在于，所述根据所述第一域名带宽的数值变化与所述服务器本地缓存命中率的状态变化的对应关系，确定所述阈值包括：
    依据所述第一域名带宽的数值的变动与所述服务器本地缓存命中率的状态变化，将在所述第一域名带宽的数值为特定值的情况下，所述服务器本地缓存命中率不再提升或小幅提升时的特定值确定为所述阈值。
  6. 根据权利要求1所述的服务器配置的方法，其特征在于，所述依据所述阈值和第二域名带宽的大小，得到待分配服务器数量包括：
    在所述第二域名带宽包括当前域名带宽的情况下，根据所述当前域名带宽与所述阈值，得到当前待分配服务器数量；
    其中，所述当前域名带宽通过流量采集设备实时获取。
  7. 根据权利要求6所述的服务器配置的方法，其特征在于，所述根据所述当前域名带宽与所述阈值，得到当前待分配服务器数量包括：
    通过所述当前域名带宽除以所述阈值，得到所述当前待分配服务器数量。
  8. 根据权利要求1所述的服务器配置的方法，其特征在于，所述依据所述阈值和第二域名带宽的大小，得到待分配服务器数量包括：
    在所述第二域名带宽包括域名带宽预测值的情况下，根据所述域名带宽预测值与所述阈值，得到预测待分配服务器数量。
  9. 根据权利要求8所述的服务器配置的方法，其特征在于，所述根据所述域名带宽预测值与所述阈值，得到预测待分配服务器数量包括：
    通过所述域名带宽预测值除以所述阈值，得到所述预测待分配服务器数量。
  10. 根据权利要求1所述的服务器配置的方法，其特征在于，所述第一域名带宽包括：服务器带宽；第二域名带宽包括：向供应商购买的带宽。
  11. 根据权利要求2所述的服务器配置的方法，其特征在于，所述在服务器集群上根据预设比例调整所述第一域名带宽包括：
    在所述服务器集群上根据预设比例放大或缩小所述第一域名带宽。
  12. 根据权利要求11所述的服务器配置的方法，其特征在于，所述服务器集群包括：至少一台服务器。
  13. 一种服务器配置的装置，其特征在于，包括：
    获取模块，用于根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到所述第一域名带宽对应的阈值；
    第一配置模块，用于依据所述阈值和第二域名带宽的大小，得到待分配服务器数量。
  14. 根据权利要求13所述的服务器配置的装置，其特征在于，所述服务器配置的装置还包括：
    调整模块，用于在得到待分配服务器数量之后，在服务器集群上根据预设比例调整所述第一域名带宽；
    第二配置模块，用于根据调整后的所述第一域名带宽和服务器本地缓存命中率的状态变化，得到调整后的阈值，以使得根据所述调整后的阈值得到待分配服务器数量。
  15. 一种存储介质，其特征在于，所述存储介质包括存储的程序，其中，在所述程序运行时控制所述存储介质所在设备执行：根据第一域名带宽和服务器本地缓存命中率进 行数据挖掘，得到所述第一域名带宽对应的阈值；依据所述阈值和第二域名带宽的大小，得到待分配服务器数量。
  16. 一种处理器，其特征在于，所述处理器用于运行程序，其中，所述程序运行时执行：根据第一域名带宽和服务器本地缓存命中率进行数据挖掘，得到所述第一域名带宽对应的阈值；依据所述阈值和第二域名带宽的大小，得到待分配服务器数量。
PCT/CN2019/083423 2018-04-25 2019-04-19 服务器配置的方法和装置 WO2019206033A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP19793601.6A EP3787231B1 (en) 2018-04-25 2019-04-19 Server configuration method and apparatus
JP2020559432A JP2021522583A (ja) 2018-04-25 2019-04-19 サーバー構成方法および装置
US17/079,231 US11431669B2 (en) 2018-04-25 2020-10-23 Server configuration method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810377843.1A CN110401553B (zh) 2018-04-25 2018-04-25 服务器配置的方法和装置
CN201810377843.1 2018-04-25

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/079,231 Continuation US11431669B2 (en) 2018-04-25 2020-10-23 Server configuration method and apparatus

Publications (1)

Publication Number Publication Date
WO2019206033A1 true WO2019206033A1 (zh) 2019-10-31

Family

ID=68294702

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/083423 WO2019206033A1 (zh) 2018-04-25 2019-04-19 服务器配置的方法和装置

Country Status (5)

Country Link
US (1) US11431669B2 (zh)
EP (1) EP3787231B1 (zh)
JP (1) JP2021522583A (zh)
CN (1) CN110401553B (zh)
WO (1) WO2019206033A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111327461B (zh) * 2020-01-23 2022-03-11 华为云计算技术有限公司 一种基于cdn系统的域名管理方法、装置、设备及介质
CN113364622A (zh) * 2021-06-04 2021-09-07 中国工商银行股份有限公司 一种跨区域流量控制的方法、装置、设备和存储介质
CN114465915A (zh) * 2021-12-22 2022-05-10 天翼云科技有限公司 一种cdn带宽预测方法、装置、系统和电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016074323A1 (zh) * 2014-11-11 2016-05-19 网宿科技股份有限公司 内容分发网络的http调度系统和方法
CN105872029A (zh) * 2016-03-28 2016-08-17 乐视控股（北京）有限公司 私有云对象存储的QoS的实现方法及系统
CN106034083A (zh) * 2015-03-12 2016-10-19 阿里巴巴集团控股有限公司 Cdn网络系统及其限速控制方法、cdn节点和服务器
CN107172126A (zh) * 2017-04-21 2017-09-15 华为技术有限公司 一种域名系统服务器分配方法及服务器

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7552235B2 (en) * 2003-12-11 2009-06-23 International Business Machines Corporation Autonomic selection of a request routing policy based upon cache effectiveness
US7925738B2 (en) * 2003-12-18 2011-04-12 Hewlett-Packard Development Company, L.P. Analytical cache performance model for a media server
US7584281B2 (en) 2005-06-07 2009-09-01 Datasynapse, Inc. Method for allocating shared computing infrastructure for application server-based deployments
US7761538B2 (en) 2006-08-30 2010-07-20 Microsoft Corporation Dynamically configuring, allocating and deploying computing systems
US7720936B2 (en) 2007-03-12 2010-05-18 Citrix Systems, Inc. Systems and methods of freshening and prefreshening a DNS cache
US8145761B2 (en) * 2008-03-03 2012-03-27 Microsoft Corporation Load skewing for power-aware server provisioning
CA2665397A1 (en) 2008-04-14 2009-10-14 Robert F. Cruickshank, Iii A method & apparatus for orchestrating utility power supply & demand in real time using a continuous pricing signal sent via a network to home networks & smart appliances
US8239482B2 (en) * 2008-11-13 2012-08-07 At&T Intellectual Property I, Lp System and method for selectively caching hot content in a content delivery system
US8694642B2 (en) 2010-10-21 2014-04-08 Opendns, Inc. Selective proxying in domain name systems
US9049244B2 (en) 2011-04-19 2015-06-02 Cloudflare, Inc. Registering for internet-based proxy services
US9354989B1 (en) * 2011-10-03 2016-05-31 Netapp, Inc Region based admission/eviction control in hybrid aggregates
CN102523231A (zh) * 2011-12-27 2012-06-27 北京蓝汛通信技术有限责任公司 一种基于dns解析的流量调度方法、装置及服务器
US8874790B2 (en) 2011-12-30 2014-10-28 Verisign, Inc. DNS package in a partitioned network
US9141669B2 (en) 2013-01-22 2015-09-22 Go Daddy Operating Company, LLC Configuring an origin server content delivery using a pulled data list
US9160809B2 (en) 2012-11-26 2015-10-13 Go Daddy Operating Company, LLC DNS overriding-based methods of accelerating content delivery
US10095978B2 (en) * 2013-01-05 2018-10-09 Microsoft Technology Licensing, Llc Monitor-mine-manage cycle
US9372825B1 (en) * 2013-02-27 2016-06-21 Netapp, Inc. Global non-volatile solid-state cache in a network storage system
US9213644B2 (en) * 2013-03-07 2015-12-15 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Allocating enclosure cache in a computing system
US9596299B2 (en) 2013-04-06 2017-03-14 Citrix Systems, Inc. Systems and methods for dynamically expanding load balancing pool
US20150074222A1 (en) * 2013-09-12 2015-03-12 Guanfeng Liang Method and apparatus for load balancing and dynamic scaling for low delay two-tier distributed cache storage system
US9354937B2 (en) * 2014-07-18 2016-05-31 Thomson Reuters Global Resources System and method for electronic work prediction and dynamically adjusting server resources
CN106921713B (zh) * 2015-12-25 2019-12-06 中国移动通信集团上海有限公司 一种资源缓存方法及装置
CN106027642A (zh) * 2016-05-19 2016-10-12 乐视控股（北京）有限公司 用于确定cdn节点磁盘数量的方法及系统
JP7011655B2 (ja) * 2017-05-16 2022-01-26 ソニーセミコンダクタソリューションズ株式会社 ストレージコントローラ、ストレージシステム、ストレージコントローラの制御方法およびプログラム
US11025710B1 (en) * 2020-10-26 2021-06-01 Verizon Digital Media Services Inc. Systems and methods for dynamic load balancing based on server utilization and content popularity

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016074323A1 (zh) * 2014-11-11 2016-05-19 网宿科技股份有限公司 内容分发网络的http调度系统和方法
CN106034083A (zh) * 2015-03-12 2016-10-19 阿里巴巴集团控股有限公司 Cdn网络系统及其限速控制方法、cdn节点和服务器
CN105872029A (zh) * 2016-03-28 2016-08-17 乐视控股（北京）有限公司 私有云对象存储的QoS的实现方法及系统
CN107172126A (zh) * 2017-04-21 2017-09-15 华为技术有限公司 一种域名系统服务器分配方法及服务器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3787231A4

Also Published As

Publication number Publication date
CN110401553A (zh) 2019-11-01
EP3787231A1 (en) 2021-03-03
EP3787231A4 (en) 2022-01-19
JP2021522583A (ja) 2021-08-30
EP3787231B1 (en) 2024-06-05
CN110401553B (zh) 2022-06-03
US11431669B2 (en) 2022-08-30
US20210044562A1 (en) 2021-02-11

Similar Documents

Publication Publication Date Title
US10455013B2 (en) Peer-to-peer upload scheduling
CN107124630B (zh) 节点数据管理的方法及装置
CN107251525B (zh) 用于支持移动设备用户的预测内容预取服务的分布式服务器架构
WO2019206033A1 (zh) 服务器配置的方法和装置
EP2832140B1 (en) Adaptive traffic management in cellular wireless networks
US9854282B2 (en) System and method for enabling network based rate determination for adaptive video streaming
US10289722B2 (en) System and methods for multi-level key-value store
CN103430169B (zh) 资产到用户设备的预取
US8787882B2 (en) Resource profile adjustment for pre-fetching of assets to user equipment
CN109982159B (zh) 在线播放流媒体的方法和终端
EP3072258B1 (en) Fractional pre-delivery of content to user devices
US10862992B2 (en) Resource cache management method and system and apparatus
JP2017509074A (ja) 動的キャッシュ割当およびネットワーク管理
CN106021126B (zh) 缓存数据处理方法及服务器、配置设备
US20200320154A1 (en) A webpage loading method, webpage loading system and server
CN107135411A (zh) 一种调整视频码率的方法及电子设备
CN103312716A (zh) 一种访问互联网信息的方法及系统
CN107251529B (zh) 用于在内容传输网络系统中的服务器之间传输和接收信息的方法和装置
US9769279B2 (en) Controlling the pre-delivery of content to a mobile device
US11671656B2 (en) Method for selecting resolution switching algorithm, computing device, and computer-program product
Silva et al. Content-aware prefetching in over-the-top wireless networks
CN107211189A (zh) 一种用于视频发送的方法与装置
KR102065662B1 (ko) 접속망 기반의 적응적인 데이터 서비스 제어 방법 및 그 장치
CN106156176B (zh) 一种数据清理方法及装置
CN115883910A (zh) 一种用于分片视频加速的渐进式弹性缓存方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19793601

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020559432

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019793601

Country of ref document: EP

Effective date: 20201125