Regardless of the amount of physical
memory in your system,Windows uses a
virtual address space of 4 GB,with 2
GB allocated to user-mode processes
(for example,applications) and 2 GB
allocated to kernel-mode processes
(for example,the operating system and
kernel-mode drivers). On systems that
have 1 GB or more of physical memory,
these two startup switches can be used
to allocate more memory to
applications (3 GB) and less memory to
the operating system (1 GB).
好的 – 这不难理解. ……但对于sql Server来说这是件好事吗？答案取决于服务器中存在多少总内存？
对于这个讨论我们可以将任何答案联系起来
> 4 GB内存
> 16 GB内存
…使用包含Windows 2008标准x64 sql Server 2008 x64的服务器.我希望#处理器不影响答案：P
所以我想我问,sql Server是否需要大量内存用于OS内核模式驱动程序？
http://support.microsoft.com/kb/294418
Applications that are compiled with
the /LARGEADDRESSAWARE option,as
would be required to take advantage of
the /3GB switch in 32-bit Windows,
will automatically be able to address
4 GB of virtual memory without any
boot time switches or changes to x64
Windows. Plus,of course,the
operating system does not have to
share that 4 GB of space. Therefore,
it is not constrained at all
和
A pool of system Page Table Entries
(PTEs) that is used to map system
pages such as I/O space,Kernel
stacks,and memory descriptor lists.
64-bit programs use a 16-terabyte
tuning model (8 terabytes User and 8
terabytes Kernel). 32-bit programs
still use the 4-GB tuning model (2 GB
User and 2 GB Kernel). This means that
32-bit processes that run on 64-bit
versions of Windows run in a 4-GB
tuning model (2 GB User and 2GB
Kernel). 64-bit versions of Windows do not support the use of the /3GB switch in the boot options. Theoretically,a 64-bit pointer could address up to 16 exabytes. 64-bit versions of Windows have currently implemented up to 16 terabytes of address space
