On Thu, 7 Jun 2007, Perrin Harkins wrote:
On 6/6/07, Tina M=FCller <[EMAIL PROTECTED]> wrote: > well, many people say, why optimize code if the database is slow anyway. No offense, but those people are entirely correct. Choosing a template module because of its speed when your application is constrained by your database doesn't make sense. None of the popular template modules are slow at this point.
but you still save CPU if you have fast templating. maybe you can save a number of machines. of course it's right that in most cases you shouldn't choose the templating engine by its speed as the first critera. when i said that many people don't care about speed because of their database slowness i also meant that i wonder why people don't rethink their architecture. if the database is so slow that it makes no difference how slow your perl-code is, then there's often a possibility to optimize that (cache things, use a search engine for searches instead of the database, change replication architecture, ...)
