Avisynth encoding slowly after overclocking CPU

[VideoFanatic]

I have an Intel Core i7 2700K (8 core) and an Asus P8Z77 V-Pro motherboard. For a long time I overclocked it from 3.6 Ghz to 4.180 Ghz. I got between 13-14 FPS when using the script below on my videos. I did a manual overclock by setting the cores to 40 and the memory frequency to 104.5 and of course I increased the CPU voltage. I did a stress test and my PC was stable.

However since then I got a new CPU cooler so I decided to see if I could get a faster overclock. I think I may have used the Auto overclock option in my Bios at some point and I also tried to manually overlclock to 4.6 Ghz. In the end I decided to go back to the original overclock I had of 4.180 Ghz except I kept the memory frequency on the default of 100 and chose a setting of 42 for the cores so I got 4.2 Ghz. The problem is that I'm now only getting between 10-11 FPS. Just to make sure it wasn't due to problem videos, I tested on the same video before and after my overclock.

I tried several different setmtmodes such as 5,12 and found 5,9 to give the fastest FPS encoding speed so I don't think it's that which is causing the problem as I used that before and after I did my overclocks.

setmtmode(5,9)
Mpeg2Source("E:\Video.d2v", CPU=6)
setmtmode(2)

McTemporalDenoise(settings="medium", interlaced=true) 

AssumeTFF() 
QTGMC(Preset="Super Fast") 
Vinverse() RemoveSpots() AddGrainC(var=1.0,uvar=1.0) SeparateFields() SelectEvery(4,0,3) Weave() 

Tweak(Hue=0, Sat=1.0, Bright=-10, Cont=1.15, Coring=False) 

Crop(0,0,-16,-14)
AddBorders(16,6,16,8, $000000)

I'm not looking for script help, there are reasons why I need this script.

CPU-z shows my speed as 4.2 GHz so I don't understand how my PC is acting like the clock speed is slower than what it is.

I did create a backup image of my hard drive from before this problem started. Would restoring this backup fix the problem. Also just wondering if Bios changes would be saved on the hard drive as well?

[Selur]

1. using SetMemoryMax(768) or SetMemoryMax(1024) or even higher values might speed up the processing quite a bit depending on the number of MT threads and the filters you use; (for the default setMemoryMax(amount) you currently use, see: http://avisynth.org/mediawiki/Internal_functions/Control_functions)
2. SetMtMode(3,9) instead of SetMtMode(5,9) should use less memory and be faster
3. depending on why you feed witht his script adding:
   distributor()
   return last
   to the end of the script might speed up things.

[nic2k4]

CPU-z shows my speed as 4.2 GHz so I don't understand how my PC is acting like the clock speed is slower than what it is.

What does it show on the memory tab? Compare that with the SPD tab. The speed of a PC depends on more than just the CPU clock, the memory clock and timings will also have a measurable impact on performance. Keep in mind the more you raise the memory clock (it usually is linked to the CPU's) the more cycles it needs to access and transfer data. Your DDR3-1600 memory that is rated 7-7-7-20 at 800 MHz might need 9-9-9-24 timing at 820 MHz. If you didn't reset the timing values after all your experiments, you may be slowing down your system inadvertently.

[VideoFanatic]

@nic2k4 - It seems to be my Bios that's the problem as I accidentally activated the auto overclock function in my bios. I had a bus speed of 100 Mhz and 4.6 Ghz clock speed. Yet for some reason the CPU when auto overclocked doesn't act like it's at the speed it is. Using the reset to defaults option on it's own did nothing even though it said in the Bios that my clock speed was now 4.2 Ghz instead of 4.6.

Instead I re-installed the firmware which reset the Bios to the defaults and my CPU is now acting like it is actually at 4.6 Ghz. I'm using a bus speed of 100 Mhz.

The only problem remains is that my videos can sometimes encode at a random FPS of between 7 - 14 FPS instead of 13-14 FPS all the time like it should.

On CPU-z the Memory tab shows 9-9-9-24 at 800 Mhz. The SPD tab shows the same thing.

@Selur: I looked at the page you mentioned but I don't have a clue what I'm supposed to do - how do I find out the default setmemorymax that I'm currently using? Where should I put that SetMemoryMax line in my script?

I'll try SetMtMode(3,9) instead of SetMtMode(5,9) but I thought I was supposed to use SetMtMode(5,9) for stability reasons?

What does adding the following to the end of the script do?:

distributor()
return last

[Selur]

how do I find out the default setmemorymax that I'm currently using?

the interesting part is:

In the 2.5 series the default Memory Max value is 25% of the free physical memory, with a minimum of 16MB. From v2.58, the default Memory Max is also limited to 512MB.

-> assuming you use a not to old Avisynth version with on a system with 2GB+ RAM your current SetMemoryMax amount is 512.

Where should I put that SetMemoryMax line in my script?

It should be the the first line in your script.

I'll try SetMtMode(3,9) instead of SetMtMode(5,9) but I thought I was supposed to use SetMtMode(5,9) for stability reasons?

Yes, mode 5 is more stable than mode 3, but it is only required for a small bunch of filters.
see: http://avisynth.org/mediawiki/MT_support_page#SetMTMode.28.29_Mode
Normally all input filters are fine with mode 3 (some are even fine with 2).
read http://avisynth.org/mediawiki/MT_modes_explained and http://avisynth.org/mediawiki/MT_support_page#SetMTmode.28.29_related to better understand what the mode values mean

What does adding the following to the end of the script do?:

distributor()
return last

distributor(): explicitly triggers the distribution of the content to the thread
return last: makes sure the output is not mixed up through the distribution
see: http://avisynth.org/mediawiki/MT_modes_explained
Note: This might help, but this might also hurt. -> Simply add it and see if the processing is faster this way.

Cu Selur