Make use of 2GB of RAM + some virtual mem
-
I am writing an application that needs to have in memory 40+ ( 30 to 60 MB ) images. Only four or five of them need to be viewed at a time. The application is running on a dual processor athlon 1.2 MP with 2GB of RAM. The problem is that Win2k server and professional limit the user process address space to 2GB and 2GB for the system. Advanced server will allow 3GB for user but I don't want to have to upgrade the OS again. The question what is the best way to allow my application to use most of the system's RAM and also allow it to use the swapfile for additional virtual memory. Can I use mem mapped files and only map them into my process space when I need to view the image. What about AWE?
-
I am writing an application that needs to have in memory 40+ ( 30 to 60 MB ) images. Only four or five of them need to be viewed at a time. The application is running on a dual processor athlon 1.2 MP with 2GB of RAM. The problem is that Win2k server and professional limit the user process address space to 2GB and 2GB for the system. Advanced server will allow 3GB for user but I don't want to have to upgrade the OS again. The question what is the best way to allow my application to use most of the system's RAM and also allow it to use the swapfile for additional virtual memory. Can I use mem mapped files and only map them into my process space when I need to view the image. What about AWE?
mem mapped files would allow your OS to take care of the virtual memory for you, parts that your app is currently using will be shipped into real ram as you use it anyway. But in graphics this swap can be a be unintelligent, portions of yuor graphic can (and probably will) be shipped out whilst your app is working on another part (assuming non contigious memory blocks). But this might be too slow for your graphics work. So, perhaps a compromise, claim a contigious global space (locked) of a size suitable for one of your graphics, and then swap each of your graphics into here yourself to work on. You may then be able to refine it by deciding which parts of your code need the graphic in your own swap area (for speed) and which don't. We do it for the joy of seeing the users struggle.