Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
litespeed_wiki:config:compare_pagespeed_and_lscache [2017/09/13 15:57] Eric Leu [Testing Method] |
litespeed_wiki:config:compare_pagespeed_and_lscache [2017/09/13 18:15] Eric Leu [Conclusion] |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| - mod_pagespeed rules | - mod_pagespeed rules | ||
| - <code>pagespeed FileCachePath /tmp/lshttpd/pagespeed; | - <code>pagespeed FileCachePath /tmp/lshttpd/pagespeed; | ||
| - | pagespeed RewriteLevel CoreFilters; </code> | + | pagespeed RewriteLevel CoreFilters; </code> |
| + | - htop v2.0.2 | ||
| * For verify pagespeed is working, you can follow [[https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:enable_pagespeed#verify_pagespeed_is_enabled | this article]]\\ | * For verify pagespeed is working, you can follow [[https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:enable_pagespeed#verify_pagespeed_is_enabled | this article]]\\ | ||
| Line 30: | Line 31: | ||
| ==== Testing Method==== | ==== Testing Method==== | ||
| - | There are four cases in our experiment: | + | There are four cases in our experiment:\\ |
| - | Case 1: without lscache and mod_pagespeed\\ | + | Case 1: Without lscache and mod_pagespeed\\ |
| Case 2: Only use mod_pagespeed\\ | Case 2: Only use mod_pagespeed\\ | ||
| Case 3: Only use lscache\\ | Case 3: Only use lscache\\ | ||
| - | Case 4: Use both lscache and mod_pagespeed. We send request command with wordpress URL from client side to the Web server. \\//Regardless of whether testing with lscache or mod_pagespeed, we followed the same procedure. // | + | Case 4: Use both lscache and mod_pagespeed\\ |
| - | - The method to test these web servers uses ApacheBench (an HTTP server benchmarking tool). In each test, 10,000 requests are made for a 68 KB size page | + | //Regardless of whether testing with lscache or mod_pagespeed, we followed the same procedure. // |
| + | |||
| + | - The method to test the web servers uses ApacheBench (an HTTP server benchmarking tool). In each test, client side send 10,000 requests to the server's webpage which size is 68 KB. | ||
| - Before each test the web server in question was restarted to clear out any potential caching or other issues that may interfere with results. | - Before each test the web server in question was restarted to clear out any potential caching or other issues that may interfere with results. | ||
| - Each test was run with the same concurrent numbers of requests to gauge performance at different cases. | - Each test was run with the same concurrent numbers of requests to gauge performance at different cases. | ||
| Line 60: | Line 63: | ||
| ===CPU Load=== | ===CPU Load=== | ||
| - | * Compare all cases by 1 min CPU Load, we can see CPU Load is higher if your mod_pagespeed is enabled than other cases. \\ | + | * We add the requests number for keeping CPU Load until 1 min. Compare all cases by 1 min CPU Load testing, we can see CPU Load is higher if your mod_pagespeed is enabled than other cases. Case 3 & Case 4 which with lscache enabled are not overloading\\ |
| {{:litespeed_wiki:config:cp-4.png?500|}} | {{:litespeed_wiki:config:cp-4.png?500|}} | ||
| Line 71: | Line 74: | ||
| ===== Conclusion ===== | ===== Conclusion ===== | ||
| After going over the benchmark testing of both lscache and mod_pagespeed enabled cases, you may have a better idea of which combination is more suited to your needs. | After going over the benchmark testing of both lscache and mod_pagespeed enabled cases, you may have a better idea of which combination is more suited to your needs. | ||
| - | - Using lscache and mod_pagespeed together are still workable, but it will slow down your page loading time and increase CPU and Memory usage, so if your LSWS include LiteSpeed Cache already, then you don't need to enable pagespeed module for faster | + | - Using lscache and mod_pagespeed together are still workable, but it will slow down your page loading time and increase CPU and Memory usage, so if your LSWS include LiteSpeed Cache already, then you don't need to enable pagespeed module for shorten the loading time |
| - If your LSWS not include Cache, then pagespeed does faster your site around 20%. It will takes part of resources and should be avoided in shared hosting environment. More information, please see [[ https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:enable_pagespeed#using_a_control_panel_in_a_shared_hosting_environment| here]] | - If your LSWS not include Cache, then pagespeed does faster your site around 20%. It will takes part of resources and should be avoided in shared hosting environment. More information, please see [[ https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:enable_pagespeed#using_a_control_panel_in_a_shared_hosting_environment| here]] | ||
| - See this article if you want to [[https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:licenses:add-lscache | Add Caching to an Existing License]] \\ | - See this article if you want to [[https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:licenses:add-lscache | Add Caching to an Existing License]] \\ | ||