Well, you used AVSMeter 2.6.2 (x86), so, a 32-bit process.
AVSMeter64 will run a 64-bit process.
Yet ... if you have LAA binaries, utilizing above 2.0 and up to 3.5 GB RAM should not cause so much speed penalty, that's a different issue (bold guess: maybe using a plugin which is not really LAA compatible, thus system calls occur a lot to try to prevent issues?).
Last edited by LigH; 6th September 2017 at 09:55.
|