Comparing 32-bit and 64-bit Memory Architectures

I've written about how the 4GB 32-bit Windows memory limit impacts Terminal Server environments. That article has spawned a lot of discussions, particularly about whether 64-bit environments will have the same limit.

I've written about how the 4GB 32-bit Windows memory limit impacts Terminal Server environments. That article has spawned a lot of discussions, particularly about whether 64-bit environments will have the same limit.

Microsoft has actually published a KB article comparing 64-bit and 32-bit memory architectures. Here's a snapshot of the major differences:

Memory Component 32-bit 64-bit
Virtual memory 4GB 16TB
Page file size 16TB 512TB
Hyperspace 4MB 8GB
Paged Pool 470MB 128GB
Nonpaged Pool 256MB 128GB
System Cache 1GB 1TB
Page Table Entries 660MB 128GB

I think it's safe to say that when we move to 64-bit Windows, we won't have to worry about running out of kernel memory space for 10 or 15 years!

Join the conversation

3 comments

Send me notifications when other members comment.

Please create a username to comment.

This message was originally posted by Anders on March 25, 2004
The System cache entries are swapped.

- Anders
Cancel
This message was originally posted by Brian Madden on March 25, 2004
Thanks for the heads up folks! I've corrected the system cache entries.. Brian
Cancel
This message was originally posted by an anonymous visitor on March 25, 2004
I think you swapped headings or mistyped values in table. The 64bit numbers should alway be higher for every item
Cancel

-ADS BY GOOGLE

SearchVirtualDesktop

SearchEnterpriseDesktop

SearchServerVirtualization

SearchVMware

Close