Archive for the ‘ Performance’ Category
There are few ASP.NET Performance books out there and even fewer good ones.
This one I like. Matt Perdick has taken an interesting approach by not just presenting technology tips and tricks that can be used to positively effect performance but rather presents the technologies in the context of a methodology one can use to identify and resolve performance problems in their own web applications.
Matt covers the tools you can use with the bottleneck pinpointing process to find and fix issues with :
- Time to First Byte
- Memory Usage
- CPU Consumption
- IIS Output
- Thread usage and Asynchronous Architectures
- Reducing Long Wait Times
- Database Access
- Time to Last Byte
- Forms Optimization
- Load Testing
- It’s easy to read with ample code samples and screenshots and contains many, many of the kind of tips you would expect concerning things like ASP.NET View State, Element Ids, working with User Agent specifics, etc.
A good addition to your ASP.NET Expertise.
[ Get it HERE ]
|Website Optimization: Speed, Search Engine & Conversion Rate Secrets: Andrew King: Books
The folks at O’Reilly recently published this gem !
From the book description:
This book is a comprehensive guide to the tips, techniques, secrets, standards, and methods of website optimization. From increasing site traffic to maximizing leads, from revving up responsiveness to increasing navigability, from prospect retention to closing more sales, the world of 21st century website optimization is explored, exemplified and explained.
Though I’ve just started readying it I’m already convinced it’s a must have !
Please check out Maarten Balliauw’s great blog posts on ASP.NET State Partitioning and Load Balancing.
Make sure debug=false is set in the <compilation> section in config.
Then the web resource URLs will be cached (like the client libraries).
The “t=” in the web resource URLs represents the assembly’s last modified date.
As long as you don’t change the atlas assembly, the same “t=” should be generated.
Proxies should get cached as well.. They are retrieved from the server as the browser parses the page, and loads referenced scripts.
This is completely orthogonal to server lifecycle events such as Page_Init.
There are some enhancements for caching in MS AJAX RTM that make the scenario even better.
Thanks to Nikhil Kothari for my edification.