If I used Code Igniter or the Cake Framework, will it affect the performance of my application?
A:
Possible disadvantages: (Sometime depends on your project)
- Different framework have different coding convention. You have to learn these
- Sometime you’ll not find any library which might be useful for you.
- Not for small projects. Simple project custom coding will work faster than setting up a framework.
- Extra overhead may affect performance
- Not necessarily more secure (you'll need to pay attention to updates and such)
- Much, much harder to customize
- Takes time to learn and master
If you want to compare different frameworks.
NAVEED
2010-08-28 12:27:14
so if i have large project custom coded that will work faster!! then using a php framework
getaway
2010-08-28 12:32:04
@Solomon Saleh: Yes. PHP Framework is not very useful for small projects.
NAVEED
2010-08-28 12:33:43
This post and the comments are not making any sense.
Matti Virkkunen
2010-08-28 12:40:05
@NAVEED a PHP Framework will greatly simplify your efforts while development (even for small projects), isn't it? Ohh if performance is not that critical (than delivery time) we should use these frameworks. After all computers are meant for computation and making life simpler.
Ankit Jain
2010-08-28 12:40:12
And a Framework has usually very good built-in things for security.
shamittomar
2010-08-28 12:41:05
NAVEED by "small projects" what do you mean.. A lot of frameworks shine because you're able to setup a site in no time. Coding from scratch in most cases will always take longer. That article provides near to no information, especially on security - Which is one of the most important, almost the most important part of a good framework.
Kieran Allen
2010-08-28 12:41:30
@Kieran Allen: I have a project: Get two numbers from user and print primary numbers in the range. What framework do you prefer!
NAVEED
2010-08-28 13:25:26
Are you serious?! Hes talking about an application not a simple script... Looks like you're just trying to plug your own post. Nice.
Kieran Allen
2010-08-28 13:32:21
@Kieran Allen: He did not ask performances of different php frameworks but he asked what possible effect on performance when using framework. It may be execution speed, it may be time spent learning a new framework, etc. But people are comparing different frameworks here which is off topic. Look at accepted answer.
NAVEED
2010-08-28 13:54:04
+1
A:
Look here, PHP framework comparison benchmarks.
But, if you need very fast performance, I would advise Yii because of its awesome performance.:
shamittomar
2010-08-28 12:35:43
it even has jquery ajax support which is an excellent, deos yii have an active community!!
getaway
2010-08-28 12:51:07
Yes, 250+ extensions: http://www.yiiframework.com/extensions/ and great forum: http://www.yiiframework.com/forum/
shamittomar
2010-08-28 12:52:45
-1 since benchmarks are for all practical purposes useless. They are only useful if your benchmarking the same real world problem as you're trying to solve. So it's mostly just marketing propeganda (since the final real world application performance will be FAR more dependent on your programming skill than the "speed" of the framework you choose...
ircmaxell
2010-08-28 13:10:27
I didnt downvote, but even if benchmarks would have anything but suggestive meaning, that article is two years old and can only give an indicator about framework performance at that time.
Gordon
2010-08-28 13:11:05
Is he asking for performance of different frameworks or he asked effect on performance when using a framework for a project ????
NAVEED
2010-08-28 13:55:25
+5
A:
If you define performance as speed of execution, then the answer is
- Yes, it will degrade performance - always.
Frameworks offer abstractions over PHP's native functions. Whenever you put an abstraction onto something, you incur the penalty of loading the abstraction and invoking it's functions. Frameworks are usually general abstractions, that cater to a lot of UseCases. Solving a specific UseCase in your application can likely be solved with less abstraction.
But with frameworks you gain better modularization, faster development times (if you know the framework), better maintainability and (hopefully) tested code, which is usually worth it. That's not to say, always use a framework, but always consider the tradeoff - then decide.
As for benchmarks, well, have a look at
Gordon
2010-08-28 13:05:08
And what about time spent on learning and switching between different frameworks for beginners
NAVEED
2010-08-28 13:16:58
@NAVEED that's why I wrote "if you know the framework". And [I still believe beginners of PHP should not use frameworks](http://stackoverflow.com/questions/2064424/zend-framework-versus-kohana-versus-symfony/2064590#2064590)
Gordon
2010-08-28 13:23:54
"Always" is too strong. A random example from the php docs: md5_file() is an abstraction over fopen(); md5(); fclose();, but using the abstraction probably has better performance than not. There are a lot of "it depends" issues. Remember we've got to compare YourCode vs YourCode+Framework. For example, if the framework makes it easy to do caching which you wouldn't have time to write yourself, using the framework could result in a better performing application.
Douglas
2010-08-28 13:30:03
@Douglas `md5_file` is a native PHP function. When I am talking about abstraction here, I am talking about Userland implementations, because that's what frameworks are. Also, I am not saying writing your own abstraction is always faster for every developer. That indeed depends on individual skill. My point is, frameworks usually offer more abstraction that you need to solve for a concrete problem. Your framework's caching module might offer multiple backend adapters, when you only use `memcached`. Using `memcached` directly will be faster than using it through an additional abstraction on top.
Gordon
2010-08-28 13:44:03
A:
Take a look at these two answers:
One on benefits and disadvantages of frameworks
One on benchmark comparisons of frameworks, and how they are all but meaningless
ircmaxell
2010-08-28 13:06:35