Supermap iserverjava 6R extended field development and stress testing-points of judgment (2)

There is always no such thing when it is sent out, so the text will be sent in two paragraphs:

(3) export as jar package, put under the Supermap iserverjava 6R installation directory \ webapps \ iServer \ WEB-INF \ Lib.

(4) Find \ webapps \ iServer \ WEB-INF \ config \ Services under the Supermap iserverjava 6R installation directory. XML file, and then add component and interface configuration in the corresponding module. For details, refer to the configuration management module of Supermap iserverjava 6R.

Component Configuration

Configure component <component class = "com. Zhangwei. Extend. inwithcomponent" interfacenames = "inwith" name = "inwithcom" providers = "ugcdataprovider-World"> </component>
Configure interface <interface class = "com. Zhangwei. Extend. iswithinservlet" name = "inwith"> </interface>

2. Use Apache's test tool AB to test the URL as follows: extended test URL: http: // 172.16.2.23: 8090/iServer/services/inwithcom/inwith? In = {"resultsetting": {"returnedgefeatures": True, "success": True, "returnedgeids": True, "returnnodefeatures": True, "returnnodegeometry": True, "returnnodeids": True, "returnpathguides": True, "returnroutes": true}, "turnweightfield": "turncost", "weightfieldname": "length"} test command: test command AB-N 10000-C 100 http: // 172.16.2.23: 8090/iServer/services/inwithcom/inwith? In = {"resultsetting": {"returnedgefeatures": True, "success": True, "returnedgeids": True, "returnnodefeatures": True, "returnnodegeometry": True, "returnnodeids": True, "returnpathguides": True, "returnroutes": true}, "turnweightfield": "turncost", "weightfieldname": "length"} Test Result: test Result c: \ Program Files \ Apache Software Foundation \ apache2.2 \ bin> AB-N 10000-C 100 http: // 172.16.2.23: 8090/is
Withcom/inwith? In = {"resultsetting": {"returnedgefeatures": True, "returnedgegeometry": True, "returnedgeids"
Features ": True," returnnodegeometry ": True," returnnodeids ": True," returnpathguides ": True," returnroutes ": TR
Eld ":" turncost "," weightfieldname ":" length "}
This is apachetings, Version 2.3 <$ revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to the Apache Software Foundation, http://www.apache.org/

Benchmarking 172.16.2.23 (Be patient)

Server Software: APACHE-Coyote/1.1
Server Hostname: 172.16.2.23
Server port: 8090

Document path:/iServer/services/inwithcom/inwith? In = {resultsetting: {returnedgefeatures: True, R
: True, returnedgeids: True, returnnodefeatures: True, returnnodegeometry: True, returnnodeids: True, returnpathg
Routes: true}, turnweightfield: turncost, weightfieldname: length}
Document length: 15116 bytes
// The concurrency granularity is 100, that is, 100 requests are sent each time.
Concurrency level: 100
Time taken for tests: 2.606 seconds // total test time
Complete requests: 173 // number of completed requests
Failed requests: 1 // number of failed requests
(CONNECT: 0, receive: 0, Length: 1, exceptions: 0)
Write errors: 0
Total transferred: 2654717 bytes // total amount of transmitted data
HTML transferred: 2630183 bytes // total amount of HTML data transmitted
Requests per second: 66.77 [#/sec] (mean) // average number of transactions processed per second, that is, the number of requests.
Time per request: 1497.787 [MS] (mean) // average transaction request time, that is, the time consumed by each request
Time per request: 14.978 [MS] (mean, messaging SS all concurrent requests) // average actual running time of each request
Transfer Rate: 1006.20 [Kbytes/sec] received // The average network traffic per second. This helps you determine whether the response time is prolonged due to excessive network traffic.

Connection times (MS)
Min mean [+/-SD] median Max
Connect: 0 0 0.5 0 2
Processing: 20 647 742.2 276 2543
Waiting: 20 647 742.2 276 2543
Total: 20 647 742.2 276 2544
// The following content shows the response of all requests in the entire scenario.
Percentage of the requests served within a certain time (MS)
50% 313
66% 872
75% 1217
80% 1472
90% 2119
95% 2279
98% 118
99% 29
100% 539 (longest request)

3. Test Result Analysis

When I first came into contact with the AB tool, most of the analysis parameters were copied from the Internet. According to the analysis results, about 66 requests are processed per second, which takes a long time. However, in the case of 10000 access and 100 concurrency, the access efficiency is acceptable. Further optimization is available, for example:

(1) The component layer makes it easy to perform two queries for the test data. It queries the output point and the surface geometric object. The more practical interface is to transmit the point parameter, the surface object may be retrieved by query or directly transmitted. The better case is that the directly transmitted parameters are passed to the background. This increases the transmission data volume but reduces the query time and improves the efficiency, in addition, the user interaction process may involve different situations, so directly passing parameters may be more efficient and interactive. Of course, you need to consider it based on the situation.

(2) passing parameters is directly encapsulatedCodeMedium, may consume efficiently.

(3) You can consider multiple servlets for processing, which is more in line with the characteristics of the Tomcat container's processing servlet, but this is not considered here, and will be added later.

The above is an API test for your own encapsulation, which does not represent the actual request processing concurrency of Supermap iserverjava 6R.