generic-library/ffmpeg
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

clarify previous revision on optimization justification

Browse Source 
Originally committed as revision 11598 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
Mike Melanson 2008-01-22 21:57:19 +00:00
parent ac59e7f4b1
commit 07bf0cc9cf
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/optimization.txt
View File

@ -30,15 +30,15 @@ NOTE: If you still don't understand some function, ask at our mailing list!!!
When is an optimization justified?
----------------------------------
Normally, clean & simple optimizations on widely used codecs can achieve
an overall speedup of 0.1%. These speedups accumulate and can make a big
difference after awhile. Also, if none of the following factors get
worse due to an optimization -- speed, binary code size, source size,
source readability -- and at least one factor improves, then an
optimization is always a good idea even if the overall gain is less than
0.1%. For obscure codecs that are not often used, the goal is more
toward keeping the code clean, small, and readable than to make it 1%
faster.
Normally, clean and simple optimizations for widely used codecs are
justified even if they only achieve an overall speedup of 0.1%. These
speedups accumulate and can make a big difference after awhile. Also, if
none of the following factors get worse due to an optimization -- speed,
binary code size, source size, source readability -- and at least one
factor improves, then an optimization is always a good idea even if the
overall gain is less than 0.1%. For obscure codecs that are not often
used, the goal is more toward keeping the code clean, small, and
readable instead of making it 1% faster.
WTF is that function good for ....: