On 5 marras, 19:34, BrendonKoz <[EMAIL PROTECTED]> wrote:
> Another issue with benchmarking is that when dealing with OOP, or any
> code in PHP, TMTOWTDI (There's More Than One Way To Do It)... So, to
> properly benchmark any framework, one would have to know each
> framework inside and out to take advantage of all the tricks to
> increase performance when necessary, and increase development time
> when not necessary.
>
> This is one of the major issues that many framework performance
> testers have found...they don't know their frameworks as best as
> possible, or may know one to a varying degree more than another and
> not make as many "allowable mistakes" in one over another. It's hard
> to get a true non-bias performance test, even if you're trying really
> hard. ;)
That is true. However I'm going to use each frameworks helpers and
components when available. That way I'll find how significant the
trade-off between shorter development time and system performance is?
-Kalle
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
