|
|
Posted by Jerry Stuckle on 01/18/08 01:30
Gilles Ganault wrote:
> On Thu, 17 Jan 2008 20:21:03 +0100, "Rik Wasmus"
> <luiheidsgoeroe@hotmail.com> wrote:
>> Efficiency wise (using or resources) in my experience hardly, but that may
>> have to do with the nature of my projects.
>
> Thanks for the input. The reason was really about performance, not
> about how to deal with a whole team working on the same PHP
> application.
>
> I'll rephrase it this way: What are the requirements for a PHP page to
> be cached?
>
> Do I need to move all the MySQL calls to other pages, and just pass
> the contents as eg. $stuff_to_display to PHP pages acting as views?
>
I agree with Rik. I don't find them overly useful for my projects,
either. But others seem to think they're the greatest thing since
sliced bread. YMMV.
The PHP code itself isn't cached unless you install an accelerator. The
source may still be in a system cache, for instance. But not the
completed page.
The HTML output my be cached by the client or any server between your
site and the clients, based on things you can recommend but not control.
The real question here is though - are you observing performance
problems? Or are you prematurely optimizing?
And if you are having performance problems, what is the source of your
problems? Unless you're getting 1K hits per second on your PHP pages, I
very much doubt it is the PHP interpreter.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|