A long term redesign of the software could definitely be beneficial.
We have done it twice, without much benefit. I'm all for evolutionary way.
Actually, we'd never have made it this far without the "revolutionary" redesign done by Lee earlier this year. Our performance old PHP code was breaking under far less load than we have all the time now.
While, we do need to improve our DB performance, but without better stats, we can't say for certain that there aren't any PHP bottlenecks. And PHP bottlenecks could eventually arise if we improve DB performance significantly.
I'm all for the evolutionary way, but I think there's room for someone who wants to work on a revolutionary way while others improve our current system.
Yours Mark Christensen
On Mon, Dec 09, 2002 at 03:24:20PM -0500, Mark Christensen wrote:
While, we do need to improve our DB performance, but without better stats, we can't say for certain that there aren't any PHP bottlenecks. And PHP bottlenecks could eventually arise if we improve DB performance significantly.
Programming languages like PHP and to even greater extend Perl, provide both very high and very low level features, and if PHP/Perl program actually happen to be a bottleneck, it's usually possible to profile it (very important) and fix - for example some regular expresion may be called very often, while it could be easily changed into a couple of index() and a substr(), and things like that.
wikitech-l@lists.wikimedia.org