![]() |
[INFO] low processor usage - reason? - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [INFO] low processor usage - reason? (/thread-894.html) |
low processor usage - reason? - kkf_hu - 23.02.2019 Hi Selur. Was wondering, you have ever had a similar report, but here is the deal. Once the movie encoding starts, the CPU usage goes up to 100% and remains there for a while, but at a certain % it drops significantly (to 20-30%) and stays there. I can ensure you, there are 0 other background processes at play. System is Win10x64, Core i7-6700, GPU usage is 0%, I forced 8 threads (for my 4x2 overall cores) on the x264 tab, but it happens also when i leave it on auto. As you can see usage is so bad, that the CPU can cut back on speed. Vaporsynth is using MLdegrain, Finesharp, Dotkill and Hysteria. Is this because one of these DLL are unoptimized? Thanks. RE: low processor usage - reason? - Selur - 23.02.2019 The Filter combination you chose also uses a lot of ram on higher resolutions. Using a 1280x720 source ant: # Imports After ~10min, the RAM usage is > 11 GB and still increasing, so my guess is that if the same is happening on your system, you might run out of RAM. ![]() Cu Selur Ps.: I'll do some more testing and may be add an option to Hybrid to limit the RAM usage of Vapoursynth. PPs.: CPU usage is down to 40% now that ~16GB are used,.. my guess is that one of the filters has a bug uses more and more memory and slows down the more memory it uses (hitting 17GB now). RE: low processor usage - reason? - Selur - 23.02.2019 Got it, it's DotKill. Replacing the file in your Hybrid\64bit\vsfilters\DeCrawlFilter\DotKill folder with the attached version should fix the issue. Cu Selur RE: low processor usage - reason? - kkf_hu - 23.02.2019 (23.02.2019, 09:58)Selur Wrote: Got it, it's DotKill. yea, in the meantime i also got it figured out that it was dotkill. ill try the new one, thx. (23.02.2019, 21:28)kkf_hu Wrote:(23.02.2019, 09:58)Selur Wrote: Got it, it's DotKill. yea it did the trick alright, thx Selur |