- #How much memory to run mac os yosemite full#
- #How much memory to run mac os yosemite free#
- #How much memory to run mac os yosemite windows#
Most other windows in OS X will give you your GPU memory back as soon as you close the window. And once again, you don’t get that memory back when you close your images - only after you exit Photoshop. While it would take 70 normal windows to max out the 512MB of video memory on a GeForce GT 120 at 2560 x 1600, it would take less than nine 12MP images open in Photoshop to do the same. You need to exit Photoshop to get all of your video memory back. Under OS X each 12MP image from my digital camera that I open in Photoshop eats up around 56MB of video memory (at 2560 x 1600)! To make matters worse, OS X won’t reclaim all of the memory even if you close all of the images in Photoshop. With each image being OpenGL accelerated you get benefits like being able to zoom and rotate smoothly, the downside is that each image you open in Photoshop now eats up even more video memory. One of its major features is the ability to enable OpenGL acceleration within the application. Note that not all applications play nicely. If you have a 30” monitor running at its native resolution (2560 x 1600), a 512MB video card will get you just under 70 windows. I extrapolated the data out to 130 Safari 4 windows and presented the video memory requirements, dependent on resolution in the graph below: At 1680 x 1050 the cost per 10 windows drops from 71MB to 44MB. Lower resolutions require less video memory. While a single Safari 4 window needs 7MB at 2560 x 1600, ten will need around 71MB twenty windows will need 144MB. At 10 windows that overhead appears to be around 1MB.
Now things don’t always scale linearly and there’s additional overhead for dealing with more windows.
With a single window requiring 7MB, 10 requires about 70MB. Finder windows are much cheaper, some application windows are much more expensive (more on this later). A single Safari 4 window required 7MB of video memory at 2560 x 1600.
#How much memory to run mac os yosemite full#
I found that a full height Safari 4 window showing the AnandTech home page was pretty stressful from a memory footprint standpoint.
#How much memory to run mac os yosemite free#
On a 512MB card, at 2560 x 1600, you end up with 488MB of free video memory in OS X 10.5.7.ĭepending on the contents of the windows you open, their memory requirements will differ. I started with a blank desktop and measured available video memory. I ran some tests to figure out exactly how much video memory was enough for a single display. Those depend on having enough video memory to store/manipulate all open windows. The issue is never about how many windows you can have open, but how smoothly effects like Dashboard and Exposé run. Faster memory busses and PCIe 2.0 both help minimize the impact, but it’s there nonetheless. The trip to system memory is much higher latency than just grabbing windows from video memory, and thus we see performance suffer. If you run out of video memory, the GPU has to swap data in and out of system RAM. What it also means is that the amount of video memory you have matters. The result is much lower CPU and system memory usage. The GPU is much faster at all of this than the CPU so it made sense. Ars Technica’s John Siracusa has an excellent explanation of the whole process.Įach window gets treated as a 2D OpenGL surface and all of the character and image rendering, blending and display happens on the GPU. Ever since OS X 10.4, the entire drawing and display process happens on the GPU and in video memory. Previous versions of OS X either drew windows in system memory and then composited all of them in video memory, or did everything in system memory and just outputted the final scene to the video card. The contents of each window and the windows themselves are drawn by the GPU and stored in video memory. Honestly, one of the biggest uses for a new graphics card under OS X is having additional video memory. How Much Video Memory Do You Need in Mac OS X? I've been considering doing more things like this in the future, where you get pieces of a review as I finish them before the full thing is done. I just finished writing a section about GPU memory usage under OS X (since the 285 has a hefty 1GB frame buffer) and thought I’d publish it as a standalone before the review is done. As I mentioned in an earlier post, I’m working on a review of EVGA’s GeForce GTX 285 Mac Edition.
0 kommentar(er)
