R
Ryan
Guest
**** the 2.4 gig memory limit x64 to the rescue
This is what those who have waited get rewarded with
This is what those who have waited get rewarded with
more like 16 exabytesMark said:To give a little more background, 32 bit processors can only address (see) 4 GB of memory (2 ^ 32 = roughly 4 GB ). Of that 4, 2 is given to the server, 2 is for the core operating system. With tweaks, we could give 3 to the server, and 1 to the operating system. With all the items and mobiles on our server though, we exceed that limit (2.4 for .NET applications). So even though our server had 4 GB of memory, we could only really use 2.4 GB of it due to the platform.
To be concise, 64 bit systems have 2 ^ 64 (like 18 petabytes or something) of address space, allowing us to use our full 4 GB of memory and more (system paging). This conversion will prevent us from crashing with the dreaded 'out of memory exception'.
EDIT:
I guess some of this goes way over people's heads, so I'll break it down.
- A large shard uses a large amount of memory.
- 32 bit computers can only handle a relatively small amount of memory.
- 64 bit computers can handle a practically unlimited amount of memory.
- Our shard is very large (perhaps the largest), and we're at the '32 bit wall', which is causing the frequent crashes.
- This transition will stop those crashes.
Devine said:more like 16 exabytes
so what happens when we hit that wall