> Z C <
zicha...@gmail.com>: Aug 26 07:07AM -0700
>
> I am recently stitching massive amount of photos (in the order of
> thousands). I am working with a i5 8600k and 4070ti with 32gb of ddr4
> memory… Sometime the system becomes unresponsive after
> creating a massive amount (last night about 1.5T) of temp files and i have
> to restart.
RAM is so cheap these days! Stuff that puppy with every byte of RAM you can afford!
If you're using smallish sticks of RAM (under 16 GB), you may have to eBay them, in order to max out your RAM with bigger sticks.
> … a load of m.2. ssd attached.
Is your SSD external? Are you booted from spinning disk?
If so, get the SSD as close as you can to the CPU.
I recommend a minimum of TWO SSDs — one for your system, and one for your data. If you have more than one, but they are arranged as a RAID, I'd split them into two logical volumes on at least two physical drives for system and data.
With only 32 GB of RAM, you're probably swapping RAM to disk during stitching, which REALLY slows things down (even with SSD), but it also wears out the SSD faster. (SSDs have a limited number of writes in their lifetime.) You DO NOT want to swap! Going over SATA is at least an order of magnitude slower than going to RAM, even with SSD!
I have 128 GB in a sixteen-year-old computer, and have never experienced what you describe. In fact, I continue using the computer for email, web browsing (with tens of pages open), and even editing the resulting ~30,000-pixel-wide images — all while stitching even more pans!
I have a 2009 Mac Pro 4,1, with:
* eight 16 GB sticks of DDR 1333 MHz RAM, for 128 GB total
* two Xeon 6-core processors, at 3.46 GHz
* two internal Micron 2TB SATA SSDs, one for the OS and programs, and the other for images, movies, music, etc.
* one 16 TB spinning disk for incremental backup (Apple Time Machine)
With that setup, the only practical implication of large stitches is that the fan is louder, and the attached watt meter goes from ~300 watts to ~500 watts.
> At that stage PTgui did not save my work to some kind of pts
> files that it can continue working on.
That would slow it down even more. You want things to stay in RAM.
If you're doing large panoramas, just bite the bullet and get as much RAM as your computer can possibly take. You've invested in PTGui when you could have been using hugin for free, so it's time to back that up with hardware!
Jan