View State Caching for ASP.NET Performance Optimization

ASP.NET View State is a powerful feature of ASP.NET that provides a client-side state management mechanism. It helps preserve page and control values between complete round trips for client requests. This gives a state full programming capability over a stateless protocol such as HTTP.

ASP.NET View State is stored in a hidden field on the page as an encoded Base64 string, as part of every response sent to the client, and is also returned to the server by the client as part of a post back.

<input id = "__VIEWSTATE"
       type = "hidden"
       name = "__VIEWSTATE"

Although very useful, ASP.NET View State does come with a few issues that you need to understand and resolve. They are discussed below.

  1. ASP.NET View State is often heavy: When your ASP.NET application has a lot of rich and heavy controls and widgets on its pages, a lot of data is traveling back and forth between your browser and the webserver. This heavy payload results in performance degradation of ASP.NET application and high bandwidth cost.
  2. ASP.NET View State is a security risk: It can also pose a security risk when sending confidential data as part of the view state to the client. This data is vulnerable to attacks and can be tempered by an attacker which is a serious security threat. You can encrypt the ASP.NET View State data but this is again going to have a performance cost to it.

NCache for ASP.NET View State

One way you can resolve ASP.NET View State issues is by storing the actual ASP.NET View State on the Web server and sending a unique token (or ID) in place of it to the browser so the browser can send this token back to the web server next time. The web server then uses this token to find the right ASP.NET View State in its store. Below is an example of a token being used in place of ASP.NET View State.

<input type = "hidden"
       name = "__VIEWSTATE"
       id = "__VIEWSTATE"
       value = "vs:cf8c8d3927ad4c1a84da7f891bb89185" />

Although ASP.NET View State can be stored on the webserver, it's not ideal when your ASP.NET application is running in a load-balanced web farm since the next HTTP request might come to another web server. Therefore, you must store the ASP.NET View State in a shared store that is accessible from all the web servers.

The best place to store ASP.NET View State on the server is in a distributed cache. This way, not only can you have a common store for all web servers, but you also have an extremely fast and scalable in-memory store as compared to SQL Server database or other storage options.

Distributed Cache storing ASP.NET View State - NCache
Figure 1: Distributed Cache storing ASP.NET View State

NCache is an extremely fast and scalable distributed cache for .NET/.NET Core, Java, and Node.js. It also lets you store ASP.NET View State to solve the issues described above.

Configure ASP.NET ViewState in NCache

To configure ASP.NET View State you need to install the AspNet.ViewState.NCache NuGet package as a pre-requisite. Then you need to configure App_browser file with NCache Plug page adapters and configure the web.config file in your application to register the configuration section for View State and specify the settings for the registered config section. Refer to the NCache ASP.NET View State docs for step-by-step configuration.

If the same cache is being used for View State caching and other data, you can fetch the View State data by using NC_ASP.net_viewstate_data tag as:

Hashtable allViewStateData = cache.GetByTag(new Tag("NC_ASP.net_viewstate_data"));

Benefits of Caching ASP.NET View State on the Server

You gain the following benefits by caching your ASP.NET View State in NCache.

  1. Improve ASP.NET Performance: NCache reduces the request/response payload which improves the overall request time.
  2. Reduce Bandwidth Cost: Smaller payload also means a significant reduction in bandwidth consumption cost. This could save you a lot of money.
  3. Security: Now that ASP.NET View State encoded string is not sent to the browser, there are no longer any security risks.
  4. Fast & Scalable ASP.NET View State Storage: NCache is an extremely fast and scalable distributed cache. This means your ASP.NET never faces any scalability bottlenecks due to ASP.NET View State storage.
  5. ASP.NET View State Reliability thru Replication: NCache replicates all data in the distributed cache intelligently. This means you don't lose any ASP.NET View State even if a cache server goes down.

Advanced ASP.NET View State Caching Features in NCache

NCache provides you a rich set of features for caching and managing ASP.NET View State. Below is a list of them.

  1. Minimum size threshold: NCache allows you to specify a minimum size of ASP.NET View State. Any View State smaller than this is not cached. This enables you to only cache heavy View State.
  2. Link ASP.NET View State with Session State: You can link an ASP.NET View State with your Session State. This way, when the user session expires, all his view states are automatically removed from the cache.
  3. Page-level max count threshold: You can configure how many view states should be kept for a given page in a FIFO manner. This way, the oldest view state is removed whenever a new view state is created for this page. This optimizes your memory consumption in the cache server by not caching view states that you would never need.
  4. Session level max count threshold: Similar to the page level, you can specify the maximum view state count for a user session in a FIFO manner with maxViewStatesPerSession. This way, the oldest view state is removed whenever a new view state is created.
  5. Page-level and session-level settings: You can specify all of the above settings differently for each page or keep them common to all sessions.


As you have seen, NCache allows you to cache ASP.NET View State on the server to optimize your ASP.NET performance. Additionally, NCache provides you a rich set of features for managing your ASP.NET View State more efficiently in the cache. This allows you to develop complex applications and use these features to handle a variety of scenarios.

What to Do Next?

Signup for monthly email newsletter to get latest updates.

© Copyright Alachisoft 2002 - . All rights reserved.