AVSMeter 3.0.9.0

[videoh]

Sorry, missed your length parameter.

Maybe BlankClip is just so fast that even a very large length won't matter.

Groucho2004 can probably enlighten us further.

[wonkey_monkey]

blankclip constructs a single blank frame on startup and just returns a pointer to it each time. It doesn't actually do anything per frame - not even calling env->NewVideoFrame() - so it's super fast. Same with colorbars, although that has a parameter to disable the framestore:

colorbars(staticframes = false)

[Groucho2004]

Originally Posted by wonkey_monkey

blankclip constructs a single blank frame on startup and just returns a pointer to it each time. It doesn't actually do anything per frame - not even calling env->NewVideoFrame() - so it's super fast. Same with colorbars, although that has a parameter to disable the framestore:

colorbars(staticframes = false)

Quite the difference:

colorbars(staticframes = x, pixel_type = "yv12").loop(10000).trim(0, 99999999)

staticframes = true

Frames processed:               314750000 (0 - 314749999)
FPS (min | max | average):      5811893 | 32190153 | 30993818
Process memory usage (max):     23 MiB
Thread count:                   9
CPU usage (average):            23.6%

Time (elapsed):                 00:00:10.155

staticframes = false

Frames processed:               287810 (0 - 287809)
FPS (min | max | average):      7370 | 28961 | 28340
Process memory usage (max):     23 MiB
Thread count:                   9
CPU usage (average):            23.5%

Time (elapsed):                 00:00:10.156

[Groucho2004]

v2.9.0

• Added Veselin Georgiev's libcpuid (again) for better detection of some CPU features (such as number of physical/logical cores of contemporary CPUs)
• Minor other fixes
• Refactoring

[wonkey_monkey]

If it doesn't exist already, would it be possible to add a switch to output seconds per frame instead of frames per second? It feels like it might be more useful, or at least differently useful, for benchmarking.

[Groucho2004]

Originally Posted by wonkey_monkey

If it doesn't exist already, would it be possible to add a switch to output seconds per frame instead of frames per second? It feels like it might be more useful, or at least differently useful, for benchmarking.

There are two INI file options:

DisplayFPS=1
DisplayTPF=0

from the included documentation:

"DisplayFPS" (0 or 1)
If set to "1", frames/second is printed to the console.

"DisplayTPF" (0 or 1):
If set to "1", time/frame (in milliseconds) is printed to the console.

Edit: These two options are not mutually exclusive.

[wonkey_monkey]

I should never have doubted you. And I should have read the manual.

[Groucho2004]

v2.9.1

• Fixed an error reporting bug
• More accurate memory usage measurements
• Limit performance data section in log/csv files to 10000 entries

[Groucho2004]

v2.9.2

• Fixed wrong AVISYNTH_INTERFACE_VERSION
• Updated dates in some messages

[LouieChuckyMerry]

Thanks again for AVSMeter, Groucho2004 and I've a question (which will most likely highlight my ignorance ). Under "Features" it states '"Running" scripts with virtually no overhead...', which I kinda-sorta understand. What I wonder is if "running" multiple scripts simultaneously with AVSMeter would change the output statistics, like running multiple non-multithreaded real scripts simultaneously does? Let me try again: If I "ran" three scripts in a row with AVSMeter--Script A, Script B, and ScriptC--then ran the three scripts simultaneously with AVSMeter, would the statistics for the three pairs of log files--Script A alone and Script A simultaneously, Script B alone and Script B simultaneously, Script C alone an Script C simultaneously--be the same? I need more coffee...

[Groucho2004]

Originally Posted by LouieChuckyMerry

What I wonder is if "running" multiple scripts simultaneously with AVSMeter would change the output statistics, like running multiple non-multithreaded real scripts simultaneously does? Let me try again: If I "ran" three scripts in a row with AVSMeter--Script A, Script B, and ScriptC--then ran the three scripts simultaneously with AVSMeter, would the statistics for the three pairs of log files--Script A alone and Script A simultaneously, Script B alone and Script B simultaneously, Script C alone an Script C simultaneously--be the same? I need more coffee...

First of all, AVSMeter only allows a single instance by default. If you want to run multiple instances you have to enable that in avsmeter.ini.

How much multiple instances of AVSMeter affect the statistics for each instance depends on how demanding each instance is. If one instance already eats up most of the CPU cycles then the other instances will of course be heavily affected. It also depends on the process priority for each instance. Also, if you mess around with thread affinity, things get even more complicated.

Lastly, if the Windows thread scheduler has a bad day, the CPU cycles may go wild and do silly things.

[StainlessS]

Not just depend upon CPU, hard drive usage (seeking etc) would likely also play a significant part, probably other stuff too.
Not a good idea anyway (assuming you want reasonable results).

[Groucho2004]

There's now a 45 minute (!) tutorial for AVSMeter on youtube.
https://www.youtube.com/watch?v=RxXP0oNJh4Q

Thanks Andrew Swan!

[LouieChuckyMerry]

Groucho2004 and Bender, er, StainlessS: Thanks very much for the answers (and Happy Saturday!). I'll stick with one instance at a time so that I'm the only silly thing in the room.

[LouieChuckyMerry]

Back for more answers--still Happy Saturday!--and thank you for your patience . I'm trying to understand just how to use AVSMeter to, hopefully, improve encoding speed in AviSynth+ x86 on a Windows 7 x64 quad-core setup. I'm testing different "SetMemoryMax()" and "PreFetch()" combinations with the script:

SOURCE INFORMATION HERE
SetMemoryMax(xxxx)
SetFilterMTMode("Default_MT_Mode",2)
SMDegrain(TR=3,ThSAD=600,RefineMotion=True,Plane=0,Chroma=False,n16=True,n16_Out=True)
FastLineDarkenMod4()
ConvertToDoubleWidth()
F3KDB(Y=100,Cb=100,Cr=100,GrainY=0,GrainC=0,Input_Mode=2,Output_Mode=2)
ConvertFromDoubleWidth()
PreFetch(x)

and I'm unclear what to make of the fact that a trim test with "SetMemoryMax(0)", which I think results in the default memory amount (a number I can't discern from the Wiki), and "PreFetch(5)" (which gave better results than 6, 7, or 8 in earlier tests without any "SetMemoryMax()" line) "run" with AVSMeter results in:

[Runtime info]
Frames processed:               1130 (0 - 1129)
FPS (min | max | average):      0.392 | 272826 | 9.702
Process memory usage (max):     1157 MiB
Thread count:                   21
CPU usage (average):            61.6%

but only achieves 2.99 fps and appears to use 100% of the CPU when viewed in Windows Task Manager when actually run in AviSynth+. Any elucidation is much appreciated.

[Groucho2004]

Originally Posted by LouieChuckyMerry

but only achieves 2.99 fps and appears to use 100% of the CPU when viewed in Windows Task Manager when actually run in AviSynth+.

I do not understand this part -> "when actually run in AviSynth+".

[gonca]

Originally Posted by LouieChuckyMerry

Back for more answers--still Happy Saturday!--and thank you for your patience . I'm trying to understand just how to use AVSMeter to, hopefully, improve encoding speed in AviSynth+ x86 on a Windows 7 x64 quad-core setup. I'm testing different "SetMemoryMax()" and "PreFetch()" combinations with the script:

SOURCE INFORMATION HERE
SetMemoryMax(xxxx)
SetFilterMTMode("Default_MT_Mode",2)
SMDegrain(TR=3,ThSAD=600,RefineMotion=True,Plane=0,Chroma=False,n16=True,n16_Out=True)
FastLineDarkenMod4()
ConvertToDoubleWidth()
F3KDB(Y=100,Cb=100,Cr=100,GrainY=0,GrainC=0,Input_Mode=2,Output_Mode=2)
ConvertFromDoubleWidth()
PreFetch(x)

and I'm unclear what to make of the fact that a trim test with "SetMemoryMax(0)", which I think results in the default memory amount (a number I can't discern from the Wiki), and "PreFetch(5)" (which gave better results than 6, 7, or 8 in earlier tests without any "SetMemoryMax()" line) "run" with AVSMeter results in:

[Runtime info]
Frames processed:               1130 (0 - 1129)
FPS (min | max | average):      0.392 | 272826 | 9.702
Process memory usage (max):     1157 MiB
Thread count:                   21
CPU usage (average):            61.6%

but only achieves 2.99 fps and appears to use 100% of the CPU when viewed in Windows Task Manager when actually run in AviSynth+. Any elucidation is much appreciated.

You do realize that the effects of an encoder are not factored in.
The 2.99 fps when run in windows is probably the result of the encoder.

[Groucho2004]

Originally Posted by gonca

The 2.99 fps when run in windows

"when run in windows"???

I kinda understand now that Chucky is comparing apples and oranges but the terminology you guys are using makes no sense.

[Natty]

Originally Posted by Groucho2004

I do not understand this part -> "when actually run in AviSynth+".

maybe - when actually encoding

[gonca]

Originally Posted by Groucho2004

"when run in windows"???

I kinda understand now that Chucky is comparing apples and oranges but the terminology you guys are using makes no sense.

Sorry
I should have written "run in Windows", with quotes, indicating that it really is being run in an encode workflow.
I was just trying to figure out what the op was referring to.
Apologies for confusing the issue