> First of all you need to get it clear in your head what an opcode cache
> is actually doing. It does not "cache the website", it caches the
> compiled version of the PHP scripts such that PHP doesn't need to
> recompile each file every time it's included which is the default way
> PHP wo
On 23 Oct 2008, at 00:04, Martin Zvarík wrote:
I am looking at the eAccelerator's website and I realize what got me
confused:
there is a function for OUTPUT CACHE, so it actually could cache the
whole website and then run out of memory I guess...
that means I would be able to store anythin
I am looking at the eAccelerator's website and I realize what got me
confused:
there is a function for OUTPUT CACHE, so it actually could cache the
whole website and then run out of memory I guess...
that means I would be able to store anything into the memory and
reference it by a variable?
Thanks for reply Stut.
So, the APC, XCache etc. doesn't work as FileCache and also doesn't
decrease the number of database queries, since it is not caching the
content...
I see now, it is obvious that it would be very hard to run out of memory.
--
Martin
Stut napsal(a):
On 22 Oct 2008, a
On 22 Oct 2008, at 22:19, Martin Zvarík wrote:
I became confused after an hour trying to understand the PHP cache
solutions.
XCache, APC, eAccelerator and others are opcode cache systems... is
memcache in the same category? or is it completely different?
Memcache is completely different in
Hi,
I became confused after an hour trying to understand the PHP cache
solutions.
XCache, APC, eAccelerator and others are opcode cache systems... is
memcache in the same category? or is it completely different?
If I install for example XCache, set it for certain directory... it will
automa
6 matches
Mail list logo
