Some extra words.

[qscale] / README

diff --git a/README b/README
index bcccb86ca0e35f5c16971f7430591fac655cc2e1..a912395bc6411b582d0b0c4a0c1505eb28727ec5 100644 (file)
--- a/README
+++ b/README
@@ -80,6 +80,16 @@ The following optimizations are possible but not done (yet?):
    on 64-bit x86-compatible (usually called amd64 or x86-64) machines. In
    fact, out of the box it might not even compile on such machines.
 
+Finally, a word of advice: Even the fastest scaler can never be as fast as not
+scaling. If you can do less work, or move it to a time where it is less user
+visible, do that no matter how you scale your pictures. In particular, cache
+your downscaled pictures if you can, preferrably ahead of time. If you cannot
+predict in advance exactly what size (or sizes) you'll need, consider making
+mipmaps (ie. one image of half the resolution each way, another one of a quarter
+the resolution each way etc., down to a reasonable size) and scaling from them
+instead. It will be much faster (primarily due to less loading time) and the
+difference in quality is nearly impossible to detect, at least in my tests.
+
 qscale is Copyright 2008 Steinar H. Gunderson <sgunderson@bigfoot.com>, and
 licensed under the GNU General Public License, version 2. The full text of
 the GPLv2 can be found in the included COPYING file.