Magento Site Performance Optimization

Chapter 1
Doubling the CPU
Our first test will be to double the CPU in order to see whether the CPU should be in
the balance while choosing your hardware. We will not double the frequency as we
don't have a 3.6 GHz core to give at our virtual machine (VM); we will add another
1.8 GHz core instead.
While the server was under stress, we use the command on it in order to see the
CPU usage. The www-root user, which is in charge of running the webserver, does
use 100 percent of the available CPU, distributed across several processes. However,
did the results improve? The default performance in terms of time and requests
per second is shown as follows:
Document Path:
/magento/index.php/furniture/living-room.html/
Document Length:
Concurrency Level: 5
Time taken for tests:
Complete requests: 100
Failed requests: 0
Write errors: 0
Total transferred:
HTML transferred:
Requests per second:
Time per request:
Time per request:
requests)
Transfer rate:
36778 bytes
137.210 seconds
3725700 bytes
3677800 bytes
0.73 [#/sec] (mean)
6860.487 [ms] (mean)
1372.097 [ms] (mean, across all concurrent
26.52 [Kbytes/sec] received
As you can see, Time per request reaches a new peak at 6860.487 ms. However,
this time no requests have failed. Therefore, we can conclude that the CPU will not
necessarily directly improve the needed time to load a page, but can drastically
improve the number of served pages.
Doubling the RAM
In this second test, we use a single CPU 1.8 Ghz but double the RAM. The new
amount of available RAM is 1 GB. The default performance, after doubling the RAM,
in terms of time and requests per second is shown as follows:
Document Path:
/magento/index.php/furniture/living-room.html/
Document Length: 36778 bytes
Concurrency Level: 5
Time taken for tests: 94.596 seconds
[ 11 ]
www.it-ebooks.info