Browse Prior Art Database

Method to associate and use caching metadata with Application templates

IP.com Disclosure Number: IPCOM000246644D
Publication Date: 2016-Jun-23
Document File: 3 page(s) / 66K

Publishing Venue

The IP.com Prior Art Database

Related People

Mithlesh Thukral: INVENTOR [+2]

Abstract

Application templates are way to abstract a service which can be deployed and replicated to create new instances. Every application has a different IO pattern. Caching improves application performance using high speed memory devices and it's impacted by the application IO patterns. This invention defines a way for the caching metadata to be stored along with application template and used whenever the template is deployed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

Method to associate and use caching metadata with Application templates

Mithlesh Thukral

Niranjan Pendharkar

Abstract

Application templates are way to abstract a service which can be deployed and replicated to create new instances. Every application has a different IO pattern. Caching improves application performance using high speed memory devices and it's impacted by the application IO patterns. This invention defines a way for the caching metadata to be stored along with application template and used whenever the template is deployed.

Problem Statement

Caching overview:
Every application has a different IO access pattern. The caching improves application performance using high speed storage devices. But the caching impact is very dependent on the application IO pattern. As the application runs, the caching subsystems tune themselves and cache only the "hot data". Application templates: In case of large deployments, application templates are defined which contain the application, associated software resources, operating systems and hardware profiles. These are in a template because when there is need to scale or deploy the application they can be deployed in a simple and quick manner. It avoids the need to setting up each component and configuring it for every instance.

The problem statement:

In case of application template being deployed, each time the caching subsystem has to wait and determine the "hot data" using the IO patterns of application. This happens after the application is up and running. Till that point the caching benefits are not 100%. This again has to be done for every deployment of the template.

1

© 2016 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.


Page 02 of 3

Publication Description

Terms used:
Caching metadata: Data containing information about block, files, regions of the file system or storage device which is cached. Information like the access frequency, "heat" and other parameters on which caching algorithm decides caching decision is also part of caching metadata.

Application template: A template which defines all the software and hardware components which make up a particular application which is on interest. The settings of various components can also be part of the same or associated template. For example Virtual Business Service.

Invention Description:
This invention proposes a method to associate the Caching metadata of an application along with the application template.

What needs to be stored:
Caching metadata is to be stored with the application Template.

The caching metadata can be in form of block numbers if the caching is being performed at block level. These block numbers would relative to the storage device start and hence can be reused.

If the caching is performed with filesystem above...