Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66658
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain zend.com does not designate 209.85.128.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5143D0B7.80204@lerdorf.com>
References: <5143D0B7.80204@lerdorf.com>
Date: Sat, 16 Mar 2013 10:13:10 +0400
Message-ID: <CA+9eiLso8Uok33GAOKwmeV0MdLGMnO_kZGxm+qXx3N6PQUmtNA@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: PHP internals <internals@lists.php.net>, Andi Gutmans <andi@zend.com>, Zeev Suraski <zeev@zend.com>
Content-Type: multipart/alternative; boundary=20cf3071c7fc6d320604d804a60b
Subject: Re: Opcache tuning
From: dmitry@zend.com (Dmitry Stogov)

--20cf3071c7fc6d320604d804a60b
Content-Type: text/plain; charset=UTF-8

Hi Rasmus,

restart_count - makes sense

last_restart_reason - is not very useful, I think it's better to add
separate counters for each reason (memory overflow, hash overflow, wasted
memory).

What do you think?

Dmitry.

On Saturday, March 16, 2013, Rasmus Lerdorf wrote:

> Hey Dmitry, I think it would be helpful if we added two tuning status
> entries. The first is a "restart_count" which lets you know how many
> times the cache has restarted since server start. And the second, since
> there are multiple triggers for a cache restart, would be a
> "last_restart_reason" which specifies which limit triggered the last
> restart. Both should be easy to do as far as I can tell and it would
> help people figure out if they need to allocate more memory to the cache
> or allocate more keys.
>
> -Rasmus
>

--20cf3071c7fc6d320604d804a60b--