![]() %CPU - Generally LSWS's CPU usage is low.(LSWS's process is called lshttpd.) A couple of these outputs are useful for determining if the current LSWS installation could benefit from access to more cores: How do I know if it's enough? There is a litespeed document for this.Ī top command will reveal important information about how different processes are using server resources. ![]() It also has a trial license 2 worker feature, you can test it for 14 days. If 1 worker is not enough, there is always a chance to upgrade to 2 workers. Similarly, LiteSpeed ADC may be configured to honor these same browser cache headers, thereby storing static files directly in the ADC's cache file location, once they are retrieved from a backend server.Click to expand.If there are websites with html content without database, 1 worker will suffice. These headers are used by the frontend browser to cache static content requested from the server. The mod_expires directive generates browser cache headers, such as Cache-Control: max-age=533280, Expires: Sun, 23:02:37 GMT, etc. Here's how to enable cache for static files on your ADC: This would avoid having to fetch the static files from backend servers every time a request is handled. However, in the case where an ADC is used in front of your backend servers, it may make sense to use the ADC like a CDN, and cache the static files at that level. Static files can be served directly from the web server with the best performance, so under normal circumstances, serving static files from cache would be a waste of resources and unnecessary steps. LiteSpeed's LSCache engine was designed to cache dynamic pages. If you don't see X-LSADC-Cache: hit or X-LSADC-Cache: miss, then there is a problem with the LSCache configuration.This means the page is being served by LSCache and is configured correctly. Reload the page and you should see X-LSADC-Cache: hit in the response header.(for example), this means the page had not yet been cached, but that LiteSpeed has now stored it for future use. X-LiteSpeed-Cache-Control:public,max-age=1800 Leave the other settings as-is and click Save.Set Storage Path to the directory where you would like to store cache objects.Navigate to Configuration > Server > Cache and click Edit in the Cache Storage Settings section.If there is no cache plugin available for your application yet, you can use rewrite rules to control LSCache. On the backend web server, you will need to install a LiteSpeed Cache plugin. Copy LSCache rewrite rules from backend server to Web ADCĪll of these steps can be executed from within the ADC WebAdmin Console.Enable caching in the virtual host cache settings. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |