WO2011065692A2

WO2011065692A2 - System for measuring the response time of a server using dummy request tags and method for same

Info

Publication number: WO2011065692A2
Application number: PCT/KR2010/007929
Authority: WO
Inventors: 김성조
Original assignee: (주)제니퍼소프트
Priority date: 2009-11-24
Filing date: 2010-11-10
Publication date: 2011-06-03
Also published as: WO2011065692A3; KR20110057529A

Abstract

Disclosed are a server response time measurement method and system which measure the response time of an application server to a transaction which is processing a service request from a user terminal. The disclosed device comprises: a results page capture unit which receives a processing results webpage that relates to a service request from an application server; a dummy request insertion unit which inserts a tag requesting a dummy service in the application server into the processing results webpage; a results page transmission unit which transmits the processing results webpage to a user terminal; a dummy request receiving unit which receives a dummy request for a dummy request tag from a user terminal; and a response time estimation unit which estimates the response time by using the arrival time of the dummy request. The disclosed device and method measure the response time between a user terminal and a server by merely inserting an additional dummy request tag in a processing results webpage, and enable the stable and accurate measurement of a transaction response time without the introduction of expensive additional equipment or the installation of additional programmes onto a user terminal.

Description

System for measuring response time of server using dummy request tag and method

The present invention relates to a server response time measuring system and method for measuring a response time of an application server for a transaction processing a service request of a user terminal.

In particular, the present invention relates to a server response time measurement system and method for inserting a dummy request tag into a processing result web page and estimating a response time of a server using a time at which a dummy request of a user terminal arrives by a dummy request tag. .

In addition, the present invention includes the server response transmission time and the identification information of the service request in the dummy request tag inserted into the processing result web page, the server response to determine the response transmission time and identification information in the received dummy request A time measurement system and method.

In general, a WAS (Web Application Server, Web Application Server, or Web Application Server) refers to a server that provides an environment in which a web application can be executed. A web application is a program designed to serve some purpose on the web. That is, the web application server is a server that processes the service when a request is made to process a service from a user terminal (or user). At this time, a web application server processes one request that a user requests. In general, when a user connects to the web and requests a request such as clicking a mouse on a web page, a transaction is processed such that the web page being viewed is updated or moved to another web page in response. Will be.

The web application server is also a normal server, and is monitored in real time whether it is properly serving a request of a plurality of user terminals, and monitoring data is recorded and accumulated for analysis. In particular, since the web application server processes the service in one transaction unit, it is monitored and analyzed around the transaction. If you find a transaction that takes more time or fails than an average transaction, you can analyze the transaction and discover problems with the application server. By fixing or refining the problems found, the web application server can run more stably or efficiently.

One of the measurement variables that measure the performance of a web application server is the response time. The precise response time refers to the time from the moment the user terminal requests the service to the moment the service result is received from the application server. That is, the total processing time of a transaction for a service request.

As shown in FIG. 7A, a transaction of a general web application server 30 includes a service request S1 of a user terminal 10, a request reception S2 of a server, processing of a requested service S3, S4, and a service response. (S5) and receiving the processing result of the user terminal 10 (S6). Therefore, the response time of the transaction refers to the time required from the service request (S1) of the user terminal 10 to the processing result received (S6).

Conventionally, the response time presented by the performance of the application server 30 is often calculated as the service processing time of the application server 30. That is, in FIG. 7A, the time required from the service start (S3) to the service end (S4) of the application server 30 is used as the response time.

However, managing the processing time of the server as the response time as described above is inevitably different from the service quality felt by the user. For example, even if the processing time of the server shows a short response within 1 second, the speed of the Internet network is slow or the performance of the user terminal is poor, and thus the overall response time may be significantly reduced. Even in this situation, the server administrator cannot know the speed of the objective section and cannot manage the quality of service in terms of users.

On the other hand, techniques for measuring the processing time of the entire transaction include a method of measuring the response time directly from a specific user terminal or a method of introducing network equipment for collecting packets.

The former technique is a method of making a virtual service request by installing a test program on a user terminal. A user terminal generates a virtual transaction by making a virtual service request, and measures the overall response time of the virtual service request in the user terminal. That is, in FIG. 7A, when the user terminal 10 virtually makes a service request S1, the user terminal 10 records a service request time, and when the application server 30 receives the virtual service request, the user terminal 10 displays the corresponding processing result web page. Transmit to the terminal 10. The user terminal 10 records the service reception time when receiving the processing result web page, and obtains the overall service response time from the request time.

However, the measurement technology for the user terminal has a disadvantage in that a test program must be installed in the user terminal. In addition, since the virtual service request is not the actual service request, the processing time and the actual service processing time of the virtual service request may be different, and thus there is a problem in that an accurate response time cannot be calculated.

The latter technique measures the response time of messages sent and received when establishing a session at the network level. As shown in Fig. 7B, when a session is established by the TCP protocol, a 3-way handshaking scheme is used. That is, when the user terminal 10 wants to request a service sends a SYN message, the application server 30 returns a SYN-ACK, the user terminal 10 receives the message and sends an ACK message to the application server 30 , Session is established.

At this time, the application server 30 records the SYN receiving time when receiving the SYN and the ACK receiving time when receiving the ACK, and estimates the difference between the SYN receiving time and the ACK receiving time as the session establishment time. The session establishment time is estimated as the time at which the service request is transmitted. That is, in FIG. 7A, the time from the service request S1 to the request reception S2 is estimated as the session establishment time.

The technology for measuring at the network level as described above has the advantage of not needing to install a separate measurement program on the user terminal 10, there is a problem that a high-performance network equipment or system is required. That is, in order to record the arrival time of the SYN or ACK message or to confirm the session establishment of which service (or process) the arrival time is, the network equipment or the network system must check the information on a packet basis. Network equipment with this capability is very expensive.

On the other hand, there are the following techniques for measuring the processing time of the entire transaction. An example of this technique is presented in Korean Patent Laid-Open Publication No. 2007-0107927 (published Nov. 08, 2007), "Service Quality Measurement System and Method of Web Server" (hereinafter, referred to as Prior Art 1). In order to measure the service response time for a plurality of web servers belonging to one switch and performing the same service, the prior art 1 measures the time for which a test server requests a service from each web server and processes the request. .

In addition, an example of another technique is disclosed in Korean Patent Laid-Open Publication No. 2002-0078240 (published on October 18, 2002), "Method for collecting communication quality information, a computer-readable recording medium having the same, a communication quality analysis system using the same, and a method thereof. "] (Hereafter Prior Art 2). In the prior art 2, a client system including a manager program and a plurality of agent programs receives schedule information from a communication quality analysis server system, and is started based on the client system, and accesses a network test operation for a communication quality analysis and a specific network or a specific site. The service test operation is performed to provide the test information to the communication quality analysis server system. In particular, the prior art 2 measures the communication speed at the network level, such as transmitting ICMP echo messages to one or more routers existing on the path of the measurement target URL.

SUMMARY OF THE INVENTION An object of the present invention is to solve the above problems, and inserts a dummy request tag into a web page of a processing result and estimates a response time of a server using a time at which a dummy request of a user terminal arrives by the dummy request tag. It is to provide a server response time measurement system and method.

In addition, an object of the present invention is to include the response transmission time of the server and the identification information of the service request in the dummy request tag inserted in the processing result web page, so as to grasp the response transmission time and identification information from the received dummy request. To provide a server response time measurement system and method.

In order to achieve the above object, the present invention relates to a server response time measurement system for measuring a response time of an application server for a transaction processing a web service request of a user terminal, the processing result web page for the service request from the application server Receiving result page capture unit; A dummy request insertion unit for inserting a tag (hereinafter, referred to as a dummy request tag) for requesting a dummy service to the application server into the processing result web page; A result page relay unit which transmits the processing result web page to the user terminal; A dummy request receiver for receiving a dummy request by the dummy request tag from the user terminal; And a response time estimating unit estimating a response time using the arrival time of the dummy request.

In addition, the present invention is a server response time measurement system, wherein the dummy request tag is characterized in that the HTML tag for requesting data or JavaScript for requesting a service.

The present invention provides a server response time measurement system, wherein the dummy request insertion unit includes a response transmission time as a variable in the dummy request tag, and the response time estimating unit includes a response transmission time included as a variable in the dummy request. The arrival time difference is characterized by estimating the response time.

The present invention provides a server response time measurement system, wherein the dummy request inserting unit includes identification information of the service request as a variable (hereinafter, referred to as an identification variable) in the dummy request tag, and the response time estimating unit is included in the dummy request. Identify the response time estimated by the identification variable included.

The present invention is a server response time measurement system, characterized in that the identification information includes any one or more of a session ID (or transaction ID), application ID (or process ID), server ID.

The present invention also relates to a method for measuring a server response time of a system for measuring a response time of an application server for a transaction processing a web service request of a user terminal, the method comprising: (a) an application server displaying a processing result web page for a service request; Receiving from; (b) inserting a tag (hereinafter referred to as a dummy request tag) for requesting a dummy service to the application server into the processing result web page; (c) transmitting the processing result web page to the user terminal; (d) receiving a dummy request by the dummy request tag from the user terminal; And (e) estimating a response time using the arrival time of the dummy request.

In addition, in the method of measuring a response time of a server, in the step (b), the response transmission time is included in the dummy request tag as a variable, and in the step (e), the dummy request is included as a variable. The difference between the response transmission time and the arrival time is estimated as the response time.

In addition, in the method of measuring a response time of a server, in the step (b), the identification information of the service request is included in the dummy request tag as a variable (hereinafter referred to as an identification variable), and in the step (e), And identifying a response time estimated by the identification variable included in the dummy request.

The present invention also relates to a computer-readable recording medium having recorded thereon a program for performing a method for measuring a response time of the server.

As described above, according to the system and method for measuring the response time of the server according to the present invention, by introducing the additional expensive equipment or the user by measuring the response time between the user terminal and the server only by inserting additional dummy request tags in the processing result web page. The effect of accurately estimating the response time of a transaction is obtained in a stable manner without installing additional programs in the terminal.

In addition, according to the system and method for measuring the response time of the server according to the present invention, by including the response transmission time of the server and the identification information of the service request in the dummy request tag as variables, the response time only for the dummy request received from the computer terminal. The effect is to obtain and identify the transaction of the response time.

1 is a diagram illustrating the configuration of an entire system for implementing the present invention.

2 is a flowchart of a transaction of service request processing according to an embodiment of the present invention.

3 is a block diagram of a configuration of a system for measuring a response time of a server according to an exemplary embodiment of the present invention.

4 is a diagram illustrating a web page in which a processing result web page and a dummy request tag are inserted according to an embodiment of the present invention.

5 is a flowchart illustrating a method of measuring a response time of a server in the clouding server according to another embodiment of the present invention.

6 is a flowchart illustrating a method of measuring a response time of a server according to an embodiment of the present invention.

7 is a transaction flow diagram of a service request process according to the prior art.

DETAILED DESCRIPTION Hereinafter, specific contents for carrying out the present invention will be described with reference to the drawings.

In addition, in describing this invention, the same code | symbol is attached | subjected and the repeated description is abbreviate | omitted.

First, the overall web service system and the transaction of the web service for implementing the present invention will be described with reference to FIG.

As shown in FIG. 1, the entire system for implementing the present invention includes a user terminal 10, a web application server 30, and a response time measurement system 40. The user terminal 10 and the application server 30 is connected via the Internet 20. On the other hand, it may be configured to further include a database 50 for storing necessary data.

The user terminal 10 is a conventional computing terminal used by a user. Examples of the user terminal 10 include a PC, a PDA, a mobile, and the like, and a detailed description thereof will be omitted since its configuration and operation principle are well-known techniques commonly used in the art. The user terminal 10 is provided with a web browser, the user can access the application server 30 through the web browser to receive a web service.

The web application server 30 (or application server) is a conventional web application server (WAS, Web Application Server). In general, web services are provided by a web server (not shown) and a web application server on the Internet. That is, the user terminal 10 first connects to a web server, and when the web server needs to perform an application in response to a service request from the user terminal, the web application server 30 requests the service processing, and the result is returned. A web page (hereinafter referred to as a processing result web page) is configured and transmitted to the user terminal 10. The web server is a server that provides content to the web browser of the user terminal 10 using the HTTL protocol, such as HTML document or image, whereas the application server 30 functions as a server that can operate the application on the server side . In the following description, the web server and the web application server 30 will be referred to as a web application server 30 as a server for providing a web service.

Response time measurement system 40 (or measurement system) is a system for measuring the service response time of the web application server (30). The measurement system 40 inserts the dummy request tag into the web page (or the processing result web page) of the result processed by the application server 30, receives the dummy request by the dummy request tag, and uses the reception time. Measure the response time. The measurement system 40 may be implemented in the application server 30, or may be implemented as a separate server. When the measurement system 40 is constructed as a separate server, a program module for receiving a processing result web page or a dummy request from the application server 30 is installed, and the other program modules are built on a separate server. desirable.

The database 50 includes identification information 51 for identifying a service request such as a transaction ID, a service ID, a server ID, a response time DB 52 for storing an estimated service response time, and the like. However, the configuration of the database 50 is only a preferred embodiment, and in the development of a specific device, it may be configured in a different structure by the database construction theory in view of the ease and efficiency of access and search.

Next, a transaction of the service request processing according to an embodiment of the present invention will be described with reference to FIG. The transaction of the service request processing refers to a series of processes in which the user terminal 10 requests a service from the application server 30 and receives a response to the service request from the application server 30.

As shown in FIG. 2, the transaction of the service request processing includes the service request step S11 of the user terminal 10, the service process S13 of the application server 30, and the processing result webpage transmission step S14, a measurement system. Inserting and relaying the dummy request tag in the processing result web page (40) (S15, S16), the rendering and the dummy request step (S17, S18) of the processing result web page in the web browser of the user terminal 10 .

First, when the user terminal 10 requests a service to the application server 30, a session is established between the user terminal 10 and the application server 30, and the service request is transmitted to the application server 30 (S11). ).

The application server 30 receives the service request and processes the service for the request (S13). The application server 30 writes the processing result into a web page (hereinafter referred to as a processing result web page) and transmits it (S14).

The measurement system 40 captures (or receives) the processing result web page transmitted by the application server 30 (S14). The measurement system 40 inserts a dummy request tag into the processing result web page (S15) and transmits the dummy request tag to the user terminal 10 (S16).

In general, the web application server 30 transmits the processing result web page to the user terminal 10 that is the counterpart of the session. Preferably, the measurement system 40 captures and retrieves the process result web page transmitted to the user terminal in the middle, and then corrects the process result web page and retransmits it to the user terminal 10 again. Therefore, the present invention provides the effect that the conventional web application server 30 can be used as it is.

The user terminal 10 receives the processing result web page and outputs (renders) the screen through a web browser (S17). At this time, when the user terminal 10 renders the dummy request tag, the user terminal 10 makes a dummy request to the application server 30 again by the dummy request tag (S18).

The measurement system 40 captures (or receives) the dummy request (S19). That is, as in the middle of capturing the processing result web page transmitted to the user terminal 10, the dummy request transmitted to the application server 30 is captured. Preferably, a session is set up in the application server 30 to install (or hook) a module for capturing and transmitting data to capture a web page or a dummy request and the like.

As a result, the dummy request transmitted from the user terminal 10 is a message sent to the application server 30, but in fact is not transmitted to the application server 30 but is blocked and the response is sent by the measurement system 40.

Measurement system 40 receives the dummy request and records the received time. The measurement system 40 estimates the response time of the transaction of the service request using the recorded reception time.

Next, the configuration of the response time measurement system of the server according to an embodiment of the present invention will be described with reference to FIGS. 3 and 4. 2 is a block diagram of the configuration of the response time measurement system 40, and FIG. 4 illustrates a web page in which a processing result web page and a dummy request tag are inserted.

As shown in Figure 2, the response time measurement system 40 according to an embodiment of the present invention is a result page capture unit 41, a dummy request insertion unit 42, a result page relay unit 43, a dummy request receiving unit (44), a response time estimating unit (45).

The result page capture unit 41 captures the processing result web page for the service request from the application server 30. As described above, the service request is requested by the user terminal 10, the application server 30 processes the service request and generates the result as a processing result web page. The processing result web page is a web page written in HTML format as shown in FIG. 4A.

The dummy request inserting unit 42 inserts a tag (hereinafter, referred to as a dummy request tag) for requesting a dummy service from the application server 30 into the processing result web page. Preferably, the dummy request tag is written in HTML tag requesting data or JavaScript requesting service.

As shown in FIG. 4B, the dummy request inserting unit 42 is inserted at the bottom of the last page of the processing result web page. In this case, after all the web pages are rendered as a result of the processing, the dummy request is sent to the application server 30.

However, in another embodiment, the processing result may be inserted at the top of the web page. In this case, since the user terminal 10 transmits the dummy request immediately after receiving the processing result web page, the pure response time between the processing result web page and the dummy request is received. That is, except for the time for rendering the web page as a result of the processing, only the data transmission time between the user terminal 10 and the application server 30 can be obtained purely.

Since the response time obtained in the embodiment inserted at the bottom includes the time rendered by the computer terminal 10, the service delay caused by the late performance of the computer terminal 10 may also be measured. Meanwhile, as another embodiment, the dummy request tag may be inserted at both the top and the bottom.

The dummy request inserter 42 may include the response transmission time as a variable in the dummy request tag. In addition, the dummy request inserting unit 42 may include the identification information of the service request in the dummy request tag as a variable (hereinafter, referred to as an identification variable). The identification information includes any one or more of a session ID (or transaction ID), an application ID (or process ID), and a server ID.

As shown in FIG. 4B, the dummy request tag may be inserted in the form of <img src = "(data request phrase)">. The dummy request tag is a tag for requesting image data. (Data request phrase) is a URL execution code for requesting the image data from the application server 30.

The URL execution code may include a variable. In FIG. 4B, x, a, t, i, p, w, and the like are variables, and the variable values are included as "(variable) = (variable value)". The variable x is a variable for a transaction ID, a is a variable for a service code, t is a time at which the web page is transmitted or responded to by the server (hereinafter referred to as response time), p is an IP address of the user terminal 10, w denotes a user ID or the like.

The dummy request inserting unit 42 can know information such as a transaction, a requested service, an application server, etc. from the processing result web page transmitted from the application server 30. That is, they can be identified. The transaction ID (or session ID) is information identifying a transaction, the application ID (or process ID) is information identifying a requested service, and the server ID is information identifying an application server. The transaction ID, application ID, and server ID may be applied to any information that can distinguish a transaction, a requested service, and an application server. In addition, the identification information of the user terminal or the user may be included.

The result page relay unit 43 transmits the processing result web page to the user terminal 10. The processing result web page transmitted at this time is a web page into which the dummy request tag is inserted. As described above, the user terminal 10 renders the processing result web page received through the web browser, and transmits the dummy request to the application server 30 by the dummy request tag in the rendering process.

The dummy request receiver 44 receives a dummy request by the dummy request tag from the user terminal 30 and records the received time (hereinafter, referred to as a reception time). As seen above, the dummy request is a message sent to the application server 30, and the dummy request receiver 44 captures this message in the middle.

On the other hand, when the dummy request tag includes a variable, the variable is included in the dummy request as it is, the dummy request receiving unit 44 receives a dummy request including the variable.

The response time estimator 45 estimates the response time using the arrival time of the dummy request. Preferably, the response time estimator 45 estimates the difference between the response transmission time included in the dummy request and the arrival time as the response time. In addition, the response time estimator 45 identifies the response time estimated by the transaction identification variable included in the dummy request.

The response time will be described in more detail with reference to FIG. 2. In FIG. 2, [A], [B], ..., [E] indicate a section in which an arrow is indicated. On the other hand, since the measurement system 40 is installed on the application server 30 side, the data transmission time between the measurement system 40 and the application server 30 may be regarded as zero. For example, the time taken in the S14 section, which is the process of transmitting the web page as a result, is almost zero.

The response transmission time included in the dummy request is a time inserted at point S15 of FIG. 2, and the reception time is a time at which a dummy request is received at point S21 of FIG. 2. Therefore, the difference in the response transmission time at the reception time means the time in the processing result web page relay (S16), rendering (S17), and dummy request (S18) sections in FIG. 2, and the sections [C] and [D] of FIG. ], [E].

The total response time of the service request originally intended is the time taken in the interval [A] + [B] + [C]. The time required for section [B] is purely the service processing time of the application server, and the time required for sections [A] and [C] is the response time on the network.

However, since the response time on the network of the [A] and [C] sections cannot be measured, the time required for the [C], [D] and [E] sections is measured instead. The duration of [C], [D], and [E] is the estimated time of response on the network, and the sum of the duration of [C], [D], and [E] and the service processing time of [B]. The time required is an estimate of the overall response time. Hereinafter, the response time is referred to as the response time on the network.

On the other hand, as described above, when the dummy request tag is inserted at the top of the processing result web page, the duration of the section [D] is almost zero, so the duration of the sections [C], [D], and [E] May be regarded as the time required between the sections [C] and [E], and may be referred to as the estimated time between the sections [A] and [C].

In addition, the response time estimator 45 distinguishes and stores the estimated response time according to the identification variable for the service request in the dummy request. Or store the identification variable with a response time. Using the identification information as described above, statistics of response time for each transaction, service, server, user, and user terminal may be calculated.

The statistics of the response time can be used as very important data for the failure and improvement of the request service. For example, the average response time of requesting services of terminals of a specific region can be obtained from identification information (IP address, etc.) of the user terminal, and the region to be improved or restored is determined by determining the region where the average response time is lower than the reference value. You can figure it out. In addition, by obtaining the average response time of a specific service, it is possible to identify the service that is delayed to identify the specific service to be improved.

Next, an example in which the application server according to an embodiment of the present invention is a clouding server will be described with reference to FIG. 5.

As shown in FIG. 5, the application server 30 may consist of server 1, server 2, ..., server N in some cases. Each server performs the same service function. In this case, a server is arbitrarily assigned to the service requested by the user terminal 10. Each service request establishes a session with an arbitrarily assigned server and performs service processing. Therefore, the measurement system 40 receives the processing result web page from an arbitrary server.

The measurement system 40 inserts the identification information (or server ID) of the server received in the dummy request into the processing result web page as a variable and transmits it to the user terminal 10. When the measurement system 40 receives the dummy request, since the server ID exists in the dummy request, the server ID may determine which server's response time is used for the transaction. Therefore, when the measurement system 40 inserts the dummy request tag, it is possible to know which server the estimated response time is related to by simply analyzing the dummy request without storing additional server information.

The above effects correspond to all of the identification information included in the dummy request.

Next, a method of measuring a response time of a server according to an embodiment of the present invention will be described with reference to FIG. 6. The response time measurement method is a method in which the measurement system 40 measures the response time of the application server 30.

As shown in Figure 6, the response time measuring method comprises the steps of (a) receiving a processing result web page for the service request from the application server (S30); (b) inserting a tag (hereinafter, referred to as a dummy request tag) for requesting a dummy service into the application server in the processing result web page (S40); (c) transmitting the processing result web page to the user terminal (S50); (d) receiving a dummy request by the dummy request tag from the user terminal (S60); And (e) estimating a response time using the arrival time of the dummy request (S70).

In particular, in step (b), the response transmission time is included in the dummy request tag as a variable, and in step (e), the difference between the response transmission time and the arrival time included in the dummy request as a variable is response time. Estimate as

In addition, in step (b), the identification information of the service request is included in the dummy request tag as a variable (hereinafter, referred to as an identification variable), and in step (e), estimated by the identification variable included in the dummy request. Identifies the response time.

The omitted part of the description of the method for measuring the server response time refers to the description of the server response time measuring system described above.

As mentioned above, although the invention made by this inventor was demonstrated concretely according to the said Example, this invention is not limited to the said Example and can be variously changed in the range which does not deviate from the summary.

The present invention can be applied to a server response time measurement system for measuring the response time of the application server for the transaction processing the service request of the user terminal. In particular, the present invention can be applied to a server response time measurement system for inserting a dummy request tag into a processing result web page and estimating the response time of the server using the time at which the dummy request of the user terminal arrives by the dummy request tag. .

Claims

In the server response time measurement system for measuring the response time of the application server for the transaction processing the web service request of the user terminal,

A result page capture unit for receiving a processing result web page for a service request from an application server;

A dummy request insertion unit for inserting a tag (hereinafter, referred to as a dummy request tag) for requesting a dummy service to the application server into the processing result web page;

A result page relay unit which transmits the processing result web page to the user terminal;

A dummy request receiving unit which receives a dummy request by the dummy request tag from the user terminal and records an arrival time; And

And a response time estimating unit estimating a response time using the arrival time of the dummy request.
The method of claim 1,

The dummy request tag is a response time measurement system of a server, characterized in that written in HTML tags requesting data or JavaScript requesting a service.
The method of claim 1,

The dummy request insertion unit includes a response transmission time as a variable in the dummy request tag, and the response time estimating unit estimates a difference between the response transmission time included in the dummy request and the arrival time as a response time. System for measuring response time of servers.
The method of claim 1,

The dummy request inserting unit includes identification information of the service request in the dummy request tag as a variable (hereinafter, referred to as an identification variable), and the response time estimating unit identifies a response time estimated by the identification variable included in the dummy request. Response time measurement system of the server, characterized in that.
The method of claim 4, wherein

The identification information server response time measurement system comprising any one or more of a session ID (or transaction ID), an application ID (or process ID), server ID.
In the server response time measurement method of the system for measuring the response time of the application server for the transaction processing the web service request of the user terminal,

(a) receiving a processing result web page from the application server for the service request;

(b) inserting a tag (hereinafter, referred to as a dummy request tag) for requesting a dummy service in the application server into the processing result web page;

(c) transmitting the processing result web page to the user terminal;

(d) receiving a dummy request by the dummy request tag from the user terminal; And

(e) estimating a response time using the arrival time of the dummy request.
The method of claim 6,

In step (b), the response transmission time is included in the dummy request tag as a variable, and in step (e), the difference between the response transmission time included in the dummy request and the arrival time is estimated as a response time. Response time measurement method of the server, characterized in that.
The method of claim 6,

In step (b), the identification information of the service request is included in the dummy request tag as a variable (hereinafter, referred to as an identification variable), and in step (e), the response estimated by the identification variable included in the dummy request Response time measurement method of the server, characterized in that identifying the time.
A computer-readable recording medium having recorded thereon a program for performing a method of measuring a response time of a server according to any one of claims 6 to 8.