By default, a View State is stored in a hidden text field on the Web page increasing the page size. The time it takes to download and upload the page increases linearly with the page size.
Revindex Optimizer can offload the View State data to another storage type minimizing the page size. Each storage type performs and reacts differently. You need to choose the suitable storage type depending on your available server resource, type of business, traffic pattern and service level agreement. See How to calculate storage space for more info.
| Storage type |
Performance |
Scalability |
Durability |
Network usage |
File
Suitable for servers with access to lots of fast hard disk storage and require supporting users staying on page for short to long amount of time. |
Fast |
Good scalability since disk storage is abundant and can support Web farm scenario. |
Highly durable. View State data remains valid after server restarts. Data remains valid until it is expired. |
None if using local files. Moderate amount of internal network usage if using Web farm. |
Memory
Recommended for servers with lots of available memory and type of business with short to medium transactions.
|
Fastest |
Least scalable storage type limited by the amount of memory. Cannot work in Web farm scenario. |
Least durable and View State will be lost when server restarts. May also lose View State when memory is insufficient. |
None |
Page
This is the default ASP.NET storage type. Recommended for small servers and type of business that support users staying on page for extremely long hours. |
Slow |
Extremely scalable since there is no limit to the amount of View State being stored on the page. |
Best durability. View State data remains valid after server restarts and for as long as the page is open. |
Large amount of external network usage. |