myk at mozilla.org
Fri Sep 13 15:37:15 UTC 2002
>What "recent regressions"?
The ones that went into 2.16 (primarily templatization). b.m.o is
noticably slower now than it was, even after we fixed the egregrious
problems post-upgrade. This slowness has a significant (if difficult to
measure) impact on developer efficiency.
As we implement additional features and rewrites, we need to be very
careful to distinguish between performance regressions that are
unavoidable because we really need the additional functionality and
those that are the result of design or programming error (lack of
indexes, poor schema design, looping over queries that could be run
once, over-abstraction, feature bloat, etc.).
Improving performance will help somewhat, but many of those improvements
are still a ways off, and we don't want to spend all that additional
speed anyway, so we need to hold the line as best we can.
More information about the developers