Maximum Virtual Memory (paging file)

Development Asset Creation
,
1

Hey all,

What would you suggest to take as the maximum Virtual Memory needed for large photosets?
Is it better to let Windows 10 manage the Virtual Memory or should I do it manually?

I am using the Capturing Reality promo version so if I read well I can go up to 3000 photos.

I am using 32GB physical memory (RAM) and for the virtual memory I have 250GB of free SSD space (where the cache is located to).
Next to that I have a i7 4790k processor and nvidia GTX 970 card.

Is this enough to run all the largest calculations or are there still limits for me?

If I learned well on the internet, it says for setting up virtual memory I can go up 4 times the physical RAM (x32GB) so 32GB x 4 = 128GB virtual memory as a maximum setting.
Is this correct or will the automatic setting do this anyway?

Or does it slow or decrease the process of I set such high settings?
I have no clue what is best to do…

I am trying to run high detail alignments of 1000-3000 photosets with 12MP RAW photos.
Yes, I am using the suggested alignment settings from Wishgranter (10k->80k)

Hope my questions are clear, thanks in advance for your help!

2

you need enough that it won’t run out :slight_smile:

I find it dose crash if you run out of virtual memory.

but 250gb ssd for pagefile + temp directory will push it.

I’ve been going by the rule maximum commit - ram size.

I’m running promo with 64gb ram, i generally find commit maximum under 200gb. but the most i have seen with pre-release was at 680gb with around 5500 photos. but i have a feeling this was due to poor alignment and memory leak.

you can also tune how much ram you need by adjusting vertices per part.