Static learning notes for PHP pages II: static pages

This is my learning notes written in the static process of my PHP Technology page. I hope this will help you. 1. Static advantages (1) meet the SEO (SearchEngineOptimization) search engine optimization requirements and are more easily crawled by search engines (2) reduces the pressure on databases and servers (3) accelerate access (page

This is my learning notes written in the static process of my PHP Technology page. I hope this will help you. 1. Static advantages (1) meet the SEO (SearchEngine Optimization) search engine Optimization requirements and are more easily crawled by search engines (2) reduces the pressure on databases and servers (3) accelerate access (page

This is my learning notes written in the static process of my PHP Technology page. I hope this will help you.

1. Static advantages

(1) comply with the SEO (SearchEngine Optimization) search engine Optimization requirements, more easily captured by the Search Engine

(2) reducing the pressure on databases and servers

(3) speed up access (the page access speed can be tested using the apache AB tool)

2. Static Page Classification

(1) Real static: Convert the PHP page into an HTML page, and the database will not be operated upon access.

(2) pseudo-static: only static URLs are used, but database operations are still performed.

3. Use Apache AB Tool

(1) test command: AB-n 10-c 10 http://www.google.com/

(2) Main parameters:

-N connections, number of connections of a customer

-C client count

(3) test results:

This is apacheloud, Version 2.0.40-dev <$ Revision: 1.146 $> apache-2.0Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/Copyright 1997-2005 The Apache Software Foundation, http://www.apache.org/ Benchmarking www.google.com (be patient )..... done Server Software: GWS/2.1 Server Hostname: www. google. comServer Port: 80 Document Path:/Document Length: 230 bytes Concurrency Level: 10/* duration of the entire test */Time taken for tests: 3.234651 seconds/* number of completed requests */Complete requests: 10/* Number of Failed requests */Failed requests: 0 Write errors: 0Non-2xx responses: 10Keep-Alive requests: 10/* network transmission volume in the entire scenario */Total transferred: 6020 bytes /* The amount of HTML content transmitted throughout the scenario */HTML transferred: 2300 bytes/* One of the most important indicators, which is equivalent to the number of transactions per second in LR, the mean in the following brackets indicates that this is an average value */Requests per second: 3.09 [#/sec] (mean)/* The second indicator that everyone cares most about, which is equivalent to the average transaction response time in LR, the mean in the brackets below indicates that this is an average value */Time per request: 3234.651 [MS] (mean)/* This does not know what it means, please leave a message if you know, thanks ^_^ */Time per request: 323.465 [MS] (mean, messaging SS all concurrent requests)/* Average network traffic per second, it can help eliminate the problem of long response time due to excessive network traffic */Transfer rate: 1.55 [K Bytes/sec] lost Ed/* decomposition of the time consumed on the network, the specific algorithm of each data is not very clear */Connection Times (MS) min mean [+/-sd] median maxConnect: 20 318 926.1 30 2954 Processing: 40 2160 1462.0 3034 3154 Waiting: 40 2160 1462.0 3034 Total: 60 2479 1276.4 3064 3184/* the following content shows the response of all requests in the entire scenario. Each request has a response time in the scenario. 50% of the user response time is less than 3064 milliseconds, and 60% of the user response time is less than 3094 milliseconds, the maximum response time is less than 3184 Ms */Percentage of the requests served within a certain time (MS) 50% 3064 66% 3094 75% 3124 80% 3154 90% 3184 95% 3184 98% 3184 99% 3184 100% 3184 (longest request)