Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9528
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <408A138C.2010801@cschneid.com>
Date: Sat, 24 Apr 2004 09:13:16 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040114
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@php.net>
Cc: internals@lists.php.net
References: <4089E106.4040409@akbkhome.com> <Pine.WNT.4.56.0404232147480.1396@DELL>
In-Reply-To: <Pine.WNT.4.56.0404232147480.1396@DELL>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Performance Consideration of 1 class per file
From: cschneid@cschneid.com (Christian Schneider)

Rasmus Lerdorf wrote:
> 1. The included_files list gets updated each time you include a file.  In
>    order to make sure that the same file included by different paths or
>    symlinks don't conflict we do a realpath() on the file to be included.

That's done by PHP, not APC, right? Does this only apply to require_once 
or require as well?

> 2. APC uses the file's device and inode as the lookup key into shared
>    memory to find the opcodes for the file, so a stat has to be done on

Hmm.. If the stat on the file and the check for device/inode would be 
done first then you wouldn't have to do a realpath, right? But I guess 
that's not easily done until after the realpath check.

> So yes, jumping from 20 to 30 include files could very well bring a rather
> significant performance hit.

I guess that's only important if your PHP code is really simple and you 
don't do something like e.g. DB queries because otherwise that'd be 90% 
of the running time anyway, right?

I guess someone _that_ considered about performance could easily do a
cat *.php | grep -v require | php -w >app.lib
or the like and include app.lib.

- Chris