Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
litespeed_wiki:lsmcd [2016/04/14 14:11] Rob Holda |
litespeed_wiki:lsmcd [2021/02/17 20:16] (current) Jackson Zhang |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== LiteSpeed Memcached ====== | + | ====== LiteSpeed MemCacheD ====== |
| - | LSMCD is a high-performance, distributed caching system with file-backed shared memory, generic in nature, but originally intended for use in speeding up dynamic web applications by alleviating database load. It is designed as a drop-in replacement for [[http://memcached.org/about|Memcached]], however we also have a few features that Memcached does not: High-Availability and persistence of data. High-Availability means that if one or more of your servers go down, your data can still be accessed and updated as though it was still up. Persistence of data means that there is no need for a database backend. Whatever you put in LSMCD stays in LSMCD unless you say otherwise. | + | LSMCD is a high-performance, distributed memory object caching system, generic in nature, but originally intended for use in speeding up dynamic web applications by alleviating database load. |
| - | LSMCD allows you to take memory from parts of your system where you have more than you need and make it accessible to areas where you have less than you need. With LSMCD, your servers will behave as multiple virtual pools of memory, which you can fine tune allowing you to improve your hit/miss ratio. | + | You can think of it as a short-term memory for your applications. |
| + | LSMCD allows you to take memory from parts of your system where you have more than you need and make it accessible to areas where you have less than you need. | ||
| + | LSMCD also allows you to make better use of your memory. | ||
| + | With LSMCD, all of your servers will look into the same virtual pool of memory. This means that a given item is always stored and always retrieved from the same location in your entire web cluster. | ||
| Also, as the demand for your application grows to the point where you need to have more servers, it generally also grows in terms of the data that must be regularly accessed. A deployment strategy where these two aspects of your system scale together just makes sense. This property remains the same as the number of servers increases. | Also, as the demand for your application grows to the point where you need to have more servers, it generally also grows in terms of the data that must be regularly accessed. A deployment strategy where these two aspects of your system scale together just makes sense. This property remains the same as the number of servers increases. | ||
| Line 13: | Line 16: | ||
| |[[litespeed_wiki:lsmcd:installation|Installation]]|How to install LSMCD| | |[[litespeed_wiki:lsmcd:installation|Installation]]|How to install LSMCD| | ||
| |[[litespeed_wiki:lsmcd:configuration|Configuration]]|Configuration explanation| | |[[litespeed_wiki:lsmcd:configuration|Configuration]]|Configuration explanation| | ||
| - | |[[litespeed_wiki:lsmcd:commands|Commands]]|How to interact with LSMCD| | + | |[[litespeed_wiki:lsmcd:commands|Commands]]|How to interface with LSMCD| |
| - | |[[litespeed_wiki:lsmcd:use_case|Usage Example]]|One example of using LSMCD| | + | |
| + | ===== Separation of individual users' data on shared hosting environment ===== | ||
| + | |||
| + | |[[litespeed_wiki:lsmcd:new_sasl|SASL on LSMCD]]|LSMCD Security Using SASL| | ||
| + | |[[litespeed_wiki:lsmcd:sasl_secure_user_data|Separation of individual users' data: A feature not on Memcached]]|LSMCD Secure User Data Using SASL| | ||
| + | |[[litespeed_wiki:lsmcd:lscwp-sasl|LSMCD + LSCWP + SASL on cPanel]]|Configure LSCWP and LSMCD to use SASL for Secure User Data on shared hosting server| | ||
| + | |[[litespeed_wiki:lsmcd:user_cpanel|LSMCD cPanel Interfacel]]|LSMCD Secure User Data CloudLinux/cPanel Interface| | ||