aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Niedermayer <michaelni@gmx.at>2008-01-22 14:45:20 +0000
committerMichael Niedermayer <michaelni@gmx.at>2008-01-22 14:45:20 +0000
commit8f738eea4373cdb5b7c3bb42739d2b98aabac34d (patch)
tree93d38f219969991caa4c46a5818f7a8f2738882c
parente5b10e31745f33c3d7af7986a1ad7d15746b5af4 (diff)
downloadffmpeg-8f738eea4373cdb5b7c3bb42739d2b98aabac34d.tar.gz
"What speedup justifies an optimization" section
Originally committed as revision 11595 to svn://svn.ffmpeg.org/ffmpeg/trunk
-rw-r--r--doc/optimization.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/optimization.txt b/doc/optimization.txt
index f42eaba12c..61dc5c40a6 100644
--- a/doc/optimization.txt
+++ b/doc/optimization.txt
@@ -23,6 +23,15 @@ and how they can be optimized.
NOTE: If you still don't understand some function, ask at our mailing list!!!
(http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel)
+What speedup justifies an optimizetion?
+Normaly with clean&simple optimizations and widely used codecs a overall
+speedup of the affected codec of 0.1% is enough. These speedups accumulate
+and can make a big difference after a while ...
+Also if none of the following gets worse and at least one gets better then an
+optimization is always a good idea even if the overall gain is less than 0.1%
+(speed, binary code size, source size, source readability)
+For obscure codecs noone uses, the goal is more toward keeping the code clean
+small and readable than to make it 1% faster.
WTF is that function good for ....: