Kohana vs Yii vs...? Which framework is able to make the most efficient use of server resources?

Question

PHP

We need practical comparative characteristics of frameworks Kohana, Yii, etc.
For example in the form of graphs.
In Kohan, ORM raises big performance issues as traffic grows.
Also garbage with folder searches.
We are looking for a class first in the application, then in the system, then in subfolders, etc.
It seems that this bodyaga will also somehow affect performance.
Caching is also necessary and competent, so that the memory does not clog.
While I'm digging, studying, looking, thinking.
But for now, I come to the conclusion that self-writing is better without any ORM there, but stupidly SELECT * FROM queries without any abstruse bodyagi.
Moreover, my thinking is based on how to squeeze everything out of the server.
Therefore, part of the functionality will be on Node.js
I am sure that among you there are already those who dealt with this and chose the best.
Actually, the question for you is: what did you choose and why?

Answer 1

Before you optimize, you need to understand what to optimize. The number of images per second, what operations are performed with the database, the required percentage of reliability ... You have the syndrome of premature optimization .
In 80% of cases, everything is solved by database indexing, the correct use of table engines, memcache \ radish. In this, all popular frameworks should be on the same level. In another - you will not decide until there are clear requirements.
And so, yes, you always want to take Node.js. And a little jQuery

Answer 2

You don't think about it. It is necessary to solve the task, and not to argue "that's when 100500 users will come ..."
Modern php applications use composer and it has a built-in solution to this problem .
kohana is hardly a good choice, take rapidly developing frameworks with a large community: symfony, laravel, yii 2.

Answer 3

Symfony2 because it's cheaper to buy a couple more servers than to pay for an overhead to support self-written garbage (pay with money or, if you write everything yourself, with your time). The architecture of the application decides a lot, though. Bottlenecks can be written in Go (I would not use Node.js for critical places), you can not use ORM, but do Doctrine DBAL. Alternatively, you can just throw out PHP and write in bare Hack.
You can also try Phalcon, but to be honest, I didn’t touch it even for the reasons described above. You can still poke ReactPHP as a base, but this already increases the risks. If you need performance and don't want to write shitty code, you can take Silex and write your own project based on it, with your own architecture...
In general, you can make good use of server resources by properly setting up the database and connecting caches.