JP2003141076A - Web application processing performance measurement method and web application server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To measure the processing performance of a Web application body (controller, business logic and presentation) without requiring the integration of the measuring function of application processing performance into the Web application body by a developer. SOLUTION: This method comprises providing a performance measuring filter, starting, in the acceptance of a corresponding request from a client, the performance measurement of the Web application by the filtering function of the performance measuring filter before executing the processing of the Web application body, and ending the performance measurement of the Web application at the end of the processing of the Web application body.

Description

Detailed Description of the Invention

[0001]

The present invention relates to an application processing performance measuring method and an application server,
For example, it can be applied to a Web application server system.

[0002]

2. Description of the Related Art Recently, Internet technologies have been incorporated into client / server architectures. In fact, on the Internet, electronic commerce (EC) involving database updating, and business construction involving a large amount of data updating in an intranet internal system are increasing. In particular, in order to handle a large amount of processing and update the database, development and operation will be a difficult task. A web application server has emerged to support this.

FIG. 2 is a block diagram showing the basic configuration of a web application server system including a web application server.

In FIG. 2, a web application server system 1 includes a client 2, a web server 3,
The web application server 4 and the data source 5 are composed of four large modules.

The client 2 is connected to the Web application server 4 via the Web server 3 or directly and realizes a presentation function for a user, and is generally realized on a Web browser. is there.

[0006] The Web server 3 controls the link process between the GUI process in the browser and the actual business process. The function of the web server 3 may be incorporated in the web application server 4.

The Web application server 4 is also called an application execution platform, an application engine, etc., and its basic role is to execute business processing. Therefore, it is necessary to realize reliability and expandability here. It may also be a bridge to other systems such as existing systems.

[0008] The data source 5 is, for example, a database itself, and may also be various existing open systems and general-purpose machines (for example, a payment server and a mail server).

The Web application server system 1 composed of the above-described modules needs to be able to handle the requests from many clients 2 so that it can be applied to online shopping.
b Performance of the application server 4 becomes a problem.

Conventionally, performance management packages (software) installed in the Web application server 4 have been used to collect system resource usage status data such as CPU usage rate and memory usage rate as performance data. Further, network traffic data is collected as performance data by using a network management node (not shown) or a network management package (software) installed in the Web application server 4.

Further, the Web application developer creates a log data output function in the application program so that the application processing performance can be captured later, manages the log data, and if necessary, uses the log data to obtain the application processing performance. Was also being grasped.

[0012]

However, the method of using software such as the performance management package or the network management package cannot capture the processing performance of the application itself.

Further, in the method in which the application developer creates a function capable of grasping the application processing performance in the application program, there is a problem that only the application intended to grasp the processing performance by the developer can capture the processing performance. .

Therefore, the application developer can measure the processing performance of the developed Web application without paying attention to the application processing performance measurement function.
There is a demand for a method for measuring application processing performance and a Web application server that can realize the measuring method.

[0015]

In order to solve such a problem, the web application processing performance measuring method according to the first aspect of the present invention has a performance measuring filter, and the filtering function of this performance measuring filter allows the corresponding When the request is accepted, the performance measurement of the Web application is started before the processing of the Web application body consisting of the controller, the business logic and the presentation is started, and the performance measurement of the Web application is finished when the processing of the Web application body is finished. It is characterized by doing.

The Web application server of the second aspect of the present invention is a Web application server that executes a Web application in response to a request from a client and sends a response to the client, and uses a controller, business logic, and presentation. It has a web application body and a performance measurement filter, and the performance measurement filter of the performance measurement filter measures the performance of the web application before executing the processing of the web application body when the corresponding request is received from the client. Is started, and the performance measurement of the Web application is ended when the processing of the Web application main body is ended.

[0017]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of a web application processing performance measuring method and a web application server according to the present invention will be described in detail below with reference to the drawings.
The web application server of this embodiment also has a function of a web server (see FIG. 2).

FIG. 1 is an explanatory diagram showing the software configuration of the Web application server according to this embodiment, and FIG. 3 is an explanatory diagram showing the relationship between each software element.

Although illustration is omitted, the Web application server of this embodiment also has a CPU, a memory, a communication unit, an auxiliary storage device, and the like in terms of hardware, similar to a general server.

In FIG. 1, the Web application server 10 includes a client (Web client) 11
The software is appropriately accessed by, and has a Web application 12 and a performance management package 13 as software.

If the Web application server 10 can handle a plurality of types of business processing,
A Web application 12 for each type of business process, that is, a plurality of Web applications 12 are installed. In this way, a plurality of Web applications 12
Performance management package 13
Can be common (although there can be more than one).

The Web application 12 is a controller (for example, S which is a Java (registered trademark) program).
14), business logic (for example, E as an application model in Java)
It has a JB 15) and a presentation (e.g., a JSP that handles a screen function (View) in Java) 16 and further has a performance measurement filter 17 that is a feature of this embodiment.

The controller servlet 14 controls the business logic 15 and the presentation 16. Business logic 15 is for data processing W
It performs the main processing of the eb application.
The presentation 16 is for displaying the processing result of the Web application on the client 11.

The performance management package 13 manages the performance information acquired by the performance measurement filter 17 as performance data on the disk and has a function of an analyzer or the like for analyzing the performance data. The performance management package 13 also has a function of acquiring system resource performance information (CPU usage rate, memory usage rate, etc.), managing it as performance data, and analyzing it. This point is the same as the conventional one. .

The performance measurement filter 17 is provided to acquire performance information of the Web application. The performance information of the Web application is, for example,
It is the processing time of the Web application from a certain HTTP request to the transmission of an HTTP response thereto.

The controller (servlet) 14 actually has a filter function that functions before the original processing such that the input data satisfying the predetermined format is passed. For example, this filter function Is used to construct the performance measurement filter 17.

FIG. 4 is an explanatory diagram showing the functional configuration of the performance measuring filter 17. The performance measurement filter 17 has a measurement information definition file reading function unit 31, a measurement information definition reading area 32, a request determination function unit 33, a performance measurement start function unit 34, a performance measurement end function unit 35, and the like.

Measurement information definition file reading function unit 31
When the Web application is activated, the information in the measurement information definition file (see FIG. 5) is loaded into the measurement information definition reading area 32 as an initialization process of the performance measurement filter 17.
Is to be read into.

FIG. 5 shows an example of the structure of the measurement information definition file. The measurement information definition file 40 includes a measurement parameter name 41, a measurement parameter value 42, and a measurement process name list 43.

The measurement parameter name 41 is the client 11
When the request from (HTTP request) has this parameter name, it is possible to be a measurement target. The parameter name does not specify a specific measurement parameter, and the specific measurement parameter is defined by the measurement parameter value 42. The measurement process name list 43 forms a pair with the measurement parameter value 42. When the result of performance measurement or the like is displayed, when the measurement parameter value 42 is displayed as it is, the result analyzer analyzes the parameter. Since it is difficult to immediately understand the meaning of the above, the name is associated with the measurement parameter value 42 in order to solve it.

That is, requests to be measured are described in the measurement information definition file 40 as a combination of parameter values, and it is possible to narrow down the requests to be measured and perform the measurement. Further, the measurement process name is defined for the combination of parameter values, and the performance analysis can be efficiently performed by defining the measurement process name which is easy to understand.

A specific example of the measurement information definition file 40 is shown in FIG. X, and its contents will be described later.

The request discriminating function unit 33 uses the information (measurement information definition file 40) stored in the measurement information definition reading area 32 when receiving the HTTP request, and determines whether or not the request is related to performance measurement. The determination processing is performed.

When the determination result of the request determination function unit 33 indicates that the acceptance request is related to the performance measurement, the performance measurement start function unit 34 measures the performance of the Web application of the process related to the corresponding parameter value. Is to start.

The performance measurement end function unit 35 is an HT for the HTTP request that triggered the performance measurement.
The performance measurement is ended when the TP response is sent.

FIG. 6 is a block diagram of the request discrimination function unit 3 described above.
3 is a flowchart showing the processing of 3 and the performance measurement start function unit 34.

The request discriminating function unit 33 sets the value of the measurement parameter specified in the measurement information definition file 40 stored in the measurement information definition reading area 32 to HTT.
It is taken out from the P request (step 51). HTTP
Matching is performed to see if the combination of parameter values extracted from the request is in the list of measurement parameter values 42 specified in the measurement information definition file 40 (steps 52 and 53). If it is in the list, the performance measurement start function unit 34 executes the measurement start process with the measurement process name 43 specified in the measurement information definition file 40 (step 54).

FIG. 7 is a sequence diagram showing the operation of each section in the Web application server 10 of the embodiment. Note that FIG. 7 shows a case where the performance measurement is executed.

When the Web client 11 sends an HTTP request to the Web application server 10 (step 61), the performance measurement filter 17 executes filtering (preprocessing) under the control of the controller 14 (step 62). In other words, the servlet function of the servlet measures the pre-servlet processing of the performance measurement filter 17.

The performance measurement filter 17 receives the received HT
When it is determined that the TP request executes the performance measurement (see FIG. 6), the performance management package 13 is requested to start the measurement (step 63).

After that, the controller (servlet) 1
4 requests application processing from the business lock 15 (step 64), and the business logic 15
Performs application processing. The controller (servlet) 14 requests the presentation 16 to display the application processing result (step 65). The presentation 16 sends the result of the application processing to the Web client 11 using HTTP.
It is sent as a response (step 66).

Note that the processing in steps 64-66 is performed by We.
The processing is the same as the conventional processing of the b application.

When the processing of the controller (servlet) 14 is finished, the post-processing (post-processing of the servlet) by the performance measuring filter 17 is executed (step 67).
The performance measurement filter 17 requests the performance management package 13 to end the measurement (step 68).

When an HTTP request unrelated to the performance measurement arrives, the performance measurement filter 17 does not recognize the necessity of the performance measurement even if the performance measurement filter 17 performs the pre-processing, and the performance measurement filter 17 performs the performance management package 1.
The general web application processing (steps 64 to 66) by the controller (servlet) 14, the business logic 15 and the presentation 16 is simply executed without requesting the measurement start of No. 3.

The Web of the embodiment will be described below by way of specific examples.
The operation of the application server 10, in particular, the operation of the performance measurement filter 17 will be described.

FIG. 8 shows an example of a plurality of screens presented to the Web client 11 by the Web application relating to “direct online shopping from production area”. Also,
FIG. 9 shows parameter names and parameter values associated with each button icon (hereinafter referred to as a button) on each screen.

The screen 1 in FIG. 8 is the main screen, and is provided with button icons 1 and 2 called "login" and "product list". Parameter names and parameter values as shown in FIG. 9 are associated with these buttons 1 and 2, and when the button 1 or button 2 is operated, they are associated with the buttons from the Web client 11. HTTP request including the parameter name and parameter value
It is given to the eb application server 10.

For example, when the "product list" button (button 2) on the screen 1 is operated, the parameter name "pa
"ge, button" and parameter value "MainPag
An HTTP request including “e, list” is given to the web application server 10.

In this case, if the content of the measurement information definition file 40 is as shown in FIG. 10, it is not recognized as a measurement object even by the filtering by the performance measurement filter 17, and the controller 14, the business logic 15 and the presentation 16 indicate. Normal processing is performed. That is, controller 14, business logic 1
5 and presentation 16 etc. search for a product from a database (DB; not shown) which is a data source,
The result is displayed on the product list screen (screen 2). In other words, the screen 2 is given to the Web client 11 as an HTTP response and displayed.

Here, when the content of the measurement information definition file 40 is as shown in FIG. 10, the performance measurement filter 1
The processing of the request discrimination function unit 33 and the performance measurement start function unit 34 of No. 7 is as shown in the flowchart of FIG. Note that FIG. 11 is a rewrite of the flowchart of FIG. 6 described above according to the contents of FIG. 10.

The parameter name "page, butt" described above
When the HTTP request including the parameter value “MainPage, list” of “on” is given, a negative result is obtained in step 53 of FIG. 11, and the performance measurement is not started.

The screen 2 in FIG. 8 is a product list screen, and buttons 3 to 5 of "apple", "grape" and "mandarin orange" are provided. Parameter names and parameter values as shown in FIG. 9 are also associated with these buttons 3 to 5, and when any of the buttons is operated, the parameter associated with the button from the Web client 11 is displayed. An HTTP request including a combination of a name and a parameter value is given to the web application server 10.

For example, when the "apple" button (button 3) on the screen 2 is operated, the parameter name "page,
button ”and the parameter value“ ListPage, a
An HTTP request including “ppple” is given to the web application server 10.

The content of the measurement information definition file 40 is shown in FIG.
Therefore, the HTTP request is not recognized as a measurement target even by the filtering by the performance measurement filter 17, and the normal processing by the controller 14, the business logic 15 and the presentation 16 is performed. That is, the controller 14, the business logic 15, the presentation 16 and the like retrieve apple information from a database (DB; not shown) which is a data source, and display the result on the apple screen (screen 3). In other words, the screen 3 is given to the Web client 11 as an HTTP response and displayed.

The screen 3 in FIG. 8 is an apple screen, and buttons 6 and 7 for "details" and "purchase" are provided. A combination of parameter names and parameter values as shown in FIG. 9 is also associated with these buttons 6 and 7, and when either button is operated, W
H including the combination of the parameter name and the parameter value associated with the button from the eb client 11
The TTP request is the Web application server 10
Given to.

For example, when the "purchase" button (button 7) on the screen 3 is operated, the parameter name "page, b"
"utton" and the parameter value "ApplePage, b
HTTP request including the combination of "uy"
It is given to the application server 10.

The content of the measurement information definition file 40 is shown in FIG.
Therefore, the HTTP request is recognized as a measurement target by filtering by the performance measurement filter 17. That is, a positive result is obtained in step 53 of FIG. 11, and the measurement start process is executed with the measurement process name “BuyApple”. As a result, the performance management package 13 starts measurement.

After the start of the measurement start, the normal processing when the button 7 is operated by the controller 14, the business logic 15 and the presentation 16 is performed. That is, controller 14, business logic 1
5 and presentation 16 and the like execute apple purchase processing (settlement, shipping processing, etc.) and display a purchase completion screen (screen 4). In other words, the screen 4 is given to the Web client 11 as an HTTP response and displayed.

The screen 4 displays the HTTP response as Web
When sent to the client 11, this HTTP
The performance measurement package 13 ends the performance measurement process started with the HTTP request that is the premise of the response.

The screen 4 in FIG. 8 is a purchase completion screen, which notifies the user of a simple message such as "Purchase completed" or "Delivery within one week", and the parameter name and parameter value. Is not defined.

It should be noted that the above-mentioned specific examples are shown in abbreviated form than the actual ones for the sake of simple explanation, and the screen is provided with an input field or the like in which a character string can be appropriately input and accordingly Processing etc. are also executed.

The performance itself (eg, processing time) may be measured by the performance measurement filter 17, and the performance measurement filter 17 notifies the performance management package 13 of the start and end of the measurement, and the performance management package 13 is notified.
May be performed. In the former case, the data measured by the performance measurement filter 17 is sent to the performance management package 13, and the performance management package 13 manages the performance data in an integrated manner.

The performance management package 13
Collects and manages system resource usage rate data such as CPU usage rate and memory usage rate in the same manner as in the past.

FIG. 12 is an example of a graph (horizontal axis indicates elapsed time) obtained by the performance management package 13 analyzing the Web application processing performance data (application processing time) 13A and the system resource usage rate data 13B. From FIG. 12, the application processing time (represented by Web AP on the graph) and the memory usage rate (represented by Memory on the graph) are high, and the CPU usage rate (represented by CPU on the graph) is very different. I know that not. From this, it can be seen that the memory shortage is the cause of the increase in application processing time. From this analysis result, it becomes possible to make a plan as a measure for performance improvement by implementing memory expansion.

According to the above embodiment, the measurement object is defined by the measurement information definition file, and the performance measurement filter for discriminating the HTTP request related to the defined measurement object is provided. Therefore, the controller (servlet), The performance of the Web application can be measured without affecting the business logic (EJB) and the presentation (JSP) (without incorporating a measurement function into them).

Web application (software)
Since the performance of can be measured, as described above,
Relationships with system resources can be easily obtained,
It can be reflected in the construction and reconstruction of the web application server and the web application server system.

Further, the function of measuring the performance of the Web application is sufficient for the developer of the Web application to concentrate on the development of the controller (servlet), business logic (EJB), presentation (JSP) and the like. In other words, the controller (servlet),
When developing a business logic (EJB), a presentation (JSP), etc., it is not necessary to create a performance measurement function, and then a measurement information definition file according to the item to be measured may be created.

Furthermore, since the request to be measured can be described as a combination of parameter values in the measurement information definition file, it is possible to narrow down the requests to be measured and perform the measurement. Furthermore, since the measurement processing name can be defined in the combination of parameter values, performance analysis can be efficiently performed by defining the measurement processing name that is easy to understand.

In the above embodiment, the Web application server having the function of the Web server described with reference to FIG. 2 is shown, but the Web server and We described with reference to FIG.
b Even if it is separated from the application server,
The present invention can be applied. W in the claims
The term eb application server refers to a group of both, even if they are separated. Further, the present invention can be applied to a system in which a plurality of Web application servers perform distributed processing if a performance measurement filter is provided at the request receiving port.

In the above embodiment, the controller,
Although the business logic and the presentation have been described as being Java-based, they may be other than Java-based.

Further, in the above-described embodiment, the object of measuring the performance of the Web application is defined by the measurement information definition file and narrowed down. However, when an HTTP request is given, the Web request is irrelevant regardless of the request type. The performance of the application may be measured.

Further, the trigger of the measurement is not limited to the operation of the button, and may be the operation of the link destination (click).

Furthermore, in the above-described embodiment, the one for the Web application server is shown. However, in the system which employs the client / server system and requires a server having the same function as the Web application server, The invention can be applied. Although the term "Web application server" is used in the title of the invention and the like, application servers of the same type as the Web application server are also included.

[0074]

As described above, according to the web application processing performance measuring method and the web application server according to the present invention, the application developer uses the application processing performance measuring function in the web application body (controller, business logic and presentation). It is possible to measure the processing performance of the Web application body without including it.

[Brief description of drawings]

FIG. 1 is an explanatory diagram of a software configuration of a web application server according to an embodiment.

FIG. 2 is an explanatory diagram showing a basic configuration of a web application server system.

FIG. 3 is an explanatory diagram showing a relationship of software components of the web application server according to the embodiment.

FIG. 4 is an explanatory diagram showing a functional configuration of a performance measurement filter according to an embodiment.

FIG. 5 is an explanatory diagram showing a configuration example of a measurement information definition file of the embodiment.

FIG. 6 is a flowchart showing processing of a request determination function unit and a performance measurement start function unit of the performance measurement filter of the embodiment.

FIG. 7 is an operation sequence diagram of the Web application server according to the embodiment.

FIG. 8 is an explanatory diagram showing an example of a screen used for explaining a specific operation of the embodiment.

9 is an explanatory diagram showing parameter names and parameter values associated with respective buttons on respective screens in FIG. 8. FIG.

10 is an explanatory diagram showing an example of contents of a measurement information definition file related to a plurality of screens in FIG.

FIG. 11 is a flowchart showing the processing of the request determination function unit and the performance measurement start function unit of the performance measurement filter of the embodiment in relation to the content example of the measurement information definition file of FIG.

FIG. 12 is an explanatory diagram showing a graph and the like of an analysis result example of the performance management package of the embodiment.

[Explanation of symbols]

10 ... Web application server, 11 ... Web client, 13 ... Performance management package, 1
4 ... Controller (servlet), 15 ... Business logic (EJB), 16 ... Presentation (JS
P), 17 ... Performance measurement filter, 31 ... Measurement information definition file reading function section, 32 ... Measurement information definition reading area, 33 ... Request determination function section, 34 ... Performance measurement start function section, 35 ... Performance measurement end function section, 40 ... Measurement information definition file.

Claims (8)

[Claims] 1. A performance measurement filter is provided, and by the filtering function of this performance measurement filter, the controller, when accepting a corresponding request from a client,
Web consisting of business logic and presentation
Before executing the processing of the application body, Web
A method for measuring performance of a web application, characterized in that performance measurement of the application is started, and performance measurement of the web application is ended when processing of the main body of the web application ends. 2. The performance measurement filter issues a start request and an end request for performance measurement of a Web application to a performance management package that measures a usage rate of system resources. Web application processing performance measuring method. 3. The performance measurement filter has a measurement information definition file that defines a performance measurement target, and the performance measurement of a Web application is performed when a request relating to the performance measurement target defined in the measurement information definition file is accepted. The Web application processing performance measuring method according to claim 1 or 2, characterized in that: 4. The measurement information definition file is a list of a measurement parameter name, a combination of measurement parameter values, and a measurement processing name corresponding to the combination of measurement parameter values. 4. The Web application processing performance measuring method according to claim 1, wherein the name and its name can be arbitrarily defined. 5. A Web application server that executes a Web application in response to a request from a client and sends a response to the client, including a Web application body including a controller, business logic, and a presentation, and a performance measurement filter. By the filtering function of the performance measurement filter, when the corresponding request is received from the client, the performance measurement of the Web application is started before the processing of the main body of the Web application is executed.
b When the processing of the application main body ends, the performance measurement of the Web application ends.
eb application server. 6. The performance measurement filter according to claim 5, wherein the performance measurement package issues a start request and a finish request for performance measurement of a Web application to a performance management package that measures a usage rate of system resources. Web application server. 7. The performance measurement filter has a measurement information definition file that defines a performance measurement target, and the performance measurement of a Web application is performed when a request related to the performance measurement target defined in the measurement information definition file is accepted. 7. The Web application server according to claim 5, wherein the Web application server executes. 8. The measurement information definition file is a list of measurement parameter names, combinations of measurement parameter values, and measurement processing names corresponding to the combinations of measurement parameter values. The Web application server according to any one of claims 5 to 7, wherein the name and its name can be arbitrarily defined.