Introduction To Caching in ASP.Net

Background

Any site is developed for a large number of users, in other words for the same request to work the same for a large number of clients so it is hard to provide the best performance for the server so we use caching.

Introduction

Caching is a state management technique that can store a copy of the data in memory. To increase the performance of the application and improve the access time, caching is used. It exists in temporary storage, in other words when the data is no longer used then it expires. Using a cache we can retrieve the data from a database directly.

Mostly, there are 3 types of caching.

1. Output Caching

When we compile our code it is first it compiled into Microsoft Intermediate Language (MSIL) then The MSIL is converted into Native Code using the JIT Compiler. Now if there is a page that changes frequently then the JIT needs to compile it every time. So, rather than generate a page on each request we can cache the page using Page Output Caching so that it can be accessed from the cache itself.



These pictures show when the first request is generated, the page is cached for the same page request in the future. The page is retrieved in the future. The page is retrieved from the cache rather than regenerating the page.

Now, here I am explaining the Output Cache with an example.

Step 1: Open Visual Studio 2010.

Step 2: Then click on "New Project" > "WEB" > "ASP.NET Empty Web Application".



Step 3: Now click on Solution Explorer.




Step 4: Now right-click on "Add" > "New Item"> "Web From" and add the name of the web form.



Step 5: Write the following code and now here I have used a Drop Down Control, Grid Control, Label Control. and set the client-side time using JavaScript.

  1. <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="WebForm1.aspx.cs" Inherits="Caching.WebForm1" %>  
  2. <%@ OutputCache Duration="30" VaryByParam="None" %>  
  3.   
  4. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">  
  5.   
  6. <html xmlns="http://www.w3.org/1999/xhtml">  
  7. <head runat="server">  
  8.     <title></title>  
  9. </head>  
  10. <body>  
  11.     <form id="form1" runat="server">  
  12. <div>   
  13. <asp:DropDownList ID="DropDownList1" runat="server" AutoPostBack="True"  
  14. onselectedindexchanged="DropDownList1_SelectedIndexChanged">  
  15. </asp:DropDownList>  
  16. <br />  
  17. <br />  
  18.     <asp:GridView ID="GridView1" runat="server">  
  19.     </asp:GridView>  
  20. <br />  
  21.     Server Time:-<asp:Label ID="Label1" runat="server"></asp:Label>  
  22. <br />  
  23. <br />  
  24. Client Time:-  
  25. <script type="text/javascript">  
  26.     document.write(Date())  
  27. </script>  
  28. </div>  
  29. </form>  
  30. </body>  
  31. </html>  
Step 6: Now, I used SQL Server 2008 and I created a database table with a name that is registered in the project database.



Step 7: Code
  1. protected void Page_Load(object sender, EventArgs e)  
  2. {  
  3.     if (!IsPostBack)  
  4.     {  
  5.        Label1.Text = DateTime.Now.ToString();  
  6.        //call the Drop_down_Bind method in pageload  
  7.        Drop_Down_Bind();  
  8.     }   
  9. }  
  10. private void Drop_Down_Bind()  
  11. {  
  12.     //bind the data in drop down  
  13.     SqlConnection con = new SqlConnection(@"server=divs\sqlexpress; Database=Project;uid=sa;password=divya");  
  14.     string query = "select User_name from registeration";  
  15.     SqlDataAdapter da = new SqlDataAdapter(query, con);  
  16.     DataSet ds = new DataSet();  
  17.     da.Fill(ds);  
  18.     DropDownList1.DataSource = ds;  
  19.     DropDownList1.DataTextField = "User_name";  
  20.     DropDownList1.DataBind();  
  21. }  
  22. private void databind(string User_name)  
  23. {  
  24.     //bind the data in gridview  
  25.     SqlConnection con = new SqlConnection(@"server=divs\sqlexpress; Database=Project;uid=sa;password=divya");  
  26.     string query = "select Name,Password,E_mail from registeration where User_name='"+User_name+"'";  
  27.     SqlDataAdapter da = new SqlDataAdapter(query, con);  
  28.     DataSet ds = new DataSet();  
  29.     da.Fill(ds);  
  30.     GridView1.DataSource = ds;  
  31.     GridView1.DataBind();  
  32. }  
  33.   
  34. protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)  
  35. {  
  36.     databind(DropDownList1.SelectedValue.ToString());  
  37. }  
Output



And now if the Other Option of Drop Down List is chosen then we can't get the data back. That happens because when I choose the First Option of the Drop Down List the request goes to the server and the page is saved in cached memory so no matter if we choose the other option, To resolve this problem we need to use VaryByParam="*"and it allows the multiple responses on a single Web Form.

2. Data Caching

Data Caching is basically used for reducing database contention and round-trips, in other words by using Data Caching we store required data in a cache so the Web Server does not send a request to the database for every request so that the database performance will also increased. The data cached is a Full-Featured Cache Engine that enables you to store and retrieve data between multiple HTTP requests and multiple sessions within the same application.

Now here I am explaining data caching with an example.

The remaining steps are the same.

Step 5: Now here I have given 2 web forms with names I have given DataCaching.aspx and DataCaching2.aspx. and in the DataCaching.aspx the following is the code:
  1. <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="DataCaching.aspx.cs" Inherits="Caching.DataCaching" %>  
  2.   
  3. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">  
  4.   
  5. <html xmlns="http://www.w3.org/1999/xhtml">  
  6. <head runat="server">  
  7.     <title></title>  
  8. </head>  
  9. <body>  
  10.     <form id="form1" runat="server">  
  11. <div>   
  12. User Name:-<asp:TextBox ID="tbUserName" runat="server"></asp:TextBox>  
  13. <br />  
  14. <br />  
  15.     Password:-<asp:TextBox ID="tbpwd" runat="server"></asp:TextBox>  
  16. <br />  
  17.     <asp:Button ID="Button1" runat="server" onclick="Button1_Click" Text="Submit" />   
  18. </div>  
  19. </form>  
  20. </body>  
  21. </html>  
Code
  1. protected void Button1_Click(object sender, EventArgs e)  
  2. {  
  3.     //textbox value is stored in cache  
  4.     Cache["UserName"] = tbUserName.Text;  
  5.     Cache["Pwd"] = tbpwd.Text;  
  6.     Response.Redirect("DataCaching2.aspx");  
  7. }  
Step 6: Now the following is the code for DataCaching2.aspx:
  1. <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="DataCaching2.aspx.cs" Inherits="Caching.DataCaching2" %>  
  2.   
  3. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">  
  4.   
  5. <html xmlns="http://www.w3.org/1999/xhtml">  
  6. <head runat="server">  
  7.     <title></title>  
  8. </head>  
  9. <body>  
  10.     <form id="form1" runat="server">  
  11. <div>  
  12.     User Name:-<asp:TextBox ID="tbUserName" runat="server"></asp:TextBox>  
  13. <br />  
  14. <br />  
  15.     Password:-<asp:TextBox ID="tbpwd" runat="server"></asp:TextBox>  
  16. <br />  
  17. </div>  
  18. </form>  
  19. </body>  
  20. </html>  
Code
  1. protected void Page_Load(object sender, EventArgs e)  
  2. {  
  3.     //cache value is assign on the text box  
  4.     tbUserName.Text = Cache["UserName"].ToString();  
  5.     tbpwd.Text = Cache["Pwd"].ToString();  
  6. }  
The output is:





3 Fragment Caching

Caching of the entire page is not good because some part of the page is common for the entire application. So Fragmentation Catching is used for some portion of the page to be cached and we can do Fragmentation Caching using a User Control.

Now here, I am explaining Fragmentation Caching with an example.

The remaining steps are the same.

Step 4: Now right-click on "Add" > "New Item" > "Web User Control" and add the name.



Add the code inside the User Control.
  1. <%@ Control Language="C#" AutoEventWireup="true" CodeBehind="WebUserControl1.ascx.cs" Inherits="Caching.WebUserControl1" %>  
  2. <%@ OutputCache Duration="30" VaryByParam="None" %>  
  3. <div>  
  4. <asp:GridView ID="GridView1" runat="server" BackColor="White"  
  5. BorderColor="#999999" BorderStyle="Solid" BorderWidth="1px" CellPadding="3"  
  6. ForeColor="Black" GridLines="Vertical">  
  7. <AlternatingRowStyle BackColor="#CCCCCC" />  
  8. <FooterStyle BackColor="#CCCCCC" />  
  9. <HeaderStyle BackColor="Black" Font-Bold="True" ForeColor="White" />  
  10. <PagerStyle BackColor="#999999" ForeColor="Black" HorizontalAlign="Center" />  
  11. <SelectedRowStyle BackColor="#000099" Font-Bold="True" ForeColor="White" />  
  12. <SortedAscendingCellStyle BackColor="#F1F1F1" />  
  13. <SortedAscendingHeaderStyle BackColor="#808080" />  
  14. <SortedDescendingCellStyle BackColor="#CAC9C9" />  
  15. <SortedDescendingHeaderStyle BackColor="#383838" />  
  16. </asp:GridView>  
  17. <br />  
  18.     Server Time:-<asp:Label ID="Label1" runat="server"></asp:Label>  
  19. <br />  
  20. <br />  
  21.     Client Time:-  
  22. <script type="text/javascript">  
  23.     document.write(Date())  
  24. </script>  
  25. </div>  
  26.     Code:- Write the Code on Code Behind.  
  27. protected void Page_Load(object sender, EventArgs e)  
  28. {  
  29.     if (!IsPostBack)  
  30.     {  
  31.           //in the label show the server time  
  32.           Label1.Text = DateTime.Now.ToString();   
  33.           //connection string  
  34.           SqlConnection con = new SqlConnection(@"server=divs\sqlexpress; Database=Project;uid=sa;password=divya");  
  35.           //It's a query  
  36.           string query = "select User_name from registeration";  
  37.          //it's a command to be execute in a disconnected mode  
  38.          SqlDataAdapter da = new SqlDataAdapter(query, con);  
  39.          //create a obj of data set  
  40.          DataSet ds = new DataSet();  
  41.         //fill the data in dataset  
  42.         da.Fill(ds);  
  43.         //bind the data in gridview  
  44.         GridView1.DataSource = ds;  
  45.         GridView1.DataBind();  
  46.     }  
  47. }  
Step 5: Now right-click on the "Add" > "New Item" > "Web From" and add the name of the web form and write the following code:
  1. <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Fregment_catching.aspx.cs" Inherits="Caching.Fregment_catching" %>  
  2.   
  3. <%@ Register src="WebUserControl1.ascx" tagname="WebUserControl1" tagprefix="uc1" %>  
  4.   
  5. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">  
  6.   
  7. <html xmlns="http://www.w3.org/1999/xhtml">  
  8. <head runat="server">  
  9.     <title></title>  
  10. </head>  
  11. <body>  
  12.     <form id="form1" runat="server">  
  13. <div>  
  14.   
  15. Server Side Time On Page Level  
  16.     <asp:Label ID="Label1" runat="server"></asp:Label>  
  17. <br />  
  18. Client Side time on Page Level:-  
  19. <script type="text/javascript">  
  20.     document.write(Date())  
  21. </script>   
  22. <br />  
  23. <br />  
  24.     <uc1:WebUserControl1 ID="WebUserControl11" runat="server" />   
  25. </div>  
  26. </form>  
  27. </body>  
  28. </html>  
Code: Write the following code in the Code Behind.
  1. protected void Page_Load(object sender, EventArgs e)  
  2. {  
  3.     //show the server time  
  4.     Label1.Text = DateTime.Now.ToString();  
  5. }  
Output



In this output the Page Side Server time and user Control Side Server Time is the same but if we again refresh the button within 30 seconds then the user control server time is the same but all the time will be changed, that means the particular portion of the page is cached.

And now the main point is if the same User Control is used in a different browser then it will also have the shared property so that the same cached user control is shared in various clients.
  1. <%@ OutputCache Shared="true" Duration="30" VaryByParam="None" %>  
Cache Dependency

By using Cache Dependency we can set the dependency on some data and entities. In ASP.NET Caching Dependency are one of the following 5 types:
  1. File-Based Dependency: Generally File-Based Dependency is used when the cached data is dependent on the file. We can set the dependency on multiple files also.
  2. Key-Based Dependency: Items in the Application Cache are stored in key/value pairs. The key dependency allows an item to be dependent on the key of another item in the Application Cache. When the original item is removed, the Item that has the key dependency is also removed. For example you can add a cache an item named reports Valid and then cache several reports that are dependent on the ReportValid Key. When the ReportValid key item is removed, all the dependent cached reports are similarly removed from the cache.
  3. SQL-Based Dependency: Items of the cache are dependent on the row of a table in a SQL Server Database
  4. Aggregate Dependency: Items of the cache are dependent on multiple elements; if any of the dependencies change then the item is removed from the cache.
  5. Custom Dependency: An Item in the cache is configured with the dependency you create in your own code. For example, you can create a custom Web Service Cache Dependency that removes data from the cache when a call to the web service results in a particular value.

We can add the object into the cache and create it using the cache.insert() and cache.add() methods. The cache.insert() method has 4 overload versions whereas cache.add() has no overloads and most of the common properties for those methods are:

  1. Key: It's type is String type and a unique key is used to identify these entries in the cache.
  2. Dependency: It's type is cachedependency and it shows the dependency of cache like file or directory and when changed it should cause this entry to be flushed.
  3. Expires: It's type is DateTime and a fixed date and time after which this cache entry should be flushed.
  4. Sliding Expiration: It's type is TimeSpan and the time between when the object was Last accessed and when the object should be flushed from the cache.
  5. Priority: It's the type CacheItemPriority and it sets the priority of the cache.
  6. OnRemoveCallBack: It's type is CacheItem RemovedCallback and a delegate that can be registered with something.

And we can write the dependency as in the following:

Cache.Insert("Name", strName,new CacheDependency(Server.MapPath("name.txt"),DateTime.Now.AddMinutes(2), TimeSpan.Zero);

Caching Location

In which location caching can be done so ASP.NET has the following 4 caching locations where we can do the cache:

  1. Client Caching: The cache data is stored inside the client's browser on the local disk as a temporary file or in the browser's internal memory. So it reduces the network traffic and the client can be accessed easily but it is totally browser dependent so it is not shareable.
  2. Proxy Caching: It stores the caching information between the client and the web server in a shared location so that all clients can use the same shared data.
  3. Reverse Proxy Caching: The web server has a Proxy Server in the front so that it reduces the number of requests that they receive. This allows the Proxy Server to respond to frequently received requests and only passes other requests to the web server. This is called a reverse proxy and it reduces the number of requests and can easily be accessed but it increases the network traffic because the Proxy Server is the front of the web server.
  4. Web Server Caching: The cache data is stored inside the web server.

Advantage of the Caching

  1. It reduces the traffic of the server because the copy of the data is cached on the server and for the same request the copy of the data is given by a response without hitting the web server.
  2. Reduces bandwidth consumption

Next Recommended Readings