There are many caching frameworks in Java like EHCache and OSCache. These are essentially in-memory caches. Meaning it uses the same java process memory to cache data. You can imagine them as HashMap or HashTable in your own java program. This frameworks work just fine for caching data in size of few GBs. In this post we will see Memcached which is another caching framework that uses distributed architectural approach as a result of which large amount of data can be stored.
As mentioned in background section memcached uses distributed architectural approach. It is essentially different process (server). Then you have memcached client (essentially jars) that you import in your java program which talks with memcached server. You can have multiple memcached servers . No server is aware of other servers. It is the client that is aware of which server has a particular key stored.
Starting/Stopping Memcached server
You can use following commands in Linux
- Start Server : /etc/init.d/memcached start
- Stop Server : /etc/init.d/memcached stop
- Restart Server : /etc/init.d/memcachedrestart
- Check status : /etc/init.d/memcached status
- memcached.exe start
- memcached.exe stop .... etc
- memcached.exe -d install
To see list of all commands type
- memcached.exe -help
Go ahead . Play around with the command line. Also if the default port i.e 11211 is used by some other process on your machine change the port of your memcached server.
Note : By default server will start up on port 11211 with 64 MB of memory.
Connecting to Memcached server
You can do telnet to your localhost and port to connect to memcached server. Eg.
C:\Users\athakur\Softwares\memcached>telnet localhost 11211
This will connect to your memcahcahed server. You can type "stats" to get the server statistics like PID of the process, uptime etc
You can type quit to exit from the telnet.
Using command line to get Memcahched detailsMemcached puts your data into different "slabs" depending on the data size. This optimized memory allocation and reduces fragmentation. You can see these slabs with command -
- stats slabs
- stats items
- stats cachedump [slabID] [number of items, 0 for all items]
stats cachedump 2 0
ITEM TEST_DATA_KEY [16 b; 1420207128 s]
This will list down all data items in slab 2. Text following the ITEM keyword is the key of the data. To get the value of the key you can simply do
- get keyName
VALUE TEST_DATA_VALUE 0 68
To delete data by it's key you can simply do
- delete keyName
Note the subsequent get call gives nothing as the data is deleted.
You can clear the entire cache with following command
telnet localhost 11211