Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9525
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <4089E106.4040409@akbkhome.com>
Date: Sat, 24 Apr 2004 11:37:42 +0800
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031002
MIME-Version: 1.0
To:  internals@lists.php.net
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Performance Consideration of 1 class per file
From: alan@akbkhome.com (Alan Knowles)

PEAR is considering stipulating 1 class per file, for the packages. - 
one of the concerns raised is performance. While this is true for a 
non-cache compiled situation (where performance is less of an issue) - 
would anyone care to comment on the implications when using the Zend 
Optimizer or APC, on how significant the impact of this would be.

- looking at typical application where the number of files included in 
the code with may jump from 20->30 included files..

 From my understanding, if you where looking for performance, you would 
probably have a cache expiry which would mean very few stat (if any) 
calls based on these addition includes.. - hence negating the issue..

Thanks
Alan



-- 
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com