Hi,
Regarding this request, the systems most affected are those with less than 32 GB of RAM, limited system disk capacity, and SATA SSD configurations on the C: drive, particularly when attempting to upscale images to the maximum size (32K pixels).
In this scenario, the temporary files can quickly consume the available space on the system drive (generally C:). Once that drive becomes full, Topaz only then allocates swap space to the Windows paging file.
This creates a temporary constraint on the Windows system, particularly during multitasking activities that require write operations on the C: drive, which can result in brief random freezes and significant slowdowns. This is especially noticeable when the system drive uses a SATA interface.
As far as I remember, this behavior did not occur in the legacy version of Topaz Gigapixel AI (around versions 4–5). In those versions, the application appeared to rely directly on the Windows paging file once the available RAM was exhausted, rather than first consuming the system drive with temporary files.
I am particularly concerned about this behavior because my C: system drive has limited capacity and relatively limited write performance, while I have a larger NVMe drive that is not configured as the system drive. Topaz itself is also installed on that NVMe drive.
Thank you for your attention and consideration.
Best regards,
-sergeantgeneral
