Sascha Schumann wrote:
On Thu, 2 Feb 2006, Rasmus Lerdorf wrote:
Sascha Schumann wrote:
Or simply use eAccelerator which does not cause those open
calls.
Which doesn't support PHP 5.1 very well.
Which is pretty fine for us PHP 4.4 users.
The site where I reinstalled eAccele
On Thu, 2 Feb 2006, Rasmus Lerdorf wrote:
> Sascha Schumann wrote:
> > Or simply use eAccelerator which does not cause those open
> > calls.
>
> Which doesn't support PHP 5.1 very well.
Which is pretty fine for us PHP 4.4 users.
The site where I reinstalled eAccelerator does not
Sascha Schumann wrote:
Or simply use eAccelerator which does not cause those open
calls.
Which doesn't support PHP 5.1 very well.
Rasmus, is that behaviour by design? I deinstalled APC
because of this 'characteristic' last week. It was killing a
high-traffic site.
Lo
I tested this and you are correct. This should make a big difference.
I learn something new every day :)
Thanks a million.
-James
Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
>
> I think the main hint you need is to never use require_once/include_once
> with an opcode cache. Those are the
Sascha Schumann wrote:
Or simply use eAccelerator which does not cause those open
calls.
Rasmus, is that behaviour by design? I deinstalled APC
because of this 'characteristic' last week. It was killing a
high-traffic site.
- Sascha
On Thu, 2 Feb 2006, Rasmus Lerdo
Or simply use eAccelerator which does not cause those open
calls.
Rasmus, is that behaviour by design? I deinstalled APC
because of this 'characteristic' last week. It was killing a
high-traffic site.
- Sascha
On Thu, 2 Feb 2006, Rasmus Lerdorf wrote:
> I think the m
I think the main hint you need is to never use require_once/include_once
with an opcode cache. Those are the only ones that will cause an open()
call. You should only be seeing a single stat() call per file under APC
(needed to get the inode+device hash key for the shared memory lookup).
-Ra
Hello:
We have a very high-volume site that runs across a cluster of several
machines which needs to have access to our back end storage platform, which
needless to say is very busy. I have been given the task of reducing load to
the filer. Due to the fact that our application is rather large a
