CN111988389B

CN111988389B - Request scheduling mechanism of server based on HTTP/3 protocol

Info

Publication number: CN111988389B
Application number: CN202010814352.6A
Authority: CN
Inventors: 崔林; 林晋霆; 丁洪伟
Original assignee: Jinan University
Current assignee: Jinan University
Priority date: 2020-08-13
Filing date: 2020-08-13
Publication date: 2023-03-24
Anticipated expiration: 2040-08-13
Also published as: CN111988389A

Abstract

The invention discloses a server side request scheduling mechanism based on an HTTP/3 protocol, which comprises the following specific steps: the method comprises the steps of loading a target Web page from a browser, and extracting calling process information of related resources; generating a transmission sequence according to the use sequence of the related resources based on the calling process information; or constructing a loading dependency tree based on the call stack of the related resources, and generating a transmission sequence according to the loading dependency tree; and inputting the obtained resource transmission sequence into the HTTP/3 server, and enabling the HTTP/3 server to adjust the return sequence of the requests according to the resource transmission sequence. The method effectively solves the problem that the HTTP/3 server cannot reasonably adjust the request return sequence due to the lack of a request priority mechanism of the HTTP/3 protocol, and can effectively reduce the time consumption of the browser for loading the Web page.

Description

Request scheduling mechanism of server based on HTTP/3 protocol

Technical Field

The invention relates to the technical field of HTTP/3 protocol, in particular to a request scheduling mechanism of a server side based on the HTTP/3 protocol.

Background

With the increasing functionality of Web services, the amount of resources that a browser needs to load when loading Web pages also increases. The HTTP server can preferentially return resources which have important influence on the process of loading the Web page by the browser through a certain HTTP request priority mechanism. The HTTP/3 server cannot acquire the request priority information from the client because the HTTP/3 protocol currently lacks a request priority mechanism. Therefore, it is highly desirable to implement a suitable request priority mechanism on the HTTP/3 server side, so that the HTTP/3 server can preferentially return resources having a significant impact on the process of loading the Web page by the browser, thereby reducing the time consumption of loading the Web page by the browser.

Disclosure of Invention

The present invention is to solve the above problems in the prior art, and provide a server-side request scheduling mechanism based on HTTP/3 protocol. The mechanism solves the problem that the HTTP/3 server cannot adjust the return sequence of the requests because the HTTP/3 server cannot acquire the request priority information provided by the client through HTTP/3 connection.

In order to achieve the purpose, the invention is realized by the following technical scheme: a request scheduling mechanism of a server side based on an HTTP/3 protocol comprises the following specific steps:

step 1, a server side request scheduling mechanism of an HTTP/3 protocol can be divided into an offline key resource transmission sequence generation module and an online request scheduler module, and a server receives and processes requests from a browser through the HTTP/3 protocol;

step 2, inputting a log file recording the process of loading the specified Web page by the browser into an offline key resource transmission sequence generation module, and calling a key resource transmission sequence generation method to generate a transmission sequence for the key resource;

step 3, loading the obtained key resource transmission sequence into a dispatcher of the HTTP/3 server;

preferably, the offline key resource transmission sequence generation module includes an EF method, an LDT method, and an LDT1 method.

Preferably, the specific steps in step 1 are as follows:

A. the online request dispatcher module carries out analysis request operation after receiving a request from the browser;

B. after the request is analyzed, the request is placed into a request queue;

C. selecting a request needing to be returned at the current moment by an online scheduler module;

D. and returning the resource corresponding to the selected request.

Preferably, the step C of the scheduler sending out the request specifically includes;

a. selecting key resources in sequence according to given key resource transmission sequence

b. Non-critical resources are selected in the form of FCFS.

Preferably, the EF method specifically derives a transmission sequence of the key resources from an actual execution sequence of the key resources, so that the key resources are returned according to an actually used sequence, thereby reducing a time for the browser to acquire the actually required key resources.

Preferably, the LDT method specifically includes generating a loading dependency tree, and generating a transmission sequence according to the loading dependency tree.

Preferably, the LDT + method is specifically configured to modify a sorting manner of the resources without the successor node in the loading dependency tree to be sorted from front to back according to the order obtained by the EF method on the basis of the transmission order obtained by the LDT method.

Advantageous effects

The invention provides a request scheduling mechanism of a server side based on an HTTP/3 protocol. The method has the following beneficial effects:

the request scheduling mechanism of the server based on the HTTP/3 protocol enables a user to analyze the loaded Web pages by using a key resource transmission sequence generation method and generate a transmission sequence of key resources, and a request scheduler of the server can adjust a return sequence of requests from a client according to the transmission sequence. The request scheduling mechanism can effectively reduce the time consumption of the browser for loading the Web page, and can also reduce the time of the client for acquiring the resources and the memory utilization rate of the server when the server processes a large number of concurrent requests.

Drawings

FIG. 1 is a flowchart of the request scheduling mechanism of the server based on HTTP/3 protocol according to the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Referring to fig. 1, the present invention provides a technical solution: a request scheduling mechanism of a server based on an HTTP/3 protocol comprises the following specific steps:

step 1, a server side request scheduling mechanism of the HTTP/3 protocol can be divided into an offline key resource transmission sequence generation module and an online request scheduler module, and a server of the HTTP/3 protocol receives a request from a browser;

step 2, inputting the key resources into an offline module, and calling an realized key resource transmission sequence generation method to generate a transmission sequence for the key resources;

and 3, loading the obtained transmission sequence of the key resources into a scheduler of the HTTP/3 server to realize the ordered return of the key resources.

Further, the off-line key resource transmission sequence generating module includes an EF method, an LDT method, and an LDT + method.

Further, the specific steps in step 1 are as follows:

A. the online request dispatcher module analyzes the request operation after receiving the request from the browser;

B. after the request is analyzed, the request is placed into a request queue;

C. deciding, by the scheduler, which to issue the request;

D. and returning the selected resource.

Further, the scheduler sending out the request in step C is specifically;

a. selecting key resources according to a transmission order

b. Non-critical resources are selected in the form of FCFS.

Further, the EF method is specifically configured to derive a transmission sequence of the key resources based on an actual execution sequence of the key resources, so that the server returns the key resources in an order in which the key resources are actually used, and reduce time for the browser to acquire the actually required key resources.

Further, the LDT method specifically includes generating a loading dependency tree based on a reference relationship between the key resources and a call stack when the browser loads the key resources, and generating a transmission order of the key resources accordingly.

Further, the LDT + method is specifically that the order obtained by the EF method is replaced by the order of the LDT method from front to back.

A server-side optimization system based on an HTTP/3 protocol comprises the following specific steps: step 1, a server side request scheduling mechanism of the HTTP/3 protocol can be divided into an offline key resource transmission sequence generation module and an online request scheduler module, and a server of the HTTP/3 protocol receives a request from a browser; step 2, the user inputs the key resources into the off-line module and calls the realized key resource transmission sequence generation method to generate a transmission sequence for the key resources; and 3, the user can load the obtained transmission sequence of the key resources into a scheduler of the HTTP/3 server to realize the ordered return of the key resources.

The method comprises the following specific steps in step 1: A. the online request dispatcher module analyzes the request after receiving the request from the browser and places the request into a request queue; B. after the request is analyzed, the request is placed into a request queue; C. deciding, by the scheduler, which to issue the request; D. returning the selected resources, wherein the scheduler sends a request specifically in the step C; a. selecting key resources b according to a transmission sequence and selecting non-key resources in an FCFS form;

the offline key resource transmission sequence generation module comprises an EF method, an LDT method and an LDT + method, wherein the EF method is specifically used for deriving the transmission sequence of the key resources based on the actual execution sequence of the key resources, the LDT method is specifically used for generating the transmission sequence of the key resources based on the loading dependency tree of the key resources, and the LDT + method is specifically used for obtaining the transmission sequence of the key resources based on the LDT method and replacing the sequence of the resources without the subsequent nodes with the sequence obtained by the EF method for sequencing from front to back.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.

Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.

Claims

1. A request scheduling mechanism of a server side based on an HTTP/3 protocol, the request scheduling mechanism of the server side based on the HTTP/3 protocol controls an offline key resource transmission sequence generation module and an online request scheduler module, and the method specifically comprises the following steps:

step 1, an HTTP server receives and processes a request from a browser through an HTTP/3 protocol;

step 2, inputting the log file recording the process of loading the specified Web page by the browser into an offline key resource transmission sequence generation module, and generating a transmission sequence for the key resource by using a key resource transmission sequence generation method;

step 3, loading the obtained key resource transmission sequence into a request dispatcher of the HTTP/3 server;

step 4, the dispatcher of the HTTP/3 server realizes the sequential return of the key resources according to the transmission sequence of the given key resources;

the off-line key resource transmission sequence generation module uses an EF method, an LDT method and an LDT + method;

the LDT method specifically generates a transmission sequence based on a loading dependency tree;

the LDT + method specifically comprises the steps of generating a transmission sequence based on a loading dependency tree, and replacing the transmission sequence of the resource without the subsequent node in the loading dependency tree with the sequence obtained by an EF method;

the EF method specifically derives a transmission order of the key resources according to an actual execution order of the key resources, so that the key resources are returned according to an actually used order.

2. The request scheduling mechanism of the server side based on the HTTP/3 protocol as claimed in claim 1, wherein: the specific steps in the step 4 are as follows:

A. the request dispatcher performs request analysis operation;

B. after the request analysis operation is completed, the request is put into a request queue;

C. the request dispatcher selects a returned request according to a certain strategy;

D. and the request scheduler returns the resource corresponding to the selected request.

3. The request scheduling mechanism of the server side based on the HTTP/3 protocol as claimed in claim 2, wherein: the strategy for the scheduler to select the request in the step C is specifically as follows:

a. selecting key resources in sequence according to a given key resource transmission sequence;

b. non-critical resources are selected in the form of FCFS.