什么是在64位操作系统上运行IIS作为32位VS 64位的利弊？ [英] What are the pros and cons of running IIS as 32bit vs 64bit on a 64bit OS?

问题描述

也许更适合机架溢出，但是从开发人员的角度，有什么优点和运行IIS的缺点上（服务于传统的传统的ASP和.NET）一个64位的过程，作为一个32位的过程，而不是64位windows主机？

Possibly better suited for "Rack Overflow", but from a developer's point of view, what are the advantages and disadvantages of running IIS (serving both legacy classic ASP and .NET) as a 32bit process instead of a 64bit process on a 64bit windows host?

32/64（IIS /服务器）超过32/32的主要优点似乎是走在每个IIS进程的内存为4GB的能力。

The main advantage of 32/64 (iis/server) over 32/32 seems to be the ability to go up to 4gb in memory per IIS process.

我预计32/64超过64/64的优势似乎是，它更容易进入传统的32位进程的DLL（其中我们仍然从合作伙伴的供应商有一个我们不能立即离开）或许对于给定的更小的内存指针一样code占用更少的内存。

The advantages I expect of 32/64 over 64/64 appear to be that it's easier to access legacy 32-bit in-process DLLs (of which we still have one from a partner vendor we can't move away from immediately) and perhaps a smaller memory footprint for the same code given smaller memory pointers.

有没有的64/64 32/64以上或其他任何东西，现在有理由进行全面切换任何性能优势？有我在这里所做的任何错误的假设？

Are there any performance benefits of 64/64 over 32/64 or anything else that would warrant a full switch now? Have I made any false assumptions here?

推荐答案

唯一PERF的优势在64位vevrsus 32位运行IIS是允许访问一个更大的存储器地址空间。

The only perf advantage to running IIS on 64bit vevrsus 32-bit is to allow access to a much larger memory address space.

如果你正在做正常的ASPX页面的处理，那么很可能你并不需要解决超过4GB的任何一个过程。假设你在32位模式下运行与在同一台机器上的多个工作进程的Web-花园。在这种情况下，每个流程最多可寻址4GB。

If you are doing normal ASPX page processing, then it's likely you don't need to address more than 4gb from any single process. Suppose you run in 32-bit mode with a web-garden with multiple worker processes on the same machine. In that case each process can address up to 4gb.

在执行缓存的最大优点能来。 64位进程能够保持巨大的内存缓存（假设你有32GB或更多的内存来支持的话），让您缓存复杂的页面内容或数据，在Web服务器上。这使得PERF收益当数据是比较昂贵，产生比它检索 - 例如，如果该数据是一个详细表格（假设蒙特卡罗模拟的结果），或如果数据驻留关闭盒和网络IO时间要比缓存检索时间更贵。

The big advantage can come when you perform caching. A 64-bit process can maintain a huge in-memory cache (assuming you have the 32GB or more of RAM to support it) to allow you to cache complex page content or data, on the web server. This allows perf gains when the data is more expensive to generate than it is to retrieve - for example if the data is an elaborated form (let's say the result of a monte carlo simulation), or if the data resides off-box and the network IO time is much more expensive than cache-retrieval time.

如果您不使用缓存，那么64位IIS是不会帮你的。这将需要64位指针，每查找，这将让一切慢一点

If you do not use caching, then 64-bit IIS is not going to help you. It will require 64-bit pointers for every lookup, which will make everything a little slower.

64位服务器的更有效的使用如SQL Server或其它数据管理服务器上的数据库时，（比方说，一个企业电子邮件服务器，如Exchange），比处理服务器，如IIS或工作进程它所管理。与64位的地址空间，需要管理数据服务器可以保留更多的数据的存储器，以及索引和其它高速缓存。这样可以节省磁盘IO时间和制订时间，当查询进来。大多数Web应用程序并不需要解决超过4GB的单个进程。

64-bit servers are much more effective when used for databases like SQL Server, or other data management servers (let's say, an enterprise email server like Exchange), than for processing servers, such as IIS or the worker processes it manages. With a 64-bit address space, servers that need to manage data can keep much more of that data in memory, along with indexes and other caches. This saves disk IO time and elaboration time when a query comes in. Most Web apps don't need to address more than 4gb from a single process.

也许一个有用的类比：在交通方面，一个大型SUV就像是一个64位的机器，而有规律的，紧凑型轿车就像是一个32位服务器。您可以携带一个大型SUV更加的东西，它有一个较大的牵引能力，容纳8人，和<一href="http://autos.msn.com/research/vip/spec_engines.aspx?year=2005&make=Ford&model=Excursion">a GVWR的8600磅。但与所有的，一分钱一分货。卡车较重。它使用更多的燃料。如果你只围绕卡丁车2人，一个行李袋，你并不需要一辆SUV。你会更好地与较小的车辆。它可以更快和更有效。

Maybe a useful analogy: In transport, an large SUV is like a 64-bit machine, while a regular, compact passenger car is like a 32-bit server. You can carry much more stuff in a large SUV, and it has a larger towing capacity, seating for 8 people, and a GVWR of 8600 lbs. But with all that, you pay. The truck is heavier. It uses more fuel. If you are only carting around 2 people and one duffel bag, you don't need an SUV. You'll be better off with the smaller vehicle. It can be speedier and more efficient.

这篇关于什么是在64位操作系统上运行IIS作为32位VS 64位的利弊？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！