Benchmark testing should be done with non-trivial code, and given these
frameworks abstract databases, and that abstraction can affect
performance, it should probably include tests that include database access.
I agree.
We don't know if the tester tried a business application, then saw his
Cake has a lot of things going for it, and I mean A LOT that the other
PHP frameworks don't have. However, I disagree that performance
doesn't matter much. A lot of us (especially in this economy) are
downsizing our servers which is one of the main reason to even look at
a PHP frameworks over
My two cents:
If your primary goal is to have a FAST webpage serving images and
multimedia content, you build static HTML with maybe some PHP using
lighttpd.
If you are building a social network/heavy interaction app (think
friendfeed/facebook) you either build the framework yourself or spend
For most people making such apps the speed of the dispatcher, template
engine etc is unimportant. The parts slowing the app would be heavy
SQL, SOAP/XML-RPC-request to other apps or huge batch ETLs. For most
people (including most public websites) the most important thing would
be faster
Absolutely true, CakePHP is most definitely a developers framework,
and developers are easy to please in regards to performance. Users
and clients on the other hand, are not. This is true in any framework
(or lack there of). Performance matters, why develop in such a
wonderful framework if its
CakePHP is a developers framework, true, its inherently going to be
slower than pure HTML etc; indeed. What has me shaking my head is
looking at all the other frameworks going from 1.x to 2.x increasing
their performance with each major release whereas we've gone backwards
at a 1:2 (1:4 in
I would love to develop my own website where performance was an
issue! :)
--~--~-~--~~~---~--~~
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
Where can we learn about these tweaks or how to stream line cake?
Chad
On Fri, Jan 2, 2009 at 7:43 PM, rtconner rtcon...@gmail.com wrote:
CakePHP is a developers framework, true, its inherently going to be
slower than pure HTML etc; indeed. What has me shaking my head is
looking at
These benchmarks dont mean anything.
Do a benchmark using a full fledged system (perhaps a whole social
community) and see how the work. Simply hello world pages are nothing
because no frameworks are used for that.
--~--~-~--~~~---~--~~
You received this message
Yii project had updated their Performance Comparison page:
http://www.yiiframework.com/performance
The core developer of Yii also created a project to host the code
needed for benchmarks:
http://code.google.com/p/phpmark/
Based on that project, I did some tests on my computer and the result
is
I won't say I have looked extensively through the code provided for all
frameworks, but the CakePHP 1.2 BenchmarkController is far from thorough.
Its bypassing view parsing, by putting a die() call in the controller
action:
You could have a look at the result I did. ;)
---
kiang
On 1月2日, 上午6時37分, Graham Weldon gra...@grahamweldon.com wrote:
I won't say I have looked extensively through the code provided for all
frameworks, but the CakePHP 1.2 BenchmarkController is far from thorough.
Its bypassing view
Your benchmarks are still Hello World examples, from what I can see there.
Great as a benchmark for those using static only pages with their
frameworks, but I suggest that the majority of developers out there are
doing something more complex.
Cheers,
Graham Weldon
kiang wrote:
You could have a
The basic case could check the baseline of a framework. Once the cache
enabled, most requests are served like static pages.
Maybe the test should include the model layer, but some of the
frameworks didn't have ORM feature included.
Waiting for somebody to do the more complex benchmarks. :)
---
14 matches
Mail list logo
