RE: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-06 Thread Daevid Vincent
> -Original Message- > From: Al [mailto:n...@ridersite.org] > Sent: Wednesday, January 06, 2010 5:09 PM > To: php-general@lists.php.net > Subject: [PHP] Re: PHP programming strategy; lots of little > include files, or a few big ones? > > > > On 1/6/2010 7:18 PM, clanc...@cybec.com.a

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-06 Thread Daniel Kolbo
Daevid Vincent wrote: > > >> -Original Message- >> From: Al [mailto:n...@ridersite.org] >> Sent: Wednesday, January 06, 2010 5:09 PM >> To: php-general@lists.php.net >> Subject: [PHP] Re: PHP programming strategy; lots of little >> include files, or a few big ones? >> >> >> >> On 1/6/2

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-06 Thread Robert Cummings
Daniel Kolbo wrote: Daevid Vincent wrote: -Original Message- From: Al [mailto:n...@ridersite.org] Sent: Wednesday, January 06, 2010 5:09 PM To: php-general@lists.php.net Subject: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones? On 1/6/2010

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-07 Thread Daniel Egeberg
On Thu, Jan 7, 2010 at 04:11, Daevid Vincent wrote: > I think it's a case by case basis. Generally File I/O is expensive, but > then again, as you say, having everything in a couple files is also > sub-optimal for organizing and keeping things modular. That is easily sorted out using automated bu

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-07 Thread clancy_1
On Wed, 6 Jan 2010 19:11:07 -0800, dae...@daevid.com ("Daevid Vincent") wrote: > > >> -Original Message- >> From: Al [mailto:n...@ridersite.org] >> Sent: Wednesday, January 06, 2010 5:09 PM >> To: php-general@lists.php.net >> Subject: [PHP] Re: PHP programming strategy; lots of little >

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-07 Thread clancy_1
On Wed, 06 Jan 2010 23:20:26 -0500, kolb0...@umn.edu (Daniel Kolbo) wrote: >Daevid Vincent wrote: >> >> >>> -Original Message- >>> From: Al [mailto:n...@ridersite.org] >>> Sent: Wednesday, January 06, 2010 5:09 PM >>> To: php-general@lists.php.net >>> Subject: [PHP] Re: PHP programming

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-07 Thread Robert Cummings
clanc...@cybec.com.au wrote: Thank you all for your comments. I did not know about bytecode caches. They're an interesting concept, but if I am interpreting the paper http://itst.net/654-php-on-fire-three-opcode-caches-compared correctly they only double the average speed of operation, which is

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-07 Thread clancy_1
On Thu, 07 Jan 2010 22:48:59 -0500, rob...@interjinn.com (Robert Cummings) wrote: >clanc...@cybec.com.au wrote: >> Thank you all for your comments. I did not know about bytecode caches. >> They're an >> interesting concept, but if I am interpreting the paper >> http://itst.net/654-php-on-fire-th

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-08 Thread Graham Cossey
On Fri, Jan 8, 2010 at 3:48 AM, Robert Cummings wrote: > > They almost always make your shit run faster. I love your final statement Robert! A reply of good grammar and vocabulary summarised most succinctly. -- Graham -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit:

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-08 Thread Andrew Ballard
On Thu, Jan 7, 2010 at 10:48 PM, Robert Cummings wrote: > ... > They almost always make your shit run faster. You know they make medicine for that? ;-) Andrew -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-08 Thread Robert Cummings
Graham Cossey wrote: On Fri, Jan 8, 2010 at 3:48 AM, Robert Cummings wrote: They almost always make your shit run faster. I love your final statement Robert! A reply of good grammar and vocabulary summarised most succinctly. :) -- http://www.interjinn.com Application and Templating Frame

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-08 Thread Robert Cummings
clanc...@cybec.com.au wrote: On Thu, 07 Jan 2010 22:48:59 -0500, rob...@interjinn.com (Robert Cummings) wrote: clanc...@cybec.com.au wrote: Thank you all for your comments. I did not know about bytecode caches. They're an interesting concept, but if I am interpreting the paper http://itst.ne

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-08 Thread J Ravi Menon
Hi, A note on bytecode caching and include/include_once performance. A while ago when we were profiling our code, we did notice that file includes do take a noticeable percentage of overall overhead (enough for us to look into it more deep). We are using apc cache on a standard LAMP platform (linu

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-08 Thread J Ravi Menon
Sorry forgot to mention that we used APC with apc.stat turned off which will give a little bit more performance gain, but it does mean flushing the cache on every code push (which is trivial). Ravi On Fri, Jan 8, 2010 at 11:30 AM, J Ravi Menon wrote: > Hi, > > A note on bytecode caching and inc

Re: [PHP] Re: PHP programming strategy; lots of little include files, or a few big ones?

2010-01-08 Thread Phpster
On Jan 8, 2010, at 10:44 AM, Andrew Ballard wrote: On Thu, Jan 7, 2010 at 10:48 PM, Robert Cummings wrote: ... They almost always make your shit run faster. You know they make medicine for that? ;-) Andrew -- Tacos? Bastien Sent from my iPod -- PHP General Mailing List (http: