Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
ASP.NET Site Performance Secrets

You're reading from   ASP.NET Site Performance Secrets Simple and proven techniques to quickly speed up your ASP.NET website

Arrow left icon
Product type Paperback
Published in Oct 2010
Publisher Packt
ISBN-13 9781849690683
Length 456 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Mattijs Perdeck Mattijs Perdeck
Author Profile Icon Mattijs Perdeck
Mattijs Perdeck
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

ASP.NET Site Performance Secrets
Credits
About the Author
About the Reviewers
1. Preface
1. High Level Diagnosis FREE CHAPTER 2. Reducing Time to First Byte 3. Memory 4. CPU 5. Caching 6. Thread Usage 7. Reducing Long Wait Times 8. Speeding up Database Access 9. Reducing Time to Last Byte 10. Compression 11. Optimizing Forms 12. Reducing Image Load Times 13. Improving JavaScript Loading 14. Load Testing

Output caching


Output caching lets you cache entire pages or sections of pages on the server itself. It gives you the following advantages:

  • Flexibility: Supports caching different versions of files, by query string variable, request header, or a custom variable.

  • Allows caching of parts of a page.

  • Life span of cached items is relatively predictable no competition for cache space by other websites. This may not apply if you use shared hosting, where many websites use the same web server.

It comes with the following disadvantages as well:

  • Not really suitable for caching visitor-specific pages because this would mean storing many pages with low hit rates.

  • Uses server memory.

  • No caching across servers because the cache is all in server memory. In a web farm, each server has its own cache. This means that each file is duplicated over multiple web servers' caches, taking more memory than needed and leading to possible inconsistencies between the versions in each cache.

  • If the application pool recycles...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image