32bit Windows has a theoretical ability to address 4GB but in practice it is usually less than about 3.5GB for hardware mapping reasons. Windows itself hogs a huge chunk of the RAM.
I too noticed in the past when I would open many charts Ninja would rapidly get to the 1GB consumption range and hit the wall.
Under a 64bit OS the memory addressing limitations are for practical purposes eliminated. I am planning to build an 8GB machine to give Ninja and the other programs plenty of breathing room. Unfortunately my understanding is that if Ninja is compiled only as a 32 bit release it might not benefit at all from running on x64 Windows. It could though depending on how x64 Windows creates a 32 bit virtual space for it to run in. Will NT be given an entire 4GB space of it's own? If so then things should improve.
So what I am saying is if NT is only compiled as 32 bit but gets it's own 4GB of space then things are better.
If it is compiled as 64 bit then it will be able to use as much RAM as you want to throw at it and things are even better.
If it is compiled as 32 bit and it does not get a wide open 4GB home of it's own then things might not change that much.
Any Windows/NET memory mapping experts out there?
Hey support, will there be a 64 bit version of NT or just a 32 bit version verified to run well under x64?
Thanks,
Gains
Leave a comment: