Skip to main content

How much VRAM does PR use



  • Martin Evans

    I have the same card and 2GB is the max memory I ever see used on the GPU. Video encode often goes almost to 100% especially when doing things like nonoise AI and tack sharp AI.

  • Keith Neff

    Martin, my biggest problem with PR on this machine is working with masking brushes at 100%, the brushes are very sticky no matter where the video card slider is set and it seems to get worse as you go along.  Once it gets into that mode I usually have to reboot the system to get any kind of performance back.  

  • Martin Evans

    I've just tried again and I can use a masking brush with a local adjustment at 100% with no lag at all. I can move the brush very quickly with my mouse. When I do I see my GPU go to about 90%. I have not touched the video card slider which is in the middle and fast preview, fast pan and GPU render are on.

    I'm sure a better GPU would be even better but this is the same GPU I used in another older machine where the performance was very poor and masking at 100% was impossible. I know a lot of people on this forum talk about the need for a fast graphics card but I seem to be fortunate in my old GTX 1060 6GB seems to be all I need in my new machine.

    My machine specs:

    • 12th generation Intel Core i7-12700KF, 3600Mhz, 12 cores, 20 logical processors
    • MSI Pro Z690-A WIFI DDR4 motherboard
    • 2 * 16GB 3600Mhz DDR4 vengeance LPX memory
    • Samsung EVO Plus NVMe M.2 SSD
    • Nvidia GeForce GTX 1060 6GB

    My CPU is running cool as a cucumber and not even breaking into a sweat

  • Keith Neff

    Well I just went up and checked it out and indeed from a fresh start I can mask away at 100% with no problem.  GPU hits about 80%, CPU ( i7-10K ) is hardly doing anything.  So, you are right this board can handle PR.  Where the trouble seems to come is after a long session of photo retouch things get sticky.  Guess the solution is just reboot and start fresh.

    Thanks for your input.

  • Martin Evans

    I rarely spend more than a few hours in PR and that would normally be editing many images in one session. If a single image needs more than 5 minutes (10 if I really like it) I usually feel it isn't worth the effort so I'd not class myself as someone who applies a lot of complex edits to a image. I seldom use layers (unless doing a composite). My main edits are (not in order):

    • straightening and perspective fixes
    • cropping
    • camera profile
    • lens correction and sometimes green/purple fringing
    • highlight correction
    • blacks and whites modification
    • white balance adjustments if required
    • saturation and very occasionally hue
    • visualize dust as I don't often clean my sensor then fix
    • clone out any distractions if it can be done quickly
    • various effects, B&W conversion, dynamic contrast, colour enhancer (mostly on skies), vignette occasionally, occasionally blur
    • local adjustments e.g., lighten up a face a little or darken the sky a little

    I'm not into sky replacement, if it is a boring sky then I might consider converting to B&W. I don't do a lot of complex masking (if it can be achieved quickly then fine). So I can usually accomplish what I want in 5 minutes per image with the occasional one taking longer.

    In this process I can edit dozens of images and I now (on new PC) don't see anything slowing down. In fact a few things since I moved to a new PC build (with the same graphics card and same disk for images) are surprisingly fast:

    • browsing through images in edit mode - Much quicker and yet the hard disk drive I edit on is exactly the same one that was in my old machine - a SATA disk but not an SSD, a conventional spinning disk.
    • the browser renders images much faster - before I might have to wait every time I scrolled down for the images to appear
    • exporting images is so fast I barely see the exporting dialogue and yet again, I'm exporting to the same old disk I had in my old machine.
    • rendering images when going from browse to edit was horribly slow on my old machine - again, same disk so it was not down to the slow disk or graphics card (the same) and must be down to the faster CPU
    • masking at 100% is now fine whereas it was impossible before
    • masking when showing the mask is now fine whereas before it was impossibly slow

    Admittedly, my cache folders are all on the main system disk which is a NVMe M.2 and that is blindingly fast so perhaps that makes a difference as well.

    I see no reason on my setup to spend £500 on a new graphics card - it works fine as it is.

  • Keith Neff

    Agreed on the video card and your process.  I just did an extensive test and found that each time a picture was opened it ate up some ram, close the pic and it didn't come back open another and loose a little more ram.  However, that is not the culprit, I did some fairly extensive masking at 100% and it bogged down to the point where it took 4 seconds for the brush to move.  Closed that pic, reopened: same, closed the program reopened: same.  Cleared that mask and bang, instantly back to normal and I was able to complete the mask.  So something odd can happen to a mask the hobbles the program.  Oh and while this is happening there is no sign of a problem in the performance monitor.

    Re your comment on sky replacement, I agree they usually look like sky replacements!  I will often use the sky replacement to generate a mask then load it into either locals or effects to tweak the real sky.

    Nice conversation, thanks.


  • Michael Lucero

    I'm having the same issue. I tried using Super Select to select the issues until I added to the initial selection using the Perfect Brush feature to finish selecting parts of the sky that was between fences. This was just a few strokes with a large brush.

    Once I zoomed in, the panning has about a 7 second lag time...not really useable.

    Latest driver for Nvidia 2060 Super (8 Gb) as of yesterday, 32 Gb RAM, working on a 36 Mb Raw image.

    I did notice that the GPU would often hit 100% while just trying to pan.

    I have also tried any and all setting combinations inside of the system preferences regarding gpu adjustments.


  • Keith Neff

    Michael, my latest theory is that the program is rendering the entire picture with each brush stroke for some reason.  You are correct about the sliders in settings, they do nothing.

    Hoping that this new patch helps, it is very slowly downloading on my other machine now.  Fingers crossed.


Please sign in to leave a comment.