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

Ministry of English Composition edits

Browse Source 
Originally committed as revision 11597 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
Mike Melanson 2008-01-22 18:21:12 +00:00
parent 5e123bd359
commit ac59e7f4b1
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/optimization.txt
View File

@ -28,16 +28,17 @@ NOTE: If you still don't understand some function, ask at our mailing list!!!
(http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel) (http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel)
What speedup justifies an optimizetion? When is an optimization justified?
--------------------------------------- ----------------------------------
Normaly with clean&simple optimizations and widely used codecs a overall Normally, clean & simple optimizations on widely used codecs can achieve
speedup of the affected codec of 0.1% is enough. These speedups accumulate an overall speedup of 0.1%. These speedups accumulate and can make a big
and can make a big difference after a while ... difference after awhile. Also, if none of the following factors get
Also if none of the following gets worse and at least one gets better then an worse due to an optimization -- speed, binary code size, source size,
optimization is always a good idea even if the overall gain is less than 0.1% source readability -- and at least one factor improves, then an
(speed, binary code size, source size, source readability) optimization is always a good idea even if the overall gain is less than
For obscure codecs noone uses, the goal is more toward keeping the code clean 0.1%. For obscure codecs that are not often used, the goal is more
small and readable than to make it 1% faster. toward keeping the code clean, small, and readable than to make it 1%
faster.
WTF is that function good for ....: WTF is that function good for ....: