diff options
author | Mike Melanson | 2008-01-22 21:57:19 +0000 |
---|---|---|
committer | Mike Melanson | 2008-01-22 21:57:19 +0000 |
commit | 07bf0cc9cf386a622fa27c9dc82fbeb11dff7c08 (patch) | |
tree | a0452fb71078f26321f69eb4def456661101839d /doc/optimization.txt | |
parent | ac59e7f4b1a7562d7f448646205ef1df94d51c4c (diff) |
clarify previous revision on optimization justification
Originally committed as revision 11598 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'doc/optimization.txt')
-rw-r--r-- | doc/optimization.txt | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/optimization.txt b/doc/optimization.txt index f5a86a3eee..27fcbba02f 100644 --- a/doc/optimization.txt +++ b/doc/optimization.txt @@ -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 ....: |