1726
General Software Discussion / Re: Seeking experiences from people backing up relatively large personal data sets
« Last post by Shades on November 27, 2012, 04:40 PM »Nope, Windows won't allow any process to consume more than 2 GByte. Believe me, I got a 64 GByte RAM computer that also has 64 processors to its knees, because of that.
Doesn't matter if the OS and/or the application is 32-bit or 64-bit. The Windows memory manager won't let you..unless you step in and take over from it. See KB article 833721 for startup parameter '/3GB'. Still, you are only allowed to consume to a maximum of 3 GByte RAM per process.
Only after enabling that startup parameter on a 64-bit OS and having a 64-bit compiled application you can go over the 3 GByte limit to go to a 4 GByte limit. Expect to run your system into the ground sooner than later though.
As far as I know both the 32-bit and 64-bit Windows memory manager sees that there is 4 GByte of RAM, even if your PC has less physical RAM. Whatever is not there, will be delegated to the hard disk (swap-file). 2GByte of this RAM is for non-Windows processes only, the other 2GByte is also open to Windows kernel processes.
With the /3G parameter you limit the Windows kernel to just 1 GByte and whatever non-Windows process is allowed to use 3 GByte. Nether you or the Windows memory manager is going to be pleased with this. So, if you have an application that consumes 2 GByte, that application is clearly doing something so wrong it doesn't deserve a place on your hard disk in the first place.
Yes Excel, I'm looking at you...
Doesn't matter if the OS and/or the application is 32-bit or 64-bit. The Windows memory manager won't let you..unless you step in and take over from it. See KB article 833721 for startup parameter '/3GB'. Still, you are only allowed to consume to a maximum of 3 GByte RAM per process.
Only after enabling that startup parameter on a 64-bit OS and having a 64-bit compiled application you can go over the 3 GByte limit to go to a 4 GByte limit. Expect to run your system into the ground sooner than later though.
As far as I know both the 32-bit and 64-bit Windows memory manager sees that there is 4 GByte of RAM, even if your PC has less physical RAM. Whatever is not there, will be delegated to the hard disk (swap-file). 2GByte of this RAM is for non-Windows processes only, the other 2GByte is also open to Windows kernel processes.
With the /3G parameter you limit the Windows kernel to just 1 GByte and whatever non-Windows process is allowed to use 3 GByte. Nether you or the Windows memory manager is going to be pleased with this. So, if you have an application that consumes 2 GByte, that application is clearly doing something so wrong it doesn't deserve a place on your hard disk in the first place.
Yes Excel, I'm looking at you...

Recent Posts

But for me the ¨sweet spot¨ lies with their 2003 Server. 
