Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66350 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66572 invoked from network); 28 Feb 2013 19:25:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Feb 2013 19:25:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=ilia@prohost.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ilia@prohost.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain prohost.org designates 209.85.210.170 as permitted sender) X-PHP-List-Original-Sender: ilia@prohost.org X-Host-Fingerprint: 209.85.210.170 mail-ia0-f170.google.com Received: from [209.85.210.170] ([209.85.210.170:40557] helo=mail-ia0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 63/28-25879-03FAF215 for ; Thu, 28 Feb 2013 14:25:36 -0500 Received: by mail-ia0-f170.google.com with SMTP id k20so1890762iak.1 for ; Thu, 28 Feb 2013 11:25:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=feuV5IEKwJyubN9O/HtU5dhgFrd/1ILfFi1MBYn9ji4=; b=pk2KY1ecPdVu314hpEY2Z+NYGGk0z4U9yZk/Fq2NWd0O6+12LoyslW/yonlCj3Mi/Q lpRNrxeUwMOB1W6YnEtfDxJOYGSHQUDu6Rw0AYDntWTaiRIU9AEvCtNokmcKIIOlZUGc C8o1wqmooLwtPNF+cB0iP+m0RU+2BA7FVzgEXxiegRrUceHDz9XBeZr9VnSNOUlpo3IL JOCCFJzVHR8YeLR6POGae/txTJ84xcNRlkKEGOQIU2k7wKrPjFQoJkINepgn8zqLZsF3 jW6+jM18UicR65baYVnZLL/jr8OVE6T+NB4Sac55FnuLq7dXY7ZpEizzwJu+5rpHv+Xq pOpQ== MIME-Version: 1.0 X-Received: by 10.50.212.3 with SMTP id ng3mr4674571igc.43.1362079533814; Thu, 28 Feb 2013 11:25:33 -0800 (PST) Received: by 10.64.14.116 with HTTP; Thu, 28 Feb 2013 11:25:33 -0800 (PST) In-Reply-To: <512FAD2B.1040903@sugarcrm.com> References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com> <512E7870.7010208@lerdorf.com> <0b8c20490dae9ecb9f9cd4a77cf47796@mail.gmail.com> <512FAD2B.1040903@sugarcrm.com> Date: Thu, 28 Feb 2013 14:25:33 -0500 Message-ID: To: Stas Malyshev Cc: Anthony Ferrara , Zeev Suraski , Pierre Joye , Ferenc Kovacs , Rasmus Lerdorf , PHP Developers Mailing List Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnXOJd0tpc8B26a8p4sEFlH3+2B35hI6KSteEaPjzzxGyJ3NgZI3UQUiAiVUcNoojPL8t2U Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution From: ilia@prohost.org (Ilia Alshanetsky) The APC issues are somewhat APC specific in most cases, they often revolve around memory utilization issues and garbage collection. Some of the work-arounds involve ensuring APC always has extra memory to prevent fragmentation. When fragmentation goes about 35-40% clearing out the entire cache to prevent increase in fragmentation which in many cases can reduce stability. Loading large number of files in parallel is another thing that frequently can negatively impact APC, doing pre-loading or staggering the loading process is the work-around that typically prevents issues. On Thu, Feb 28, 2013 at 2:16 PM, Stas Malyshev wrote: > Hi! > >> If you are referring to APC as the stable cache, that unfortunately is >> not entirely correct, it is still relatively easy to crash APC unless >> some work-arounds are applied. I was speaking to a several people at >> the conference just yesterday and they were indicating frequent >> crashes with APC, the work-arounds appear to have solved their issues, >> but those are not exactly obvious. > > Do we have those ways and work-arounds recorded somewhere? It would be a > very good idea to have tests for O+ to ensure there are no problems in > these areas (or if there are, to fix them :). My experience suggests > opcode cache solutions often tend to have issues in the same areas, so I > think it'd be very useful. > > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227