![]() I use the free version of processlasso that has this "core parking" feature built in.ĭon't know if there are tweaks to change WoW64 affinity for use with specific programs. To change the core parking strategy you can do a registry tweak or use one of a few small utilites. Thats a good time saver for Xvid-HD recodes (on a 64 bit OS). ![]() The upshot is that the 64 bit version can give more than three times the performance of the 32 bit version.Ĭpu utilisation is up from about 16% with 32 bit to about 60% with 64 bit (no cpu parking). On my PC the 64 bit avidemux runs mostly on 4 physical cores (I7 cpu) and barely touches the logical cores (they mostly stay parked).ĭisabling core parking gives 64 bit avidemux a little bit of a performance boost again. There is no such performance hit with the other encoders (maybe they call for better threading!).įuthermore, by default windows 7/8 has core parking enabled. (However, you will need 64-bit capable hardware to build a 32-bit Avidemux for Windows). Tweaking various settings for threading, cpu affinity etc makes no difference. You need a Linux system (a VM with a lot of hard disk space and memory should suffice) to build your own. It stands to reason that it gets a bit of a performance hit (low cpu utilisation). It seems that under WoW64, the avidemux 32 bit - xvid4 encoder, runs on only 2 cpu cores. Part of the reason may be that 32 bit applications run under WoW64 (Windows on Windows). But looking at my I7 based PC I noticed that cpu utilisation is actually really low for encoding with MPEG-4 ASP (xvid4). Not so of course for properly functioning setups. This forum has a thread that avidemux was maxing out cpu utilisation and that this causes overheating and damage. For anyone using a PC with multiple cpu cores (like an I7) and running a 64 bit windows 7/8 this might be of interest.
0 Comments
Leave a Reply. |