Continuing our discussion of the Sitecore Rocks Manage tool, today we will be covering the Caches interface. Having an understanding of how and what Sitecore Caches is an integral skill when configuring, tuning and troubleshooting performance. The Caches interface will provide us with more information than we've previously had available to us with the Sitecore cache page.
If we don't already have the Manage tool open, right click the Sitecore instance, in this case the Jetstream node, in the Sitecore Explorer and select the "Manage" menu item.
With the Caches interface open we will notice, similar to the Sitecore cache page, each of the caches for the sites currently configured in our instance of Sitecore. The number of columns is what differentiates the Caches interface. Here are the available columns. The bold columns are new.
What also differentiates the Caches interface is that we have the ability to clear a single cache as opposed to all caches. To do so, simply select the cache you would like to clear and right click to open the context menu. From here we can either clear the single cache or all caches.
Another nice feature of the Caches tool is the ability to explore the caches. To explore a cache, select a cache and open the context menu by right clicking the item and selecting "Explore Cache." The Explore Cache dialog lists out each items key, size, last accessed and data. We can filter the list of items in the cache by entering a value in the filter textbox, as well as evict a single item from a cache by right clicking an item and selecting "Remove."
Using the Caches interface of the Sitecore Rocks Manage tool can provide insight into Sitecore caches that was previously unavailable via the standard methods. I would encourage anyone who works with Sitecore to give this interface a try when configuring, tuning or troubleshooting performance.
Getting to know about the caches in detail is really cool feature. Mostly we need to look at the cache configurations on the Prod sites or servers. Is there any way by which we can use this feature on the production server/site....
Good question from Summit Phadke, this would make an excellent admin and production debugging tool.