CLR通过C#探索：第四版多核编程全面解析

5星 · 超过95%的资源需积分: 16 58 浏览量更新于2024-07-25 2 收藏 6.47MB PDF 举报

"Microsoft.Press.CLR.via.Csharp.4th.Edition.Oct.2012" 本书《CLR via C#》第四版是针对C#编程语言和.NET Framework的重要参考资料，作者是知名的软件开发专家Jeffrey Richter。相较于第三版，这本书新增了对C# 5.0和.NET Framework 4.5的支持，涵盖了多核编程的全面内容。书中深入探讨了公共语言运行时（Common Language Runtime, CLR）的内部工作原理，为开发者提供了对.NET平台的深度理解。在C# 5.0中，引入了几个重要的新特性，如异步编程模型（async/await），它使得编写异步代码变得更加简洁和易于理解。这个特性允许开发者在不阻塞主线程的情况下执行长时间运行的操作，提高应用的响应性和用户体验。此外，还添加了动态类型（dynamic）关键字，这允许在运行时绑定对象，增强了与非.NET框架库（如IronPython和IronRuby）的交互能力。 .NET Framework 4.5是.NET平台的一个重大更新，它在性能、安全性、可靠性和开发工具方面都有所提升。其中，改进的垃圾收集机制优化了内存管理，减少了应用程序暂停时间。WCF（Windows Communication Foundation）和WPF（Windows Presentation Foundation）也得到了增强，提供了更好的跨设备和跨平台支持。书中“Full Coverage of Multicore Programming”部分详细介绍了如何利用多核处理器来提升应用程序的性能。这包括线程池的使用、并发编程的最佳实践、任务并行库（Task Parallel Library, TPL）以及如何有效地管理锁和同步。这些内容对于现代计算环境至关重要，因为多核已经成为大多数计算机的标准配置。《CLR via C#》第四版不仅讲解了理论，还提供了大量示例代码，帮助读者在实践中掌握这些高级概念。书中的章节来自作者未经最终润色和调试的原始稿，因此读者可以第一时间接触到最新的技术发展。然而，由于这是预发布版本，部分内容可能会在最终出版时有所变化，甚至可能不会出现在正式版书籍中。总而言之，本书是.NET开发者不可或缺的参考资料，无论是对于深入理解CLR的工作原理，还是学习C# 5.0的新特性，或是掌握多核编程技巧，都能提供宝贵的指导。通过阅读此书，开发者可以提升自己的技能，编写出更高效、更健壮的.NET应用程序。

When Main makes its first call to WriteLine, the JITCompiler function is called. The

JITCompiler function is responsible for compiling a method’s IL code into native CPU instructions.

Because the IL is being compiled “just in time,” this component of the CLR is frequently referred to as a

JITter or a JIT compiler.

Note If the application is running on an x86 version of Windows or in WoW64, the JIT compiler

produces x86 instructions. If your application is running as a 64-bit application on an x64 version of

Windows, the JIT compiler produces x64 instructions. If the application is running on an ARM version

of Windows, the JIT compiler produces ARM instructions.

When called, the JITCompiler function knows what method is being called and what type defines

this method. The

JITCompiler function then searches the defining assembly’s metadata for the called

method’s IL. JITCompiler next verifies and compiles the IL code into native CPU instructions. The

native CPU instructions are saved in a dynamically allocated block of memory. Then,

JITCompiler

goes back to the entry for the called method in the type’s internal data structure created by the CLR

and replaces the reference that called it in the first place with the address of the block of memory

containing the native CPU instructions it just compiled. Finally, the

JITCompiler function jumps to

the code in the memory block. This code is the implementation of the

WriteLine method (the version

that takes a String parameter). When this code returns, it returns to the code in Main, which

continues execution as normal.

Main now calls WriteLine a second time. This time, the code for WriteLine has already been

verified and compiled. So the call goes directly to the block of memory, skipping the

JITCompiler

function entirely. After the

WriteLine method executes, it returns to Main. Figure 1-5 shows what the

process looks like when WriteLine is called the second time.

FIGURE 1-5 Calling a method for the second time.

A performance hit is incurred only the first time a method is called. All subsequent calls to the

method execute at the full speed of the native code because verification and compilation to native

code don’t need to be performed again.

The JIT compiler stores the native CPU instructions in dynamic memory. This means that the

compiled code is discarded when the application terminates. So if you run the application again in the

future or if you run two instances of the application simultaneously (in two different operating system

processes), the JIT compiler will have to compile the IL to native instructions again. Depending on the

application, this can increase memory consumption significantly compared to a native application

whose read-only code pages can be shared by all instances of the running application.

For most applications, the performance hit incurred by JIT compiling isn’t significant. Most

applications tend to call the same methods over and over again. These methods will take the

performance hit only once while the application executes. It’s also likely that more time is spent inside

the method than calling the method.

Console

JITCompiler

Native CPU

instructions

static void Main() {

Console.WriteLine(“Hello”);

Console.WriteLine(“Goodbye”);

}

Managed EXE

static void WriteLine()

(remaining members)

...

static void WriteLine(string)

ITCompiler

unction {

}

SCo

rEE.

dll

1. In the assembly that implements the type

(

Conso

), look up the metho

iteLine

)

being called in the metadata.

2. From the metadata, get the IL for this method.

3. Allocate a block of memory.

4. Compile the IL into native CPU instructions;

the native code is saved in the memo

allocated in step 3.

5. Modify the method’s entry in the Type’s table so

that it now points to the memory block allocated

in step 3.

6. Jump to the native code contained inside the

memor y block .

bly that implements t

, look up the method (

Writ

alled in the

the metadata, get the IL for this me

ate a block of mem

pile the IL into native CPU instruction

ative code is saved in the memory

ated in

fy the method’s entry in the Type’s t

now points to the memory block a

e native code contained in

Native

You should also be aware that the CLR’s JIT compiler optimizes the native code just as the back end

of an unmanaged C++ compiler does. Again, it may take more time to produce the optimized code,

but the code will execute with much better performance than if it hadn’t been optimized.

There are two C# compiler switches that impact code optimization:

/optimize and /debug. The

following table shows the impact these switches have on the quality of the IL code generated by the

C# compiler and the quality of the native code generated by the JIT compiler:

Compiler Switch Settings C# IL Code Quality JIT Native Code Quality

/optimize- /debug-

(this is the default)

Unoptimized Optimized

/optimize- /debug(+/full/pdbonly) Unoptimized Unoptimized

/optimize+ /debug(-/+/full/pdbonly) Optimized Optimized

With /optimize-, the unoptimized IL code produced by the C# compiler contains many

no-operation (NOP) instructions and also branches that jump to the next line of code. These

instructions are emitted to enable the edit-and-continue feature of Visual Studio while debugging and

the extra instructions also make code easier to debug by allowing breakpoints to be set on control flow

instructions such as

for, while, do, if, else, try, catch, and finally statement blocks. When

producing optimized IL code, the C# compiler will remove these extraneous NOP and branch

instructions, making the code harder to single-step through in a debugger as control flow will be

optimized. Also, some function evaluations may not work when performed inside the debugger.

However, the IL code is smaller, making the resulting EXE/DLL file smaller, and the IL tends to be easier

to read for those of you (like me) who enjoy examining the IL to understand what the compiler is

producing.

Furthermore, the compiler produces a Program Database (PDB) file only if you specify the

/debug(+/full/pdbonly) switch. The PDB file helps the debugger find local variables and map the IL

instructions to source code. The

/debug:full switch tells the JIT compiler that you intend to debug

the assembly, and the JIT compiler will track what native code came from each IL instruction. This

allows you to use the just-in-time debugger feature of Visual Studio to connect a debugger to an

already-running process and debug the code easily. Without the

/debug:full switch, the JIT compiler

does not, by default, track the IL to native code information which makes the JIT compiler run a little

faster and also uses a little less memory. If you start a process with the Visual Studio debugger, it forces

the JIT compiler to track the IL to native code information (regardless of the

/debug switch) unless you

turn off the Suppress JIT Optimization On Module Load (Managed Only) option in Visual Studio.

When you create a new C# project in Visual Studio, the Debug configuration of the project has

/optimize- and /debug:full switches, and the Release configuration has /optimize+ and

/debug:pdbonly switches specified.

For those developers coming from an unmanaged C or C++ background, you’re probably thinking

about the performance ramifications of all this. After all, unmanaged code is compiled for a specific

CPU platform, and, when invoked, the code can simply execute. In this managed environment,

compiling the code is accomplished in two phases. First, the compiler passes over the source code,

doing as much work as possible in producing IL. But to execute the code, the IL itself must be compiled

into native CPU instructions at runtime, requiring more non-shareable memory to be allocated and

requiring additional CPU time to do the work.

Believe me, since I approached the CLR from a C/C++ background myself, I was quite skeptical and

concerned about this additional overhead. The truth is that this second compilation stage that occurs

at runtime does hurt performance, and it does allocate dynamic memory. However, Microsoft has done

a lot of performance work to keep this additional overhead to a minimum.

If you too are skeptical, you should certainly build some applications and test the performance for

yourself. In addition, you should run some nontrivial managed applications Microsoft or others have

produced, and measure their performance. I think you’ll be surprised at how good the performance

actually is.

You’ll probably find this hard to believe, but many people (including me) think that managed

applications could actually outperform unmanaged applications. There are many reasons to believe

this. For example, when the JIT compiler compiles the IL code into native code at runtime, the compiler

knows more about the execution environment than an unmanaged compiler would know. Here are

some ways that managed code can outperform unmanaged code:

• A JIT compiler can determine if the application is running on an Intel Pentium 4 CPU and

produce native code that takes advantage of any special instructions offered by the Pentium 4.

Usually, unmanaged applications are compiled for the lowest-common-denominator CPU and

avoid using special instructions that would give the application a performance boost.

• A JIT compiler can determine when a certain test is always false on the machine that it is

running on. For example, consider a method that contains the following code:

if (numberOfCPUs > 1) {

...

}

This code could cause the JIT compiler to not generate any CPU instructions if the host

machine has only one CPU. In this case, the native code would be fine-tuned for the host

machine; the resulting code is smaller and executes faster.

• The CLR could profile the code’s execution and recompile the IL into native code while the

application runs. The recompiled code could be reorganized to reduce incorrect branch

predictions depending on the observed execution patterns. Current versions of the CLR do not

do this, but future versions might.

These are only a few of the reasons why you should expect future managed code to execute better

than today’s unmanaged code. As I said, the performance is currently quite good for most applications,

and it promises to improve as time goes on.

If your experiments show that the CLR’s JIT compiler doesn’t offer your application the kind of

performance it requires, you may want to take advantage of the NGen.exe tool that ships with the .NET

Framework SDK. This tool compiles all of an assembly’s IL code into native code and saves the resulting

native code to a file on disk. At runtime, when an assembly is loaded, the CLR automatically checks to

see whether a precompiled version of the assembly also exists, and if it does, the CLR loads the

precompiled code so that no compilation is required at runtime. Note that NGen.exe must be

conservative about the assumptions it makes regarding the actual execution environment, and for this

reason, the code produced by NGen.exe will not be as highly optimized as the JIT compiler–produced

code. I’ll discuss NGen.exe in more detail later in this chapter.

In addition, you may want to consider using the

System.Runtime.ProfileOptimization class.

This class causes the CLR to record (to a file) what methods get JIT compiled while your application is

running. Then, on a future startup of your application, the JIT compiler will concurrently compile these

methods using other threads if your application is running on a machine with multiple CPUs. The end

result is that your application runs faster because multiple methods get compiled concurrently, and

during application initialization instead of compiling the methods just-in-time as the user is interacting

with your application.

IL and Verification

IL is stack-based, which means that all of its instructions push operands onto an execution stack and

pop results off the stack. Because IL offers no instructions to manipulate registers, it is easy for people

to create new languages and compilers that produce code targeting the CLR.

IL instructions are also typeless. For example, IL offers an

add instruction that adds the last two

operands pushed on the stack. There are no separate 32-bit and 64-bit versions of the

add instruction.

When the

add instruction executes, it determines the types of the operands on the stack and performs

the appropriate operation.

In my opinion, the biggest benefit of IL isn’t that it abstracts away the underlying CPU. The biggest

benefit IL provides is application robustness and security. While compiling IL into native CPU

instructions, the CLR performs a process called verification. Verification examines the high-level IL code

and ensures that everything the code does is safe. For example, verification checks that every method

is called with the correct number of parameters, that each parameter passed to every method is of the

correct type, that every method’s return value is used properly, that every method has a return

statement, and so on. The managed module’s metadata includes all of the method and type

information used by the verification process.

In Windows, each process has its own virtual address space. Separate address spaces are necessary

because you can’t trust an application’s code. It is entirely possible (and unfortunately, all too common)

that an application will read from or write to an invalid memory address. By placing each Windows

process in a separate address space, you gain robustness and stability; one process can’t adversely

affect another process.

剩余812页未读，继续阅读

习惯就好

粉丝: 28
资源: 18

CLR通过C#探索：第四版多核编程全面解析

Jeffrey Richter的《CLR via C# 第4版：多核编程全面指南》预览

.NET开发深入理解：CLR.via.Csharp.3rd.Edition精华解析

.NET平台架构详解：CLR via C# 第3版

CLR.via.Csharp.4th.Edition.Oct.2012.pdf

Microsoft.Press.CLR.via.C#.4th.Edition.2012

Microsoft.Press.CLR.via.Csharp.3rd.Edition.Feb.2010.part2

Microsoft.Press.CLR.via.Csharp.3rd.Edition.Feb.2010.part1

Microsoft.Press.CLR.via.Csharp.3rd.Edition part2

Microsoft.Press.CLR.via.Csharp.3rd.Edition part1

Microsoft.Press.CLR.via.Csharp.3rd.Edition 英文原版pdf part2

最新资源