Table of ContentsLibraryView in Frames

Cache hits and misses

There are several types of cache hits and misses. Factors include whether data is present in the cache, whether the attribute cache timeout has been exceeded, and whether the file's attributes have changed.

When a client makes a read request, if the relevant block is cached in the FlexCache volume, the data is read directly from the FlexCache volume. This is called a cache hit. Cache hits are the result of a previous request.

A cache hit can be one of the following types:
  • Hit

    The requested data is cached and no verification is required; the request is fulfilled locally and no access to the origin system is made.

  • Hit-Verify

    The requested data is cached but the attribute cache timeout has been exceeded, so the file attributes are verified against the origin system. No data is requested from the origin system.

If data is requested that is not currently on the FlexCache volume, or if requested data has changed since it was cached, the caching system loads the data from the origin system and then returns it to the requesting client. This is called a cache miss.

A cache miss can be one of the following types:
  • Miss

    The requested data is not in the cache; it is read from the origin system and cached.

  • Miss-Verify

    The requested data is cached, but the file attributes have changed since the file was cached; the file is ejected from the cache and the requested data is read from the origin system and cached.