Ultra-Fast ASP.NET 4.5：构建高性能可扩展网站

需积分: 9 71 浏览量更新于2024-07-18 收藏 5.71MB PDF 举报

"《构建高性能可扩展ASP.NET网站》(Ultra-Fast ASP.NET 4.5 第二版) 是一本专注于提升ASP.NET 4.5应用程序性能和可扩展性的技术书籍。作者通过深入探讨一系列关键主题，帮助读者理解并实施高效能的Web应用开发策略。" 本书的内容涵盖广泛，旨在帮助开发者实现ASP.NET网站的极致性能优化。以下是各章节的简要概述： 1. **原理与方法**：这一章介绍基础的性能优化原则和设计模式，包括理解性能瓶颈和如何系统性地进行性能测试。 2. **客户端性能**：讨论了如何优化前端代码，如减少HTTP请求，压缩CSS和JavaScript，以及利用缓存机制来提升页面加载速度。 3. **缓存技术**：深入讲解了ASP.NET的缓存机制，包括数据缓存、输出缓存和分布式缓存，以及如何有效地利用它们来减少服务器负载。 4. **IIS 7.5**：介绍IIS的高级配置和管理，包括URL重写、模块优化和多站点托管，以提高服务器效率。 5. **ASP.NET线程与会话**：探讨了ASP.NET中的线程管理和会话状态管理，以及如何避免这些问题导致的性能问题。 6. **使用ASP.NET实现和管理优化技术**：讨论了各种ASP.NET特性，如异步处理、任务并行库(TPL)，以及如何在Web应用中有效地使用这些工具。 7. **管理ASP.NET应用策略**：涵盖了应用程序池、配置管理、错误处理和日志记录，以便更好地控制和监控应用程序的运行。 8. **SQL Server关系型数据库**：讲述了数据库优化技巧，包括索引策略、查询优化和数据库架构设计，以最大化数据库性能。 9. **SQL Server Analysis Services**：介绍了数据分析服务，如何利用其进行大数据处理和分析，以支持高效的报表和决策支持。 10. **基础设施与运维**：讨论了硬件选择、网络架构和运维实践，以确保整个系统的基础稳定和高效。 11. **整合应用**：将前面各章节的知识综合运用，展示如何构建一个高性能、可扩展的完整解决方案。 12. **词汇表**：提供了书中专业术语的解释，方便读者查阅。 13. **索引**：完整的书本索引，便于读者查找特定主题。通过这本书，读者不仅可以了解到ASP.NET 4.5的性能最佳实践，还能掌握一套全面的工具和技术，用于构建能够应对高并发、大数据量挑战的高性能网站。对于任何希望提升ASP.NET应用性能的专业人士来说，这都是一份宝贵的资源。

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页未读，继续阅读

Begeeking

粉丝: 0
资源: 7

Ultra-Fast ASP.NET 4.5：构建高性能可扩展网站

构建高性能可扩展ASP.NET网站 高清中文版

构建高性能可扩展ASP.NET网站.part1

构建高性能可扩展ASP.NET网站PDF与源码（修正PDF）

构建高性能可扩展ASP.NET网站-中文版

构建高性能可扩展ASP.NET网站 + 源代码----英文版

Ultra-fast ASP.NET - Building Ultra-fast and Ultra-scalable Web Sites

构建高性能可扩展ASP.NET网站

《构建高性能可扩展ASP.NET网站》源码

构建高性能可扩展ASP.NET网站.part2

构建高性能可扩展ASP.NET网站（pdf英文版 + SourceCode)

最新资源

构建高性能可扩展ASP.NET网站高清中文版