I wonder what rules on optimizations that increase build time we'd want.
Some of us (due, sorear) code on very slow machines, and I don't want to
hurt them badly; some changes can make concrete gains, though.
For example, pngcrush shaves 700KB off binary downloads, and I later learned
that advpng can make that 840.
The time cost on a machine that does "make TILES=y -j4" in 2m48.483s, is
(-j1):
19s pngcrush
8s pngcrush with hardcoded optimization choice
37s advpng
This may be just a 5% slowdown, but then, it's another ~1.5 minute on slow
machines...
For now, I made it do these optimizations whenever you do a build that
optimizes code. Ie, any but "debug", "NO_OPTIMIZE=y" or "HURRY=y".
Not having advancecomp nor pngcrush installed will have the same effect.
Is this ok with you?
(These are optimizations of built packages, not of source.)
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Crawl-ref-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crawl-ref-discuss
