Nothing Special   »   [go: up one dir, main page]

CN110098978B - DNS scheduling test method and device, network equipment and storage medium - Google Patents

DNS scheduling test method and device, network equipment and storage medium Download PDF

Info

Publication number
CN110098978B
CN110098978B CN201910295063.7A CN201910295063A CN110098978B CN 110098978 B CN110098978 B CN 110098978B CN 201910295063 A CN201910295063 A CN 201910295063A CN 110098978 B CN110098978 B CN 110098978B
Authority
CN
China
Prior art keywords
cache server
test
domain name
scheduling
bandwidth data
Prior art date
Legal status (The legal status 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 status listed.)
Expired - Fee Related
Application number
CN201910295063.7A
Other languages
Chinese (zh)
Other versions
CN110098978A (en
Inventor
韦贤韬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wangsu Science and Technology Co Ltd
Original Assignee
Wangsu Science and Technology Co Ltd
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 Wangsu Science and Technology Co Ltd filed Critical Wangsu Science and Technology Co Ltd
Priority to CN201910295063.7A priority Critical patent/CN110098978B/en
Publication of CN110098978A publication Critical patent/CN110098978A/en
Application granted granted Critical
Publication of CN110098978B publication Critical patent/CN110098978B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

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/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
    • 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/50—Testing arrangements
    • 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]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a DNS scheduling test method, a DNS scheduling test device and network equipment. The method comprises the following steps: acquiring current bandwidth data of the CDN; according to a test scene, adjusting the current bandwidth data into test bandwidth data under the test scene; the test scene is determined according to the test requirement of the DNS scheduling system to be tested; obtaining a scheduling result of the DNS scheduling system to be tested, wherein the scheduling result is determined by the DNS scheduling system to be tested according to the test bandwidth data in the test scene; and determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result so as to solve the problems that the testing period is long, the testing coverage rate cannot be guaranteed, the testing scene is not consistent with the actual scene and the like in the prior art.

Description

DNS scheduling test method and device, network equipment and storage medium
Technical Field
The invention relates to the technical field of software testing, in particular to a method and a device for testing DNS scheduling and network equipment.
Background
A Content Delivery Network (CDN) caches various Network contents through cache servers and distributes the cache servers to various regions, and when a client accesses the Network contents, the client directs the access of the client to the cache server closest to the client, thereby achieving Network acceleration. At present, more and more network resources are accelerated by using a CDN technology, and the user access speed is increased and the pressure of a source station is reduced by using a distance priority principle, a same operator priority principle and the like.
Due to the complexity of the network, the cache server may cause unavailable service or poor service quality due to various reasons such as network interruption, network fluctuation, and excessive load, which may affect the effect of CDN acceleration. At this time, in order to ensure the availability of CDN acceleration, the cache server needs to be scheduled: and (3) selecting an available cache server (hereinafter referred to as a replacement cache server) to replace a cache server (hereinafter referred to as a replacement cache server) with unavailable cache service. After being scheduled by a Domain Name Server (DNS), a request for accessing a CDN acceleration Domain Name and addressed to a replaced cache is gradually transferred to a replacement cache Server, that is, bandwidth is transferred from the replaced cache Server to the replacement cache Server. In order to guarantee QoS, it is necessary to ensure that the replacement cache server can bear the incremental bandwidth, and in order to avoid that frequent scheduling or wrong scheduling affects normal operation of the CDN, the scheduling needs to be tested in advance.
Because the current network scale is huge, the existing testing method is difficult to be applied to the actual network environment, and the testing effect is poor.
Disclosure of Invention
The embodiment of the invention provides a DNS scheduling test method, a DNS scheduling test device and network equipment, and aims to solve the problems that in the prior art, the test period is long, the test coverage rate cannot be guaranteed, and a test scene is not consistent with an actual scene.
The embodiment of the invention provides a DNS scheduling test method, which comprises the following steps:
acquiring current bandwidth data of the CDN;
according to a test scene, adjusting the current bandwidth data into test bandwidth data under the test scene; the test scene is determined according to the test requirement of the DNS scheduling system to be tested;
obtaining a scheduling result of the DNS scheduling system to be tested, wherein the scheduling result is determined by the DNS scheduling system to be tested according to the test bandwidth data;
and determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result.
By the method, a test scene is determined according to the test requirement of the DNS scheduling system to be tested, and the current bandwidth data is adjusted to be the test bandwidth data in the test scene according to the test scene; an expected test scene is actively constructed, the actual on-line operation scene is met, the test requirement can be met, the test period is short, and the effective test coverage rate can be achieved; and determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result, further determining the influence of scheduling on network bandwidth, and reducing the testing difficulty.
In one possible implementation, the CDN includes at least one node; the node comprises at least one cache server; the cache server is used for caching cache data corresponding to the accelerated domain name;
the acquiring of the current bandwidth data of the CDN includes:
the method comprises the steps of obtaining current bandwidth data of a cache server, current bandwidth data of a node to which the cache server belongs, and current bandwidth data occupied by a speed-up domain name on the cache server.
The required bandwidth data in the CDN is acquired according to the requirement of the test scene so as to further construct an expected test scene and carry out the test of DNS scheduling.
A possible implementation manner, where the adjusting the current bandwidth data to the test bandwidth data in the test scenario according to the test scenario includes:
if the test scene is specific to a cache server, determining a first adjustment amount of the cache server;
according to the first adjustment quantity, adjusting the current bandwidth data of the node to which the cache server belongs to obtain the test bandwidth data of the node to which the cache server belongs;
and adjusting the current bandwidth data of each accelerated domain name on the cache server according to the first adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server.
By the method, the test scene generated aiming at the node is realized, the difficulty in establishing the test scene can be reduced, the bandwidth amount of the generated test scene is closer to a real scene, and the test efficiency is improved.
A possible implementation manner, where the adjusting the current bandwidth data to the test bandwidth data in the test scenario according to the test scenario includes:
if the test scene is directed to the node, determining a second adjustment amount of the node;
adjusting the current bandwidth data of each cache server of the node according to the second adjustment amount to obtain the test bandwidth data of each cache server of the node;
and adjusting the current bandwidth data of each accelerated domain name on each cache server according to the second adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server of the node.
By the method, the test scene generated aiming at the node is realized, the difficulty in establishing the test scene can be reduced, the bandwidth amount of the generated test scene is closer to a real scene, and the test efficiency is improved.
A possible implementation manner, where the adjusting the bandwidth data of the CDN to the test bandwidth data in the test scenario according to the test scenario includes:
if the test scene is directed at an accelerated domain name, determining a third adjustment amount of the accelerated domain name;
according to the third adjustment quantity, adjusting the current bandwidth data of each cache server corresponding to the accelerated domain name to obtain the test bandwidth data of each cache server corresponding to the accelerated domain name;
and adjusting the current bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs according to the third adjustment amount to obtain the test bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs.
By the method, the test scene generated aiming at the accelerated domain name is realized, the difficulty in establishing the test scene can be reduced, the bandwidth amount of the generated test scene is closer to a real scene, and the test efficiency is improved.
In one possible implementation, the scheduling result includes: a scheduled cache server, a scheduled accelerated domain name;
the determining whether the DNS scheduling system to be tested meets the requirements according to the scheduling result comprises the following steps:
determining the dispatching bandwidth amount of the accelerated domain name according to the testing bandwidth data of the accelerated domain name and the cache server accelerated by the accelerated domain name before dispatching;
determining the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs according to the scheduling bandwidth amount of the accelerated domain name and the cache server accelerated by the domain name after scheduling;
and if the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs meet the bandwidth requirements of the cache server and the node, determining that the DNS scheduling system to be tested meets the requirements.
By accelerating the test bandwidth data and the scheduling result of the domain name, whether each cache server and each node meet the scheduling requirement after scheduling of the CDN to be tested is determined, the influence of the scheduling on the bandwidth can be directly determined, and the verifiable range of the test is widened.
The embodiment of the invention provides a testing device for DNS scheduling, which comprises:
the receiving and sending unit is used for acquiring the current bandwidth data of the CDN; obtaining a scheduling result of the DNS scheduling system to be tested, wherein the scheduling result is determined by the DNS scheduling system to be tested according to the test bandwidth data;
the processing unit is used for adjusting the current bandwidth data into test bandwidth data under the test scene according to the test scene; the test scene is determined according to the test requirement of the DNS scheduling system to be tested; and determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result.
In one possible implementation, the CDN includes at least one node; the node comprises at least one cache server; the cache server is used for caching cache data corresponding to the accelerated domain name;
the transceiver unit is specifically configured to: the method comprises the steps of obtaining current bandwidth data of a cache server, current bandwidth data of a node to which the cache server belongs, and current bandwidth data occupied by a speed-up domain name on the cache server.
In a possible implementation manner, the processing unit is specifically configured to:
if the test scene is specific to a cache server, determining a first adjustment amount of the cache server; according to the first adjustment quantity, adjusting the current bandwidth data of the node to which the cache server belongs to obtain the test bandwidth data of the node to which the cache server belongs; and adjusting the current bandwidth data of each accelerated domain name on the cache server according to the first adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server.
In a possible implementation manner, the processing unit is specifically configured to:
if the test scene is directed to the node, determining a second adjustment amount of the node; adjusting the current bandwidth data of each cache server of the node according to the second adjustment amount to obtain the test bandwidth data of each cache server of the node; and adjusting the current bandwidth data of each accelerated domain name on each cache server according to the second adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server of the node.
In a possible implementation manner, the processing unit is specifically configured to:
if the test scene is directed at an accelerated domain name, determining a third adjustment amount of the accelerated domain name; according to the third adjustment quantity, adjusting the current bandwidth data of each cache server corresponding to the accelerated domain name to obtain the test bandwidth data of each cache server corresponding to the accelerated domain name; and adjusting the current bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs according to the third adjustment amount to obtain the test bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs.
In one possible implementation, the scheduling result includes: a scheduled cache server, a scheduled accelerated domain name;
the processing unit is specifically configured to: determining the dispatching bandwidth amount of the accelerated domain name according to the testing bandwidth data of the accelerated domain name and the cache server accelerated by the accelerated domain name before dispatching; determining the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs according to the scheduling bandwidth amount of the accelerated domain name and the cache server accelerated by the domain name after scheduling; and if the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs meet the bandwidth requirements of the cache server and the node, determining that the DNS scheduling system to be tested meets the requirements.
The embodiment of the present application further provides a network device, where the network device has a function of implementing the above-described test method. This function may be implemented by hardware executing corresponding software, and in one possible design, the apparatus includes: a processor, a transceiver, a memory; the memory is used for storing computer execution instructions, the transceiver is used for realizing the communication between the device and other communication entities, the processor and the memory are connected through the bus, and when the device runs, the processor executes the computer execution instructions stored by the memory so as to enable the device to execute the test method described above.
Embodiments of the present invention also provide a computer storage medium, in which a software program is stored, and the software program, when being read and executed by one or more processors, implements the testing method described in the above various possible implementation manners.
Embodiments of the present invention also provide a computer program product containing instructions, which when run on a computer, cause the computer to perform the testing method described in the above various possible implementations.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that are required to be used in the description of the embodiments will be briefly described below.
FIG. 1 is a diagram of a system architecture suitable for use with an embodiment of the present invention;
fig. 2 is a schematic diagram of an architecture of a CDN according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a DNS scheduling test method according to an embodiment of the present invention;
fig. 4 is a schematic flow chart corresponding to a testing method according to another embodiment of the present invention;
fig. 5 is a schematic flow chart corresponding to a testing method according to another embodiment of the present invention;
fig. 6 is a schematic flow chart corresponding to a testing method according to another embodiment of the present invention;
fig. 7 is a schematic scheduling diagram corresponding to a testing method according to another embodiment of the present invention;
fig. 8 is a schematic flow chart corresponding to a testing method according to another embodiment of the present invention;
fig. 9 is a schematic scheduling diagram corresponding to a testing method according to another embodiment of the present invention;
fig. 10 is a schematic structural diagram of a testing apparatus according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram corresponding to a network device according to an embodiment of the present invention.
Detailed Description
The present application will be described in detail below with reference to the accompanying drawings, and the specific operation methods in the method embodiments can also be applied to the apparatus embodiments.
Fig. 1 exemplarily shows a system architecture to which the DNS scheduling test method according to the embodiment of the present invention is applied, where the system architecture may include a DNS scheduling system 101, a test system 102, and a CDN 103.
Referring to fig. 1, as shown in fig. 2, the CDN103 includes at least one node; the node comprises at least one cache server; the cache server is used for caching cache data corresponding to the accelerated domain name; taking FIG. 2 as an example, node 1 includes cache server 211-.
CDN103 may also include a DNS server; the DNS server is composed of a domain name resolver and a domain name server. The domain name server is a server which stores domain names and corresponding IP addresses of all hosts in the network and has a function of converting the domain names into the IP addresses. The process of mapping a domain name to an IP address is known as "domain name resolution". After a user sends an access request to the CDN, the DNS server performs global load balancing DNS analysis on the accelerated domain name in the access request, and the global load balancing DNS analysis is used for determining the IP address of the CDN cache server. For example, the corresponding IP address is resolved from the geographical location information. The accelerated domain name may be understood as a domain name accelerated by a customer domain name in a public network access CDN, for example, the original domain name "www.xxxx.com." has an accelerated domain name "www.xxxx.com.lxdns.com." in the public network. The CDN plans different client acceleration domains according to different acceleration types, where the client acceleration types may include on-demand acceleration, web acceleration, live acceleration, and the like, and accordingly, the acceleration domains may also be classified into on-demand acceleration, web acceleration, live acceleration, and the like. The CDN may plan different acceleration domain names according to different acceleration types for different network resources, and different acceleration domain names may plan different CDN cache server resources to provide different acceleration services.
After the IP address of the cache server is obtained, an access request is sent to the corresponding cache server; the cache server obtains an IP address of the domain name through DNS analysis of the cache server according to the domain name to be accessed provided by the browser, and then the cache server submits an access request to the IP address; after obtaining the content from the IP address, the cache server stores the content locally for later use on the one hand, and returns the obtained data to the client on the other hand to complete the data service process; the client end obtains the data returned by the cache server and displays the data and completes the whole browsing data request process.
As shown in fig. 2, in the CDN103, a predetermined bandwidth is allocated in the cache server 211 and the cache server 222 to cache data of the accelerated domain name a. The cache server 223 and the cache server 233 are allocated with a predetermined bandwidth for caching the data of the accelerated domain name B.
Due to the complexity of the network, the cache server may cause unavailable service or poor service quality due to various reasons such as network interruption, network fluctuation, and excessive load, which may affect the effect of CDN acceleration. The DNS scheduling system 101 is used for resource scheduling in the CDN, and when it is determined that an access abnormality occurs to an IP address of a certain cache server, for example, when it is determined that a cache server in the CDN is highly loaded or unavailable, the scheduling system 101 may correspondingly allocate the accelerated domain name to the CDN103Such that the CDN may initiate a normal response through the cache server closest to the customer and serving access is normal. After DNS scheduling, requests to the replaced cache generated by accessing the CDN accelerated domain name will gradually be transferred to the replacement cache, i.e., bandwidth is transferred from the replaced cache to the replacement cache. To ensure QOS, it is necessary to ensure that the replacement buffer can carry the portion of the incremental bandwidth BwAddNamely, it is required to satisfy:
1) replacement of the bandwidth cap Bw of a cache serverMax-replacing the current bandwidth of the cache server BwNow>BwAdd；
2) Bandwidth upper limit NodeBw for replacing node where cache server is locatedMax-replacing the current bandwidth nodebnown of the node where the cache server is located>BwAdd。
In the prior art, as BwMaxAnd BwNow, NodeBwNow, NodeBwMaxThe method has service relevance with NodeBwNow, and the feasibility of artificially constructing million-level bandwidth data as test input is not high; only part of bandwidth data is constructed, and incomplete test coverage rate cannot be caused if the data cannot be evaluated completely; the actual bandwidth is continuously fluctuated, the constructed data is relatively fixed and does not accord with the actual scene, and the test accuracy is low.
If the bandwidth of the online operation environment is directly used as test data, due to the fact that an expected test scene cannot be actively constructed, when the problems that a cache server is high in load or unavailable and the like occur in the online operation environment and a user needs to access the corresponding cache server, DNS scheduling can be triggered, the test period is long, the test coverage rate is low, and the test requirement cannot be met.
In addition, for the DNS scheduling system to be tested online, because the scheduling result of the test environment does not really take effect, the bandwidth data operated on line is directly used, the bandwidth cannot be transferred from the replaced cache to the replacement cache, and for the situations such as the cache load is too high and the node load is too high, the DNS scheduling can be continuously performed by the DNS system operated on line because the load is not reduced, so that the scheduling result of the test environment is not consistent with the actual situation, and it cannot be determined whether the scheduling of the DNS scheduling system to be tested online meets the requirement.
The test system 102 is configured to monitor bandwidth data in the CDN and interact with the DNS scheduling system, so as to test the DNS scheduling system 101.
Based on the above problem, an embodiment of the present invention provides a method for testing DNS scheduling, as shown in fig. 3, where the method includes:
step 301: acquiring current bandwidth data of the CDN;
step 302: according to a test scene, adjusting the current bandwidth data into test bandwidth data under the test scene;
the test scene is determined according to the test requirement of the DNS scheduling system to be tested. The DNS scheduling system 101 to be tested in the embodiment of the present invention may be an online running DNS scheduling system, or may also be a DNS scheduling system to be tested, which needs to be tested and is to be online, and may be determined according to actual test requirements, which is not limited herein. The test scenario may be one or more of cache server high load or unavailable, node high load or unavailable, accelerated domain name high load or unavailable, and the like.
Step 303: obtaining a scheduling result of the DNS scheduling system to be tested, wherein the scheduling result is determined by the DNS scheduling system to be tested according to the test bandwidth data;
step 304: and determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result.
By the method, a test scene is determined according to the test requirement of the DNS scheduling system to be tested, and the current bandwidth data is adjusted to be the test bandwidth data in the test scene according to the test scene; an expected test scene is actively constructed, the actual on-line operation scene is met, the test requirement can be met, the test period is short, and the effective test coverage rate can be achieved; and determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result, further determining the influence of scheduling on network bandwidth, and reducing the testing difficulty.
In order to better meet the requirement of the test scenario, the required bandwidth data in the CDN is acquired to further construct an expected test scenario for DNS scheduling test. The acquiring of the current bandwidth data of the CDN includes: the method comprises the steps of obtaining current bandwidth data of a cache server, current bandwidth data of a node to which the cache server belongs, and current bandwidth data occupied by a speed-up domain name on the cache server.
In a specific implementation process, the test system may obtain bandwidth data of the CDN in real time, and may update the current bandwidth data according to a set time period.
In step 302, the bandwidth adjustment mode according to the test scenario may be pre-stored in a configuration file, and after obtaining the bandwidth data of the CDN, the test system reads the corresponding configuration file according to the test requirement to perform bandwidth adjustment. The configuration of bandwidth adjustment may be multidimensional, and in the embodiment of the present invention, bandwidth adjustment may be performed on one or more items of a cache server, a node to which the cache server belongs, and an acceleration domain name.
The embodiment of the present invention provides a test scenario for adjusting a cache server, for example, in the test scenario, if the cache server 211 is in a high load, a first adjustment amount N that the cache server 211 exceeds a bandwidth threshold of the high load needs to be determined according to a test scenario of the high load and according to current bandwidth data of the cache server 211.
As shown in fig. 4, adjusting the current bandwidth data to the test bandwidth data in the test scenario specifically includes:
step 401: if the test scene is specific to the cache server, determining a first adjustment amount of the cache server;
in particular implementations, the amount of adjustment of the bandwidth of the cache server may be adjusted based on a scaling and/or based on a specified value. In connection with the above example, taking the determination of the first adjustment amount based on the specified value Bw as an example: if it is determined that the current bandwidth BwNow of the cache server 211 is 100M and the bandwidth threshold Bw of the high load that needs to be scheduled is 200M, the first adjustment amount N may be determined as Bw-BwNow being 100M. The method of determining the first adjustment amount N based on the proportional Rate1 may be: the first adjustment amount N is (Rate1-1) × BwNow.
At this time, the test bandwidth data of the cache server is the current bandwidth data of the cache server plus the first adjustment amount N.
For another example, for a cache server failure scenario, if it is determined that the cache server 232 fails, the first adjustment amount N of the cache server 232 is determined to be the current bandwidth amount of the cache server 232; for example, the current bandwidth amount of the cache server 232 is 200M, in a fault scenario, the bandwidth of the cache server 232 needs to be reduced to 0, and the first adjustment amount N is 200M.
Step 402: according to the first adjustment quantity, adjusting the current bandwidth data of the node to which the cache server belongs to obtain the test bandwidth data of the node to which the cache server belongs;
in a specific embodiment, the test bandwidth data Node of the Node to which the cache server belongs may be equal to the current bandwidth data Node now of the Node plus the first adjustment amount N.
403, the step of: and adjusting the current bandwidth data of each accelerated domain name on the cache server according to the first adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server.
If it is assumed that the network bandwidth occupied by the accelerated domain names on each cache server is the same, the first adjustment amount N may be equally allocated to each accelerated domain name on the cache server to determine the test bandwidth data of each accelerated domain name.
In a specific embodiment, the adjustment can be performed by traversing each accelerated domain name, and the specific formula is as follows:
Bwi，j＝BwNowi，j+N/D
wherein, Bwi，jTo speed up the testing of bandwidth data on cache server j for domain name i, BwNowi，jAccelerating the current bandwidth data of the domain name i on the cache server j; i is less than or equal to D; d is the number of the accelerated domain names on the cache server j.
Certainly, the bandwidth allocation condition of each acceleration domain name on the cache server can be determined according to an actual scene, the weight of the bandwidth allocation of each acceleration domain name on the cache server is determined, and the first adjustment amount N is allocated to each acceleration domain name on the cache server according to the weight, so that the bandwidth adjustment of each acceleration domain name is realized.
By the method, the test scene generated aiming at the node is realized, the difficulty in establishing the test scene can be reduced, the bandwidth amount of the generated test scene is closer to a real scene, and the test efficiency is improved.
As shown in fig. 5, the adjusting the current bandwidth data to the test bandwidth data in the test scenario according to the test scenario includes:
step 501: if the test scene is directed to the node, determining a second adjustment amount of the node;
for example, in the test scenario, if the node 1 has a high load, the second adjustment amount NodeBw by which the node 1 exceeds the bandwidth threshold of the high load needs to be determined according to the current bandwidth data of the node 1 and the test scenario of the high load. In particular implementations, the amount of adjustment of the bandwidth of the node may be adjusted based on a scaling adjustment and/or based on a specified value. For example, taking the example of determining the second adjustment amount based on the specified value NodeBw 1: if it is determined that the current bandwidth nodebnown of the node 1 is 800M and the bandwidth threshold NodeBw1 of the high load that needs to be scheduled is 1000M, the second adjustment amount NodeBw may be determined as NodeBw 1-nodebnown — 200M. The method for determining the second adjustment amount NodeBw based on the proportional Rate2 may be: the second adjustment amount NodeBw is (Rate2-1) × nodebnow.
At this time, the test bandwidth data of the node is the current bandwidth data of the node plus the second adjustment amount NodeBw.
Step 502: adjusting the current bandwidth data of each cache server of the node according to the second adjustment amount to obtain the test bandwidth data of each cache server of the node;
in a specific embodiment, the second adjustment amount may be evenly distributed to the cache servers under the node, that is, the bandwidth adjustment amount NodeBw/C of each cache server under the node, where C is the number of cache servers under the node; test bandwidth data of each cache server of node k:
Bwn＝BwNown+NodeBw/C
wherein, BwnFor caching test bandwidth data of server n in node k, BwNownCurrent bandwidth data of a cache server n in a node k; n is less than or equal to C; c is the number of cache servers in node k.
Of course, the weight of bandwidth adjustment of the cache servers under the node may also be determined according to the needs of the test scenario, so as to determine the bandwidth adjustment amount of each cache server under the node.
Step 503: and adjusting the current bandwidth data of each accelerated domain name on each cache server of the node according to the second adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server of the node.
If it is assumed that the network bandwidths occupied by the accelerated domain names on each cache server are the same, the second adjustment amount NodeBw may be equally distributed to each accelerated domain name on the node to determine the test bandwidth data of each accelerated domain name.
In a specific embodiment, the bandwidth adjustment of each accelerated domain name can be realized by traversing each cache server under the node and each accelerated domain name accelerated by the cache server, and the specific formula is as follows:
NodeBwn，m＝Node BwNown，m+NodeBw/(C1*D1)
wherein, NodeBwn，mTo speed up the testing of bandwidth data of domain name m on cache server n, NodeBwNown，mAccelerating the current bandwidth data of the domain name m on the cache server n; m is less than or equal to C1; d1 is the number of the speed-up domain names on the cache server n; c1 is the number of cache servers on node k.
Of course, the bandwidth allocation condition of each acceleration domain name on the cache server may also be determined according to an actual scene, and the weight of the bandwidth allocation of each acceleration domain name on the cache server is determined, so that the second adjustment amount is allocated to each acceleration domain name on the cache server according to the weight, so as to implement bandwidth adjustment on each acceleration domain name.
By the method, the test scene generated aiming at the node is realized, the difficulty in establishing the test scene can be reduced, the bandwidth amount of the generated test scene is closer to a real scene, and the test efficiency is improved.
As shown in fig. 6, the adjusting, according to a test scenario, the bandwidth data of the CDN to the test bandwidth data in the test scenario includes:
step 601: if the test scene is directed at the accelerated domain name, determining a third adjustment amount of the accelerated domain name;
for example, in the test scenario, if the accelerated domain name a is accessed with a high load, the third adjustment amount DomainBw by which the accelerated domain name a exceeds the bandwidth threshold of the high load needs to be determined according to the current bandwidth data of the accelerated domain name a and the test scenario of the high load. In particular implementations, the amount of adjustment to speed up the bandwidth of the domain name can be adjusted based on a scaling and/or based on a specified value. For example, taking the determination of the third adjustment amount based on the specified value DomainBw1 as an example: if it is determined that the current bandwidth DomainBwNow of the speed-up domain name a is 400M and the bandwidth threshold value DomainBw1 of the high load required to be scheduled is 700M, the third adjustment amount DomainBw may be determined as DomainBw1-DomainBwNow being 300M. The method for determining the third adjustment amount DomainBw based on the Rate3 may be: the third adjustment amount DomainBw is (Rate3-1) × DomainBwNow.
At this time, the test bandwidth data of the accelerated domain name is the current bandwidth data of the accelerated domain name plus the third adjustment amount DomainBw.
Step 602: according to the third adjustment quantity, adjusting the current bandwidth data of each cache server corresponding to the accelerated domain name to obtain the test bandwidth data of each cache server corresponding to the accelerated domain name;
if it is assumed that the network bandwidth occupied by the accelerated domain name on each cache server is the same, the third adjustment amount DomainBw may be equally distributed to each cache server of the accelerated domain name to determine the test bandwidth data of each cache server.
In a specific embodiment, bandwidth adjustment of each cache server and node can be realized by traversing each cache server corresponding to the accelerated domain name, and the specific formula is as follows:
DomainBwl，g＝DomainBwNowl，g+DomainBw/(C2)
wherein, DomainBwl，gTo speed up the testing of bandwidth data on the cache server g for domain name l, DomainBwNowl，gCurrent bandwidth data on the cache server g for the acceleration domain l; g is less than or equal to C2; c2 is the number of cache servers that accelerate the domain name l.
Of course, the bandwidth allocation condition of each acceleration domain name on the cache server may also be determined according to an actual scenario, and the weight of the bandwidth allocation of each acceleration domain name on the cache server is determined, so that the third adjustment amount is allocated to each cache server according to the weight.
Step 603: and adjusting the current bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs according to the third adjustment amount to obtain the test bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs.
In a specific embodiment, the bandwidth adjustment of the node can be realized by traversing the node corresponding to each cache server corresponding to the accelerated domain name; the adjustment amount of the real-time bandwidth of the node where the corresponding node cache server is located may be DomainBw/(C2), or may also be determined according to an actual scene, a bandwidth allocation condition of each acceleration domain name on the cache server is determined, a weight of the bandwidth allocation of each acceleration domain name on the cache server is determined, and thus the adjustment amount of the real-time bandwidth of the node is determined.
By the method, the test scene generated aiming at the accelerated domain name is realized, the difficulty in establishing the test scene can be reduced, the bandwidth amount of the generated test scene is closer to a real scene, and the test efficiency is improved.
It should be noted that, because the bandwidth cannot be adjusted to be less than 0, if the adjusted test bandwidth data of the cache server or the node is less than 0, it is prompted that the test bandwidth data is set unreasonably, so as to reconfigure the test scenario.
And sending the adjusted bandwidth to a DNS scheduling system. In one possible implementation, the scheduling result includes: a scheduled acceleration domain name, a scheduled cache server. Specifically, if the scheduled cache server includes a replaced cache server and a replacement cache server, the scheduling result may include the accelerated domain name, and the replaced cache server and the replacement cache server corresponding to the accelerated domain name.
For example, as shown in fig. 7, the cache servers that accelerate domain name a before scheduling are cache server 211 and cache server 222, and the scheduling result is that the bandwidth of accelerated domain name a in cache server 211 is scheduled to cache server 231.
As shown in fig. 8, in a possible implementation manner, the method for determining whether the DNS scheduling system to be tested meets the requirement according to the scheduling result may include:
step 801: determining the dispatching bandwidth amount of the accelerated domain name according to the testing bandwidth data of the accelerated domain name and the cache server accelerated by the accelerated domain name before dispatching;
referring to fig. 7, if the scheduling result is determined to be that the bandwidth of the speed-up domain name a in the cache server 211 is scheduled to the cache server 231. At this time, the scheduling bandwidth amount of the accelerated domain name a is the testing bandwidth amount of the accelerated domain name.
Step 802: determining the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs according to the scheduling bandwidth amount of the accelerated domain name and the cache server accelerated by the domain name after scheduling;
in a specific embodiment, the bandwidth adjustment amount of the CDN may be determined according to an actual scheduling process, that is, the bandwidth of the replaced cache server is decreased, and the bandwidth of the replaced cache server is increased.
Specifically, the method may include:
step one, traversing each cache server list of the accelerated domain name A before scheduling, and removing the bandwidth of the accelerated domain name A on each cache server;
for example, if it is determined that there is no replacement cache server in the scheduling result, the scheduling is performedPost-degree cache server list L for accelerating domain name accelerationafterCache server list L for accelerated domain name acceleration before schedulingbefore-a replaced cache server; if the cache server with replacement exists in the scheduling result, the scheduled cache server list L for accelerating the domain name accelerationafterCache server list L for accelerated domain name acceleration before schedulingbefore-replaced cache server + replaced cache server.
For example, it is determined that the test bandwidth data for accelerating domain name a is DomainBwA, and the bandwidth reduction amount of cache server n responsible for accelerating domain name a is DomainBwA/Cbefore，CbeforeBefore scheduling, the method is responsible for accelerating the number of corresponding cache servers of the domain name A;
after DNS scheduling, the bandwidth increment of the cache server m in charge of accelerating the domain name A is DomainBw/Cafter，CafterIs the number of cache servers after scheduling; if a cache server accelerates the acceleration domain name before and after scheduling, the bandwidth adjustment amount of the cache server is DomainBw/Cafter-DomainBw/Cbefore。
Step 803: and if the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs meet the bandwidth requirements of the cache server and the node, determining that the DNS scheduling system to be tested meets the requirements.
For example, if it is determined that the bandwidth amount of the node decreases, it is smaller than the bandwidth upper limit of the high load of the node; if the bandwidth amount of the cache server is determined to be reduced, the bandwidth amount is smaller than the high-load bandwidth upper limit of the cache server; it is determined that re-scheduling is not required.
In one possible implementation, since the bandwidth transfer is gradually effective, it may be assumed that the bandwidth transfer process is linear, and assuming that the time of full effectiveness is T, as shown in fig. 9, the real-time bandwidth scheduling amount of the cache server is:
1) bandwidth scheduling amount ((current time-schedule time)/T) current time-schedule time < T
2) The bandwidth scheduling amount is current time-scheduling time > -T
By accelerating the test bandwidth data and the scheduling result of the domain name, whether each cache server and each node of the CDN to be tested meet the scheduling requirement or not can be determined in the scheduling process, the influence of the scheduling on the bandwidth can be directly determined, the verifiable range of the test is widened, and the DNS scheduling is favorably and pointedly improved.
By accelerating the test bandwidth data and the scheduling result of the domain name, whether each cache server and each node meet the scheduling requirement after scheduling of the CDN to be tested is determined, the influence of the scheduling on the bandwidth can be directly determined, and the verifiable range of the test is widened.
In the embodiment of the invention, the online operation environment can be directly accessed to obtain the real-time bandwidth data of the CDN, and the bandwidth data of the CDN is adjusted in the test system according to the test requirement, so that the method not only fits the actual application scene, but also can meet the test requirement and improve the test efficiency. In addition, the scheduling result of the DNS scheduling test environment can be acted on the traffic bandwidth, so that the scheduling bandwidth amount triggered by overhigh load can be closer to the scheduling requirement of the scheduling system on one hand, and the influence condition of the scheduling on the bandwidth can be observed on the other hand. The rationality of the scheduling algorithm can be verified before the new DNS scheduling function comes online.
Based on the same inventive concept, as shown in fig. 10, an embodiment of the present invention provides a DNS scheduling test apparatus, where the apparatus includes:
a transceiving unit 1001, configured to acquire current bandwidth data of the CDN; obtaining a scheduling result of the DNS scheduling system to be tested, wherein the scheduling result is determined by the DNS scheduling system to be tested according to the test bandwidth data;
the processing unit 1002 is configured to adjust the current bandwidth data to test bandwidth data in a test scenario according to the test scenario; the test scene is determined according to the test requirement of the DNS scheduling system to be tested; and determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result.
In one possible implementation, the CDN includes at least one node; the node comprises at least one cache server; the cache server is used for caching cache data corresponding to the accelerated domain name;
the transceiving unit 1001 is specifically configured to: the method comprises the steps of obtaining current bandwidth data of a cache server, current bandwidth data of a node to which the cache server belongs, and current bandwidth data occupied by a speed-up domain name on the cache server.
In a possible implementation manner, the processing unit 1002 is specifically configured to:
if the test scene is specific to a cache server, determining a first adjustment amount of the cache server; according to the first adjustment quantity, adjusting the current bandwidth data of the node to which the cache server belongs to obtain the test bandwidth data of the node to which the cache server belongs; and adjusting the current bandwidth data of each accelerated domain name on the cache server according to the first adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server.
In a possible implementation manner, the processing unit 1002 is specifically configured to:
if the test scene is directed to the node, determining a second adjustment amount of the node; adjusting the current bandwidth data of each cache server of the node according to the second adjustment amount to obtain the test bandwidth data of each cache server of the node; and adjusting the current bandwidth data of each accelerated domain name on each cache server according to the second adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server of the node.
In a possible implementation manner, the processing unit 1002 is specifically configured to:
if the test scene is directed at an accelerated domain name, determining a third adjustment amount of the accelerated domain name; according to the third adjustment quantity, adjusting the current bandwidth data of each cache server corresponding to the accelerated domain name to obtain the test bandwidth data of each cache server corresponding to the accelerated domain name; and adjusting the current bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs according to the third adjustment amount to obtain the test bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs.
In one possible implementation, the scheduling result includes: a scheduled cache server, a scheduled accelerated domain name;
the processing unit 1002 is specifically configured to: determining the dispatching bandwidth amount of the accelerated domain name according to the testing bandwidth data of the accelerated domain name and the cache server accelerated by the accelerated domain name before dispatching; determining the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs according to the scheduling bandwidth amount of the accelerated domain name and the cache server accelerated by the domain name after scheduling; and if the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs meet the bandwidth requirements of the cache server and the node, determining that the DNS scheduling system to be tested meets the requirements.
Fig. 11 is a schematic structural diagram of a network device provided in an embodiment of the present application, and as shown in fig. 11, the network device 1100 includes a processor 1110, a memory 1120, and a communication interface 1130. Optionally, the network device 600 also includes an input device 640, an output device 650, and a bus 660. The processor 1110, the memory 1120, and the communication interface 1130 are connected to each other via a bus 550. The memory 1120 stores instructions or programs therein, and the processor 1110 is configured to execute the instructions or programs stored in the memory 1120. When the instructions or programs stored in the memory 1120 are executed, the processor 1110 is configured to perform the operations performed by the processing unit 1020 in the above-described method embodiments, and the communication interface 1130 is configured to perform the operations performed by the transceiver unit 510 in the above-described embodiments.
It should be noted that the network device 1100 provided in the embodiment of the present application may correspond to a network device that executes any method provided in the embodiment of the present invention, and operations and/or functions of each module in the network device 1100 are respectively for implementing corresponding flows of the methods shown in fig. 2 to fig. 9, and are not described herein again for brevity.
It should be understood that the processor mentioned in the embodiments of the present application may be a Central Processing Unit (CPU), and may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will also be appreciated that the memory referred to in the embodiments of the application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (memory module) is integrated in the processor.
It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of the processes should be determined by their functions and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
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 will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (14)

1. A DNS scheduled test method is characterized by comprising the following steps:
acquiring current bandwidth data of a Content Delivery Network (CDN);
according to a test scene, adjusting the current bandwidth data into test bandwidth data under the test scene; the test scene is determined according to the test requirement of the DNS scheduling system to be tested;
obtaining a scheduling result of the DNS scheduling system to be tested, wherein the scheduling result is determined by the DNS scheduling system to be tested according to the test bandwidth data in the test scene;
determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result; the scheduling result comprises: a scheduled cache server; and if the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs meet the bandwidth requirements of the cache server and the node, determining that the DNS scheduling system to be tested meets the requirements.
2. The method of claim 1, wherein the CDN comprises at least one node; the node comprises at least one cache server; the cache server is used for caching cache data corresponding to the accelerated domain name;
the obtaining of the current bandwidth data of the CDN includes one or more of:
the method comprises the steps of obtaining current bandwidth data of a cache server, current bandwidth data of a node to which the cache server belongs, and current bandwidth data occupied by a speed-up domain name on the cache server.
3. The method of claim 2, wherein the adjusting the current bandwidth data to the test bandwidth data in the test scenario comprises:
if the test scene is specific to a cache server, determining a first adjustment amount of the cache server;
according to the first adjustment quantity, adjusting the current bandwidth data of the node to which the cache server belongs to obtain the test bandwidth data of the node to which the cache server belongs;
and adjusting the current bandwidth data of each accelerated domain name on the cache server according to the first adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server.
4. The method of claim 2, wherein the adjusting the current bandwidth data to the test bandwidth data under the test scenario according to the test scenario comprises:
if the test scene is directed to the node, determining a second adjustment amount of the node;
adjusting the current bandwidth data of each cache server of the node according to the second adjustment amount to obtain the test bandwidth data of each cache server of the node;
and adjusting the current bandwidth data of each accelerated domain name on each cache server according to the second adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server of the node.
5. The method of claim 2, wherein the adjusting the bandwidth data of the CDN to the test bandwidth data under the test scenario according to the test scenario includes:
if the test scene is directed at an accelerated domain name, determining a third adjustment amount of the accelerated domain name;
according to the third adjustment quantity, adjusting the current bandwidth data of each cache server corresponding to the accelerated domain name to obtain the test bandwidth data of each cache server corresponding to the accelerated domain name;
and adjusting the current bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs according to the third adjustment amount to obtain the test bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs.
6. The method of claim 2, wherein the scheduling result comprises: a scheduled acceleration domain name;
the determining the bandwidth scheduling amount of the cache server and the bandwidth scheduling amount of the node to which the cache server belongs after scheduling according to the scheduling result includes:
determining the dispatching bandwidth amount of the accelerated domain name according to the testing bandwidth data of the accelerated domain name and the cache server accelerated by the accelerated domain name before dispatching;
and determining the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs according to the scheduling bandwidth amount of the accelerated domain name and the cache server accelerated by the domain name after scheduling.
7. A DNS-scheduled testing apparatus, the apparatus comprising:
the receiving and sending unit is used for acquiring the current bandwidth data of the CDN; obtaining a scheduling result of the DNS scheduling system to be tested, wherein the scheduling result is determined by the DNS scheduling system to be tested according to the test bandwidth data in the test scene;
the processing unit is used for adjusting the current bandwidth data into test bandwidth data under the test scene according to the test scene; the test scene is determined according to the test requirement of the DNS scheduling system to be tested; determining whether the DNS scheduling system to be tested meets the requirements or not according to the scheduling result; the scheduling result comprises: a scheduled cache server; and if the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs meet the bandwidth requirements of the cache server and the node, determining that the DNS scheduling system to be tested meets the requirements.
8. The apparatus of claim 7, wherein the CDN comprises at least one node; the node comprises at least one cache server; the cache server is used for caching cache data corresponding to the accelerated domain name;
the transceiver unit is specifically configured to: the method comprises the steps of obtaining current bandwidth data of a cache server, current bandwidth data of a node to which the cache server belongs, and current bandwidth data occupied by a speed-up domain name on the cache server.
9. The apparatus as claimed in claim 8, wherein said processing unit is specifically configured to:
if the test scene is specific to a cache server, determining a first adjustment amount of the cache server; according to the first adjustment quantity, adjusting the current bandwidth data of the node to which the cache server belongs to obtain the test bandwidth data of the node to which the cache server belongs; and adjusting the current bandwidth data of each accelerated domain name on the cache server according to the first adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server.
10. The apparatus as claimed in claim 8, wherein said processing unit is specifically configured to:
if the test scene is directed to the node, determining a second adjustment amount of the node; adjusting the current bandwidth data of each cache server of the node according to the second adjustment amount to obtain the test bandwidth data of each cache server of the node; and adjusting the current bandwidth data of each accelerated domain name on each cache server according to the second adjustment amount to obtain the test bandwidth data of each accelerated domain name on the cache server of the node.
11. The apparatus as claimed in claim 8, wherein said processing unit is specifically configured to:
if the test scene is directed at an accelerated domain name, determining a third adjustment amount of the accelerated domain name; according to the third adjustment quantity, adjusting the current bandwidth data of each cache server corresponding to the accelerated domain name to obtain the test bandwidth data of each cache server corresponding to the accelerated domain name; and adjusting the current bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs according to the third adjustment amount to obtain the test bandwidth data of the node to which each cache server corresponding to the accelerated domain name belongs.
12. The apparatus of claim 8, wherein the scheduling result comprises: a scheduled acceleration domain name;
the processing unit is specifically configured to: determining the dispatching bandwidth amount of the accelerated domain name according to the testing bandwidth data of the accelerated domain name and the cache server accelerated by the accelerated domain name before dispatching; and determining the bandwidth scheduling amount of the cache server after scheduling and the bandwidth scheduling amount of the node to which the cache server belongs according to the scheduling bandwidth amount of the accelerated domain name and the cache server accelerated by the domain name after scheduling.
13. A network device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the DNS scheduled testing method according to any of claims 1-6 when executing the program.
14. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps in the DNS scheduled testing method according to any one of the claims 1-6.
CN201910295063.7A 2019-04-12 2019-04-12 DNS scheduling test method and device, network equipment and storage medium Expired - Fee Related CN110098978B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910295063.7A CN110098978B (en) 2019-04-12 2019-04-12 DNS scheduling test method and device, network equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910295063.7A CN110098978B (en) 2019-04-12 2019-04-12 DNS scheduling test method and device, network equipment and storage medium

Publications (2)

Publication Number Publication Date
CN110098978A CN110098978A (en) 2019-08-06
CN110098978B true CN110098978B (en) 2021-02-26

Family

ID=67444786

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910295063.7A Expired - Fee Related CN110098978B (en) 2019-04-12 2019-04-12 DNS scheduling test method and device, network equipment and storage medium

Country Status (1)

Country Link
CN (1) CN110098978B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114500663B (en) * 2021-12-28 2024-04-12 网宿科技股份有限公司 Scheduling method, device, equipment and storage medium of content distribution network equipment

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2362302A (en) * 2000-05-08 2001-11-14 3Com Corp Network management data storage
CN101266566A (en) * 2007-03-13 2008-09-17 中国电信股份有限公司 Multi- test scene automatic dispatch system and method
CN102045411A (en) * 2009-10-13 2011-05-04 中国移动通信集团公司 Method, server and system for domain name resolution
CN104410691A (en) * 2014-11-27 2015-03-11 网宿科技股份有限公司 Method and system for website acceleration on basis of content delivery network
CN104852912A (en) * 2015-04-29 2015-08-19 中国互联网络信息中心 Domain name registration server performance testing system and domain name registration server performance testing method
CN105653451A (en) * 2015-12-29 2016-06-08 北京金山安全软件有限公司 Software performance testing method and device
CN106027408A (en) * 2016-04-26 2016-10-12 乐视控股（北京）有限公司 CDN (Content Delivery Network) network model node server access pressure detection method and system
CN106034083A (en) * 2015-03-12 2016-10-19 阿里巴巴集团控股有限公司 CDN system and rate-limiting control method thereof, CND node, and server
CN106331213A (en) * 2016-08-29 2017-01-11 广东欧珀移动通信有限公司 Domain name system DNS processing method and apparatus
CN106528432A (en) * 2016-12-12 2017-03-22 北京三快在线科技有限公司 Construction method and apparatus for test scene data, and buried point test method
CN106571981A (en) * 2016-11-15 2017-04-19 中国互联网络信息中心 DNS (Domain Name System) server automated testing method and system
CN106789360A (en) * 2017-02-15 2017-05-31 中国互联网络信息中心 A kind of DNS flow simulations system
CN108259237A (en) * 2018-01-05 2018-07-06 葛晗 Network access accelerated method, cloud dns server, CE and cloud IP accelerate network system
CN109361622A (en) * 2018-11-30 2019-02-19 网宿科技股份有限公司 The method and CDN system of bandwidth control are carried out to the service connection of CDN system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109542613A (en) * 2017-09-22 2019-03-29 中兴通讯股份有限公司 Distribution method, device and the storage medium of service dispatch in a kind of CDN node
CN109067938B (en) * 2018-10-15 2022-03-04 网宿科技股份有限公司 Method and device for testing DNS (Domain name Server)

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2362302A (en) * 2000-05-08 2001-11-14 3Com Corp Network management data storage
CN101266566A (en) * 2007-03-13 2008-09-17 中国电信股份有限公司 Multi- test scene automatic dispatch system and method
CN102045411A (en) * 2009-10-13 2011-05-04 中国移动通信集团公司 Method, server and system for domain name resolution
CN104410691A (en) * 2014-11-27 2015-03-11 网宿科技股份有限公司 Method and system for website acceleration on basis of content delivery network
CN106034083A (en) * 2015-03-12 2016-10-19 阿里巴巴集团控股有限公司 CDN system and rate-limiting control method thereof, CND node, and server
CN104852912A (en) * 2015-04-29 2015-08-19 中国互联网络信息中心 Domain name registration server performance testing system and domain name registration server performance testing method
CN105653451A (en) * 2015-12-29 2016-06-08 北京金山安全软件有限公司 Software performance testing method and device
CN106027408A (en) * 2016-04-26 2016-10-12 乐视控股（北京）有限公司 CDN (Content Delivery Network) network model node server access pressure detection method and system
CN106331213A (en) * 2016-08-29 2017-01-11 广东欧珀移动通信有限公司 Domain name system DNS processing method and apparatus
CN106571981A (en) * 2016-11-15 2017-04-19 中国互联网络信息中心 DNS (Domain Name System) server automated testing method and system
CN106528432A (en) * 2016-12-12 2017-03-22 北京三快在线科技有限公司 Construction method and apparatus for test scene data, and buried point test method
CN106789360A (en) * 2017-02-15 2017-05-31 中国互联网络信息中心 A kind of DNS flow simulations system
CN108259237A (en) * 2018-01-05 2018-07-06 葛晗 Network access accelerated method, cloud dns server, CE and cloud IP accelerate network system
CN109361622A (en) * 2018-11-30 2019-02-19 网宿科技股份有限公司 The method and CDN system of bandwidth control are carried out to the service connection of CDN system

Also Published As

Publication number Publication date
CN110098978A (en) 2019-08-06

Similar Documents

Publication Publication Date Title
US10148542B2 (en) Monitoring domain allocation performance
US11240156B2 (en) Techniques for steering network traffic to regions of a cloud computing system
CN111327461B (en) Domain name management method, device, equipment and medium based on CDN system
CN108494891A (en) A kind of domain name analytic method, server and system
CN108737532A (en) A kind of resource acquiring method, client, computer equipment and readable medium
US20170171344A1 (en) Scheduling method and server for content delivery network service node
EP3567881A2 (en) Request routing and updating routing information utilizing client location information
CN108737470B (en) Access request source returning method and device
BR112014020579B1 (en) METHOD, DEVICE AND SYSTEM FOR RDC VOLUME ALLOCATION
CN109067930A (en) Domain name cut-in method, domain name analytic method, server, terminal and storage medium
CN103780714A (en) Method and apparatus for probing DNS server
Meyer et al. Validated model-based performance prediction of multi-core software routers
CN108509256B (en) Method and device for scheduling running device and running device
US20140222896A1 (en) Distributed processing system and management method of distributed processing system
CN109639796A (en) A kind of implementation of load balancing, device, equipment and readable storage medium storing program for executing
CN110098978B (en) DNS scheduling test method and device, network equipment and storage medium
CN111966556A (en) Performance pressure measurement method and device, server and computer readable storage medium
CN106713456A (en) Network bandwidth statistics method and device
CN112019627B (en) Load balancing method, load balancing device, computer equipment and computer readable storage medium
CN109347766B (en) Resource scheduling method and device
US8769104B2 (en) System and method for loading web page using multiple paths in multiple interface circumstances
CN113301445B (en) Address allocation method and device for content distribution network
CN114520784A (en) Dynamic content accelerated access method and device
Meyer et al. Measurement and simulation of high-performance packet processing in software routers
CN113301172A (en) Response time measuring method, device, system and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20210226