在 64 位操作系统上以 32 位和 64 位运行 IIS 的优缺点是什么? [英] What are the pros and cons of running IIS as 32bit vs 64bit on a 64bit OS?

问题描述

可能更适合机架溢出"，但从开发人员的角度来看，将 IIS(同时提供传统经典 ASP 和 .NET)作为 32 位进程而不是 64 位进程运行在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(我们仍然有一个来自合作伙伴供应商的 DLL，我们无法立即离开)) 并且在给定较小的内存指针的情况下，对于相同的代码可能会占用较小的内存.

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?

推荐答案

在 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 位模式下运行，在同一台机器上有多个工作进程的网络花园.在这种情况下，每个进程最多可以寻址 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 或更多的 RAM 来支持它)，以允许您在 Web 服务器上缓存复杂的页面内容或数据.当数据的生成成本高于检索成本时，这允许性能提升 - 例如，如果数据是精心设计的形式(假设是蒙特卡罗模拟的结果)，或者如果数据驻留在开箱即用和网络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 人，并且 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 位操作系统上以 32 位和 64 位运行 IIS 的优缺点是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！