Linked by Thom Holwerda on Tue 14th Aug 2007 17:55 UTC, submitted by tudyparghel
Windows "As we saw in part 1 of this series, large applications and games under Windows are getting incredibly close to hitting the 2GB barrier, the amount of virtual address space a traditional Win32 (32-bit) application can access. Once applications begin to hit these barriers, many of them will start acting up and/or crashing in unpredictable ways which makes resolving the problem even harder. Furthermore, as we saw in part 2, games are consuming greater amounts of address space under Windows Vista than Windows XP. This makes Vista less suitable for use with games when at the same time it will be the version of Windows that will see the computing industry through the transition to 64-bit operating systems becoming the new standard. Microsoft knew about the problem, but up until now we were unable to get further details on what was going on and why. As of today that has changed."
Thread beginning with comment 263449
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

I've never worked on games, but I have in many industries where we hit this limit (medical imaging was the biggest one). It's not something more efficient coding can help with...the datasets are just that big.

Define 'need that much memory'. The amount of memory needed is a function of what you want to do. I want as smooth an experience as possible. The more caching you do, the better, so give me more memory ;)

Don't worry. The more memory developers have available, the more memory they will use. So it all works out ;)

Reply Parent Score: 4

Ventajou Member since:

You're talking about highly specialized domains. The kind of stuff that should be using more reliable systems than Windows anyways unless you want to give a whole new meaning to the blue screen of death...

Reply Parent Score: 3