On Tue, Jul 1, 2014 at 6:22 AM, Gregory Szorc <g...@mozilla.com> wrote: > > Given it's 9 PM and I have a beer in me, I will also suggest the > "honeybadger" approach: just use items() and friends without worrying about > performance. Will non-iterable functions make pymake a little slower? > Probably. But is this the biggest performance concern? Probably not (we know > variable evaluations are quite painful on large make files and I doubt > iteration over 10,000+ item collections or iteration where lazy evaluation > is important has much to do with anything).
See, I always knew beer was a solution! > Besides, Mozilla has already stopped supporting pymake to build Firefox > because it's slower than GNU make. Given that pymake was invented to make > building Firefox faster [on Windows], I'd say that leaves pymake as purely a > "research" project. I'd say it is acceptable for pymake to continue a long > tradition of academic projects and not care too much about performance. Performance is a constraint for us, we have a pretty big Make system that we generate Visual Studio projects from and life is better when it's snappy. But I can't see how/if materialized views make any difference and on my Python3 platform, they will already be lazy, so I'm leaning towards code simplicity. I'll make an effort to get the Firefox build going, but I usually can't get representative results in my build environment. Thanks for your input! - Kim _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
