XP or Vista 32-bit can only address up to 4GB of memory. It ends up losing some of that to the system resources (videocard, bios, and some other features). Common is to see only about 3.25GB if you have 4GB.
In a Windows environment, any given 32-bit application by default can only use 2GB of memory. If the application was written for it, you can use the /3GB in the boot.ini to allow applications to use up to 3GB of memory. If the application wasn't written for it, and it tries to use more than 2GB of memory, it could cause stability issues.
When you go 64-bit, Windows XP and Vista can go up to 128GB depending on the version (see XP x64
here and Vista x64
here).
Since you have the windows version of the program, you need to decide if its worth switching to the linux version. If you stay with Windows, does your application support 64 bit? Is there a cheap upgrade path if not? You may want to consider removing any other applications that may be running that you don't need to free up memory. Faster access hard drives may make a big difference. Asking your questions to the software manufacturer may be your best bet. They can tell you what runs best.
Dev Mgr
4 Operator
•
9.3K Posts
0
November 29th, 2007 18:00
XP or Vista 32-bit can only address up to 4GB of memory. It ends up losing some of that to the system resources (videocard, bios, and some other features). Common is to see only about 3.25GB if you have 4GB.
In a Windows environment, any given 32-bit application by default can only use 2GB of memory. If the application was written for it, you can use the /3GB in the boot.ini to allow applications to use up to 3GB of memory. If the application wasn't written for it, and it tries to use more than 2GB of memory, it could cause stability issues.
When you go 64-bit, Windows XP and Vista can go up to 128GB depending on the version (see XP x64 here and Vista x64 here).
tr4
1.7K Posts
0
November 30th, 2007 22:00