Quote:
Originally Posted by Groucho2004
If the application that uses 32 Bit Avisynth is built with the LARGEADDRESSAWARE linker flag it can address up to 4 GB on a 64 Bit OS.
|
I'll have to test this some more
Without SetMemoryMax
Code:
FPS (min | max | average): 0.762 | 28.59 | 6.270
Memory usage (phys | virt): 1710 | 2022 MiB
Thread count: 35
CPU usage (average): 77%
With SetMemoryMax
Code:
FPS (min | max | average): 0.264 | 61.48 | 6.238
Memory usage (phys | virt): 2201 | 2510 MiB
Thread count: 35
CPU usage (average): 79%
I'm not seeing much of a difference here (8-bit)
Yes, I noticed that 16-bit is a LOT slower; it's either FFT3DFilter or MvTools2 that isn't well optimized. To know for sure, we'd have to test on a Y8 clip. If it's 2x slower in 16-bit, it's FF3DFilter. If it's 5x slower, it's MvTools2.
mClean crashes on a Y8 clip!