Details about this thread
  • State Verified Answer
  • Replies 15 replies
  • Subscribers 295 subscribers
  • Views 2582 views
  • Users 0 members are here
Related content from around SugarClub

Memory leak issue, possibly because PHP APC add on.

Doddy Amijaya
I noticed that when I enabled APC it spawn so many apache process and it can consume memory really quickly. Our client server crashed twice because it ran out of memory.

Setup:
Linux CentOS 7
MariaDB
Apache 2.2
php 5.4.16 with APC
enabled JSMIN.
CPU : 4 cores
RAM : 12 GB

When I disabled the APC add on I didn't have that many apache processes being spawned and the RAM is hardly go beyond 3GB. I was doing a mass update that update the Account record and ALL of its related records, this is a massive operations but it didn't go beyond 3GB in terms of memory use when I have the APC disabled.

When I turned it on it was easily jumped from 2 GB to 6 GB.
is there a known issues with APC add on that you guys are aware off?
Parents Reply
  • 0 in reply to Justin Kuehlthau
    Thanks a lot Harold

    For average Sugar installation the APC config we were using is
    apc.shm_size = 512M
    apc.shm_segments = 1
    apc.optimization = 0
    apc.slam_defense = On
    apc.num_filed_hint = 2048
    apc.ttl = 0
    apc.enable_cli = 1
    apc.max_file_size = 1M

                   

    I think we will try for a start ( subject to load testing and monitoring) following opcache settings:

     

    opcache.memory_consumption = 256 or 512 
    opcache.max_file_size = 1M
    opcache.interned_strings_buffer = 8
    opcache.max_accelerated_files = 4000
    opcache.fast_shutdown = 1
    opcache.enable_cli = 1
    opcache.revalidate_freq = 0
    opcache.use_cwd = 1


Children
No Data