Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39614
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: Marcus Boerger <helly@php.net>,
 Stefan Priebsch <stefan.priebsch@e-novative.de>,
 Hannes Magnusson <hannes.magnusson@gmail.com>,
 Dmitry Stogov <dmitry@zend.com>,
 internals@lists.php.net
Message-ID: <FDAFAA57-4B75-44A5-9E21-350863661BBB@pooteeweet.org>
To: Andrey Hristov <php@hristov.com>
In-Reply-To: <4896CEF9.1090500@hristov.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Mon, 4 Aug 2008 11:48:08 +0200
References: <909776579.20080803142659@marcus-boerger.de>  <4896A7C4.8090503@zend.com> <7f3ed2c30808040055r377369d0l86f7c39cea7d94b2@mail.gmail.com> <4896BDB3.7000003@e-novative.de> <99710BD7-2224-4AA2-B2DD-1B6A4A5C0DA8@pooteeweet.org> <4110342533.20080804104113@marcus-boerger.de> <71D8CF46-882A-4120-A4D7-B62646703120@pooteeweet.org> <4896CEF9.1090500@hristov.com>
Subject: Re: [PHP-DEV] Inconsistencies in 5.3
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 04.08.2008, at 11:42, Andrey Hristov wrote:

> Hi,
> Lukas Kahwe Smith wrote:
>> On 04.08.2008, at 10:41, Marcus Boerger wrote:
>>> Hello Lukas,
>>>
>>> Monday, August 4, 2008, 10:32:26 AM, you wrote:
>>>
>>>
>>>> On 04.08.2008, at 10:28, Stefan Priebsch wrote:
>>>
>>>>> Hannes Magnusson schrieb:
>>>>>> I don't think anyone but him likes multiple namespaces per  
>>>>>> file. I do
>>>>>> remember a PhD thesis sized mail from him explaining why multiple
>>>>>> namespaces per file was needed though (can hardly believe  
>>>>>> anyone read
>>>>>> the whole thing..).
>>>>>
>>>>> In some deployment processes, multiple PHP files are merged  
>>>>> together
>>>>> into one file. Symfony, for example, does this, at least  
>>>>> optionally.
>>>
>>>
>>>> Right, this is common practice to reduce disk I/O without having to
>>>> make development too hard. Also that way people can pick and choose
>>>> what they want to include (like not all drivers of a DBAL).
>>>
>>> If an edgecase optimization is th eonly reason then I am against  
>>> this
>>> even more.
>> its not an edge optimization .. like i said its "common practice"  
>> in many PHP frameworks. this way they can more easily develop the  
>> code, while not having to suffer the drawbacks from a lot of disk I/ 
>> O from files that need to be loaded in every request anyways.
>
> isn't that easily solved by using a opcode cache?


The op code cache can reduce the overhead, but not all. Obviously  
there still needs to be work done to determine if the file has  
changed. of course you can just tell APC to never do that, but i think  
this is a setting very few people consider and its definitely not made  
for general purpose frameworks, that want to be easy to use while  
still being as fast as possible.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org