Improve Revo front end performance

Quote from: AMDbuilder at Mar 09, 2012, 02:12 AM

The other question you may want to ask (granted this IS environment specific) is how well the sites handle concurrent traffic.

If you run the shell: ab -n 100 -c 10 http://www.domain.com/

(100 requests with a max of 10 concurrently - add " > test1.txt &" to the end to write the output to file)

I wouldn't go too crazy with the requests as it will tax any server, but this should give us another test to help measure how MODX is doing and more importantly how we can improve it.

Interesting idea. Just tried it on 2 sites (one drupal with kenters.com content, one clean MODX with caching enabled).

MODX

Server Software:        Apache/2.2.16
Server Hostname:        ***********
Server Port:            80

Document Path:          /
Document Length:        129 bytes

Concurrency Level:      10
Time taken for tests:   4.584 seconds
Complete requests:      100
Failed requests:        0
Write errors:           0
Total transferred:      57900 bytes
HTML transferred:       12900 bytes
Requests per second:    21.82 [#/sec] (mean)
Time per request:       458.367 [ms] (mean)
Time per request:       45.837 [ms] (mean, across all concurrent requests)
Transfer rate:          12.34 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    2   7.9      0      41
Processing:   140  444 224.3    400    1112
Waiting:       74  428 215.5    390     969
Total:        140  446 224.1    406    1113

Percentage of the requests served within a certain time (ms)
  50%    406
  66%    500
  75%    543
  80%    648
  90%    782
  95%    908
  98%   1069
  99%   1113
 100%   1113 (longest request)

Drupal

Server Software:        Apache/2.2.16
Server Hostname:        ************
Server Port:            80

Document Path:          /
Document Length:        11365 bytes

Concurrency Level:      10
Time taken for tests:   2.459 seconds
Complete requests:      100
Failed requests:        0
Write errors:           0
Total transferred:      1187600 bytes
HTML transferred:       1136500 bytes
Requests per second:    40.66 [#/sec] (mean)
Time per request:       245.923 [ms] (mean)
Time per request:       24.592 [ms] (mean, across all concurrent requests)
Transfer rate:          471.60 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   1.0      0       4
Processing:    55  244 110.5    232     582
Waiting:       44  227 113.0    209     581
Total:         55  244 110.5    232     582

Percentage of the requests served within a certain time (ms)
  50%    232
  66%    271
  75%    296
  80%    339
  90%    416
  95%    485
  98%    535
  99%    582
 100%    582 (longest request)

Althought it would be good to see improved frontend speed in MODx, there is a trade-off which I can live with. The fact that MODx is not theme based but tag based will impact speed but this is something I can live with. Drupal is theme based which makes it more easier for them to cater for caching a page and as someone stated before MODx caches by elements since you can have some items uncached.

How would you turn on MODX sessions to be file-based?

Quote from: gernot_ebenlechner at Sep 20, 2012, 04:45 PM

How would you turn on MODX sessions to be file-based?

Set the System Setting with the key session_handler_class to an empty string and MODX will use the session handling settings from your PHP configuration.

When friendly url enabled, this trick will speed up the frontend a little bit https://forums.modx.com/thread/80511/improve-static-files-performance-when-friendly-url-enabled-htaccess