|
|
Posted by Jeremy on 01/08/08 19:27
Jerry Stuckle wrote:
> In fact, I find it's more often assumed to be on the same server
> when not specified.
> the overhead of making a connection - especially on a local machine
> - is small..
> the problem is not related to database - but general resource
> shortage.
Interesting and valid points all around. I'm glad you were able to help
the OP. Many of my assumptions about his situation were incorrect.
Memcached was not a helpful suggestion here, but I still think that apc
is helpful in most situations. Even if memory is short - a smart opcode
cache won't particularly hurt memory use. In fact, it may even help -
instead of compiling the code (into memory, I might add) separately for
multiple concurrent requests, suddenly there is already a compiled copy
in shared memory that can be utilized. True, there may be less memory
used when the server is completely idle - but that is not particularly
helpful, right? Before denigrating it, I suggest you try it out on one
of your applications; it might surprise you.
I stand by my conviction that explicit caching is a good idea more often
than not, but then I rarely work with a single-server (or significantly
memory-bound) environment so maybe it's my lack of experience there
that's distorting my perception in your view.
In any case, I appreciate the discussion.
Jeremy
Navigation:
[Reply to this message]
|