From 07bf0cc9cf386a622fa27c9dc82fbeb11dff7c08 Mon Sep 17 00:00:00 2001 From: Mike Melanson Date: Tue, 22 Jan 2008 21:57:19 +0000 Subject: clarify previous revision on optimization justification Originally committed as revision 11598 to svn://svn.ffmpeg.org/ffmpeg/trunk --- doc/optimization.txt | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'doc/optimization.txt') 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 ....: -- cgit v1.2.3