APC and new update process
Permalink
Something I discovered - if you update concrete through the dashboard, where it basically downloads an entirely new core in the /updates folder, APC will cache both the original /concrete/ and /updates/concrete folders, doubling the amount of memory needed. This can be prevented by just overwriting the original /concrete/ folder rather than using the dashboard update process.
I am downloading from my testing directory to the public_html. I have to download it all first to get the images and everything I need, but since I've updated the core through the dashboard, I now have three instances of the concrete core folder.
It's taking FOREVER to download it all. On hour two now.