Oh yeah - as I recall shared memory shows up for every process that is
attached to it in top. That can be a bit confusing. It's not really
duplicated.
On Sep 28, 2:56 pm, Daniel Kucharski dan...@inspiran.be wrote:
Hi Tom,
Thanks for the tip, I implemented APC and noticed that the login page
First off the cache is there to reduce memory consumption as when your cache
is clear symfony will need to rebuild all the cache files and so that first
run after a cleared cache is very high.
One way to reduce your memory footprint is in the Propel criteria you use
and the data returned.
Hi,
Thank you very much for your quick response. I'll keep this in mind while
querying and hydrating objects.
However, the problem is actually that i already have a very high memory
consumption even before anything from the database is queried. If you
check the trace, you'll notice that
If you check the trace, you'll notice that already 16MB is consumed
before any
querying occurs...
This is PHP's overhead to compile the Symfony code. You probably don't
have APC enabled. Enable APC and watch this overhead disappear
completely (apart from the first request after you restart
Hi Tom,
Thanks for the tip, I implemented APC and noticed that the login page now
dropped from 22 MB to just 7 MB. Still lots in my opinion but it is
already a good step in the right direction.
However I do notice as I am on a private Virtual private Server with just
512 MB that this APC is
There is just one APC cache. That's a big part of the point. Unless
there is something wrong with your APC setup, or you don't have it set
up to use shared memory.
How are you measuring the memory impact of APC on Apache, exactly?
On Sep 28, 2:56 pm, Daniel Kucharski dan...@inspiran.be wrote:
