[eluser]vlad_ci[/eluser]
@xeoncross
Ok, I think I understand the scenario you refered to:
without PHP framework: all code is in one or two PHP scripts
(which is what is used in the article you refered to)
with a PHP framework all the functions are split into many PHP files
if both use the same database access, which accounts probably for
less than 20% of the overall time (just my guess) in that example
non-framework code will appear to be much faster.
In my mind the scenario I was describing above
is of an application that deals with
Inserts/Updates/Selects on a few tables between 300 to 600 million rows
each, where each 'task' is a single database transaction
that manipulates (reads and updates) about between
30 to 30,000 rows at a time (some times selects must use joins with the large
tables, so some joins must be performed 'in-application' memory or some other
tecnique)
So in that scenario -- in my mind -- a distributed system will be heavily
database bottlenecked, and PHP, especially when pages can be precompiled
with various accellerator tecniques, would not be noticeable.
Perhaps, before making my conclusions in the post above, I should have
known more, where the application of the original poster will spends most of its time.
If it is in PHP function calls that are results of abstraction, then
of course the non-framework code will be much faster.
