search

tel8618217223380 / prado3

Automatically exported from code.google.com/p/prado3
Other
0 stars 0 forks source link

Feature request: Configurable and/or more comprehensive pradolite.php #225

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
My understanding is that pradolite.php increases performance by first 
having a lot of smaller files united in a single big one (thus lowering 
the number of file operations, lookup tables, etc related to handling 
script), and also by preventing to have the autoload functions to kick in, 
and load scripts on-demand when referencing the included classes.

I'd assume that performance could be increased even further by having even 
more classes included in a single big file (like pradocomplete.php or 
something). The optimial set of controls to include might be dependent on 
the actual project (ie. on what kind of controls and features it's using 
for ex. on all pages), so maybe the "compiler" script - which would 
combine all the framework files into a single one - would have to be 
configurable, so everybody could make their own versions of this 
performance-oriented file, depending on the component-use behavior of 
their sites.

However, I'd not be much suprised if a proper benchmarking would point out 
that it wouldn't make much a difference to practically combine all 
framework files in a single file, indifferently of which and how many of 
them the actual project is using. This is because even though dead code 
would normally have a detoriating effect on performance, as it would 
require unneccessary parsing, but I guess with an opcode-cache (like 
eAccelerator) loaded all of the performance hit because of this could be 
eliminated (as thank to the cache the need for parsing itself would be 
eliminated, only leaving PHP with the task of scanning and building symbol 
tables, which I presume quite fast even when all files are combined) - 
thus leaving us only with the benefits of the combined file, ie. the 
circumvention of autoload and even the reduced number of filestat queries 
(on the script files) from the side of the opcode cache itself.

Any ideas, comments on this?

Original issue reported on code.google.com by google...@pcforum.hu on 21 Feb 2010 at 12:36

GoogleCodeExporter commented 9 years ago

Original comment by Christophe.Boulain@gmail.com on 21 Feb 2010 at 5:12

GoogleCodeExporter commented 9 years ago

Original comment by ctrlal...@gmail.com on 25 Jun 2012 at 1:56

GoogleCodeExporter commented 9 years ago

Original comment by ctrlal...@gmail.com on 21 Jan 2013 at 7:03

GoogleCodeExporter commented 9 years ago

Original comment by ctrlal...@gmail.com on 24 Jul 2013 at 1:46

GoogleCodeExporter commented 9 years ago 
Moved to github: https://github.com/pradosoft/prado/issues

Original comment by ctrlal...@gmail.com on 1 Oct 2013 at 10:14