优化ASP.NET 4.5.2性能的实战指南

5星 · 超过95%的资源需积分: 10 126 浏览量更新于2024-07-27 收藏 7.16MB PDF 举报

"Apress.Ultra-Fast.ASP.NET.4.5.2nd.Edition" 本书是《Ultra-Fast ASP.NET 4.5》的第二版，旨在帮助读者深入理解和优化ASP.NET 4.5应用程序的性能。作者在微软的工作经历为其提供了丰富的经验，使他能够从内部视角解析ASP.NET的运行机制。内容概览： 1. **引言**：作者分享了他在微软工作期间的经历，以及他对.NET技术的兴趣，这为他深入研究和理解ASP.NET打下了基础。 2. **原则与方法**（Chapter 1）：本章介绍了开发高性能ASP.NET应用的基本原理和方法，包括设计、架构和编码的最佳实践。 3. **客户端性能**（Chapter 2）：讨论如何优化客户端代码，如JavaScript和CSS，以减少页面加载时间和提高用户体验。 4. **缓存策略**（Chapter 3）：详细讲解了ASP.NET的缓存机制，包括页面输出缓存、数据缓存和分布式缓存，以提高应用响应速度。 5. **IIS 7.5**（Chapter 4）：深入探讨了IIS服务器的配置和管理，以提升Web应用的性能和稳定性。 6. **ASP.NET线程与会话管理**（Chapter 5）：解释了ASP.NET中的线程池和会话状态管理，以及如何有效地使用它们以避免性能瓶颈。 7. **使用ASP.NET实现优化技术**（Chapter 6）：展示了如何利用ASP.NET框架来实施各种性能优化策略，如HTTP压缩、异步处理等。 8. **ASP.NET应用程序策略管理**（Chapter 7）：讨论了如何管理和配置ASP.NET应用程序的生命周期，包括错误处理、配置管理等。 9. **SQL Server关系数据库**（Chapter 8）：涵盖了数据库优化，如索引、查询优化和数据库架构设计，以提升数据访问速度。 10. **SQL Server Analysis Services**（Chapter 9）：介绍了用于商业智能的多维数据处理和分析服务，包括数据挖掘和报表生成。 11. **基础设施与操作**（Chapter 10）：讨论了部署、监控和维护高性能ASP.NET应用所需的基础设施和运维策略。 12. **整合所有技术**（Chapter 11）：将前面章节所学的知识整合，提供了一个实际的案例，展示如何综合运用这些技术来构建一个完整的高性能ASP.NET应用。 13. **词汇表**和**索引**：提供了方便读者查阅的技术术语和主题索引。通过本书，读者将能够掌握提高ASP.NET 4.5应用程序性能的关键技术和策略，无论是对初学者还是有经验的开发者，都是宝贵的参考资料。

CHAPTER 1  PRINCIPLES AND METHOD

Software Version Cost

Expression Web 4.0.1303.0 SP2 $$

Fiddler Web Debugger 2.3.9 Free download

Firebug 1.10 Free download (Firefox plug-in)

Firefox 11.0 Free download

Internet Explorer 8 and 9 Free download

Log Parser 2.2 Free download

.NET Framework 4.5 Free download

Office 2010 Ultimate $$

Silverlight 5 Free download

SQL Server 2012 RC0 Developer,

Standard and Enterprise

$$$

SQL Server Data Tools April 2012 Free download (VS plug-in)

SQL Server Feature Pack October 2008 Free download

System Center Operations Manager 2012 RC $$

Visual Studio 2010 Premium SP1,

11 Developer Preview & Beta

$$$

Windows Server 2008R2 Standard $$

Windows 7 Professional x64 $$

Wireshark 1.6.4 Free download

YSlow 3.0.4 Free download (Firefox plug-in)

Most of the code that I discuss and demonstrate will also work in Visual Studio Web Express, which

is a free download.

C H A P T E R 2

Client Performance

The process of displaying a web page involves distributed computing. A browser on the client PC

requests and parses the HTML, JavaScript, CSS, images, and other objects on a page, while one or more

servers generate and deliver dynamic and static content. Building a fast system therefore requires a

capacity for speed in both the browser and the server, as well as in the network and other components in

between. One way to think about this is by viewing the server as really sending one or more programs to

the browser in the form of HTML (which is after all, Hypertext Markup Language) and JavaScript. The

browser then has to parse and execute those programs and render the results to the screen.

For existing sites, I’ve found that larger user-visible performance improvements can often be

obtained by optimizing the output of your web site so that it runs faster on the client rather than by

making your server-side code run faster. It is therefore a good place to start on the road to building an

ultra-fast site.

Particularly on the browser side of the performance equation, many small improvements can

quickly add up to a large one. Slow sites are often the result of the “death by 1,000 cuts” syndrome. A few

extra characters here or there don’t matter. However, many small transgressions can quickly add up to

make the difference between a slow site and a fast one, or between a fast site and an ultra-fast one.

Another way to think about this is that it’s often a lot easier to save a handful of bytes in 100 places than

100 bytes in a handful of places.

Imagine building a house. A little neglect here or there won’t compromise the quality of the final

product. However, if the attitude becomes pervasive, it doesn’t take long before the whole structure

suffers as a result. In fact, at some point, repairs are impossible, and you have to tear down the house

and build again from scratch to get it right. A similar thing happens with many aspects of software,

including performance and scalability.

In this chapter, I will cover the following:

• Browser page processing

• Browser caching

• Network optimizations

• JavaScript grouping and placement

• Downloading less

CHAPTER 2  CLIENT PERFORMANCE

• Using JavaScript to gate page requests

• Using JavaScript to reduce HTML size

• Uploading less

• Optimizing CSS

• Using image sprites and clustering

• Leveraging dynamic HTML and JavaScript (Ajax)

• Improving layout and rendering speed

• Precaching

• Using CSS layout without tables

• Optimizing JavaScript performance

The example files for this chapter are available online at www.12titans.net and in the download

that’s available from www.apress.com.

Browser Page Processing

When a browser loads a page, it’s not performing a batch process. Users don’t close their eyes after they

enter a URL and open them again when the browser has finished loading the page. Browsers do what

they can to overlap activity on multiple network connections with page parsing and rendering to the

screen. The steps that browsers follow are often extremely visible to users and can have a significant

impact on both perceived performance and total page load time.

Network Connections and the Initial HTTP Request

To retrieve a web page, browsers start with a URL. The browser determines the IP address of the server

using DNS. Then, using HTTP over TCP, the browser connects to the server and requests the content

associated with the URL. The browser parses the response and renders it to the screen in parallel with

the ongoing network activity, queuing and requesting content from other URLs in parallel as it goes.

Rather than getting too sidetracked with the variations from one browser to another, my focus here

will mostly be on Internet Explorer 9 (IE9, or just IE). Other browsers work similarly, although there are

definite differences from one implementation to another. With Firefox, users can set parameters that

change some of the details of how it processes pages, so the page load experience may not be 100

percent identical from one user to another, even when they’re using the same browser.

Figure 2-1 shows the TCP networking aspect of connecting to a remote server and requesting a URL

with HTTP.

剩余458页未读，继续阅读

DoomLord

粉丝: 114
资源: 1318

优化ASP.NET 4.5.2性能的实战指南

[Apress] Ultra-Fast ASP.NET 4.5 2nd Edition

Apress.Objective-C.for.Absolute.Beginners.2nd.Ed.2012

[iPhone开发书籍大全].iPhone.Design.Award-Winning.Projects(Apress.2009-12).pdf

Apress.Beginning.T-SQL.2012.2nd.Edition.Jul.2012

Apress.Beginning.PHP.and.MySQL.E.Commerce.2nd.Edition.Feb.2008-BBL

Beginning.iPhone.Games.Development(Apress.2010-3).pdf

].iPad.Made.Simple(Apress.2010-05).pdf

Apress.Pro.JSP.Third.Edition.eBook-LiB

Apress.Applied.ADO.NET.Building.Data-Driven.Solutions

Apress.Maximizing.Dot.NET.Performance.eBook-LiB.chm

最新资源