Web Site Performance Test
At last! You have finished that project that made you loose your sleep, friends, or I don't know what else... A really "boring" and very time consuming step is ... yes you know... Testing!
There are a lot of things that you want to test. I will complete the list through time... But now I would like to notice 2 very important tests:
1. Put your enemies to test your site. Make them find whatever bug, fault anything that they don't like. Make sure you Thank them then.
2. MAKE a performance test: If you
want to start with the big picture—how well the server copes with
demand—software like ApacheBench and Siege
will run benchmarks on your Web
server, reporting on how many requests can be handled per second, which is
the standard measuring tool for a site’s performance. Once you start checking your site’s performance, you will fi nd that big, systemwide changes you make
will have the greatest impact. These include:
■ Changing the server hardware: increasing memory, installing faster hard
drives, and using faster processors
■ Changing the demands on the server: disabling unnecessary features,
putting fewer users or sites on a single server, and balancing loads across
multiple servers
■ Caching the PHP output
■ Caching the PHP execution
■ Caching the database results
If you think about the process involved for handling the request of a PHPMySQL
based page, you’ll see three areas where caching can be applied
(Figure 1.4). First, if the database or PHP is caching the results of a database
query, then that query will not need to be executed with each request.
Second, by default, each request of a PHP script requires that the PHP code
be executed as if it had never been run before. By applying an opcode cache
such as the Alternative PHP Cache (APC), the PHP code
itself is cached by the system, making that execution faster. Finally, the end
result is that HTML is sent to the Web browser. If you can cache the dynamically
generated HTML, then no PHP code will be executed at all, no database
queries are required, and the request itself becomes as fast as a request for
a static HTML page.
There are a lot of things that you want to test. I will complete the list through time... But now I would like to notice 2 very important tests:
1. Put your enemies to test your site. Make them find whatever bug, fault anything that they don't like. Make sure you Thank them then.
2. MAKE a performance test: If you
want to start with the big picture—how well the server copes with
demand—software like ApacheBench and Siege
will run benchmarks on your Web
server, reporting on how many requests can be handled per second, which is
the standard measuring tool for a site’s performance. Once you start checking your site’s performance, you will fi nd that big, systemwide changes you make
will have the greatest impact. These include:
■ Changing the server hardware: increasing memory, installing faster hard
drives, and using faster processors
■ Changing the demands on the server: disabling unnecessary features,
putting fewer users or sites on a single server, and balancing loads across
multiple servers
■ Caching the PHP output
■ Caching the PHP execution
■ Caching the database results
If you think about the process involved for handling the request of a PHPMySQL
based page, you’ll see three areas where caching can be applied
(Figure 1.4). First, if the database or PHP is caching the results of a database
query, then that query will not need to be executed with each request.
Second, by default, each request of a PHP script requires that the PHP code
be executed as if it had never been run before. By applying an opcode cache
such as the Alternative PHP Cache (APC), the PHP code
itself is cached by the system, making that execution faster. Finally, the end
result is that HTML is sent to the Web browser. If you can cache the dynamically
generated HTML, then no PHP code will be executed at all, no database
queries are required, and the request itself becomes as fast as a request for
a static HTML page.
Σχόλια