A few test results to show how performance scales with number of threads.
I've run the tests using two different short clips (to help establish scaling behaviour is independent of video content for 'typical' video {ie not pathological cases}). I've also run initial tests twice to see what magnitude variation is due to (low) background activity & hence how many figures in the results are significant. Lastly I've run tests with both the last official release of mvtools & the latest tsp mvtools-comp2, for comparison.
Code:
clip1 mvtools-tsp2
run1
Name Input FPS
job1 noSetMT 6.00 1.0000
job4 SetMT1 5.96 0.9933
job7 SetMT2 11.80 1.9667
job10 SetMT3 17.53 2.9217
job13 SetMT4 22.98 3.8300
job16 SetMT0 22.91 3.8183
run2
Name Input FPS
job1 noSetMT 6.00 1.0000
job4 SetMT1 5.98 0.9967
job7 SetMT2 11.82 1.9700
job10 SetMT3 17.49 2.9150
job13 SetMT4 22.98 3.8300
job16 SetMT0 23.19 3.8650
clip1 mvtools-orig
run1
Name Input FPS
job1 noSetMT 6.01 1.0000
job4 SetMT1 5.98 0.9950
job7 SetMT2 11.78 1.9601
job10 SetMT3 17.53 2.9168
job13 SetMT4 23.09 3.8419
job16 SetMT0 22.83 3.7987
run2
Name Input FPS
job1 noSetMT 6.00 1.0000
job4 SetMT1 5.98 0.9967
job7 SetMT2 11.80 1.9667
job10 SetMT3 17.32 2.8867
job13 SetMT4 23.21 3.8683
job16 SetMT0 22.95 3.8250
clip2 mvtools-tsp2
run1
Name Input FPS
job1 noSetMT 6.07 1.0000
job4 SetMT1 6.04 0.9951
job7 SetMT2 11.92 1.9638
job10 SetMT3 17.71 2.9176
job13 SetMT4 23.44 3.8616
job16 SetMT0 23.21 3.8237
clip2 mvtools-orig
run1
Name Input FPS
job1 noSetMT 6.07 1.0000
job4 SetMT1 6.04 0.9951
job7 SetMT2 11.92 1.9638
job10 SetMT3 17.71 2.9176
job13 SetMT4 23.47 3.8666
job16 SetMT0 23.20 3.8221