Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92773
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.65 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <59412f65-4d7d-bcd3-6c9b-400dbbb07cdc@fedoraproject.org>
References: <CALW=WECkP4D7QHbAt9LCE0DT=40qyYk5iEspUSpjG4MUKTi6Rg@mail.gmail.com>
 <59412f65-4d7d-bcd3-6c9b-400dbbb07cdc@fedoraproject.org>
Date: Tue, 26 Apr 2016 18:38:01 +0900
Message-ID: <CAGa2bXaX_LDsDwxs3dPB9nOevCCTXMcN7hiiUuy4+PKfUkR3MQ@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Opcache::get($key), set($key, $value) to shared memory,
 is planned in PHP 7.1?
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

Hi all,

On Tue, Apr 26, 2016 at 4:44 PM, Remi Collet <remi@fedoraproject.org> wrote=
:
> Le 25/04/2016 =C3=A0 16:09, S.A.N a =C3=A9crit :
>> In userland  lacks the ability to store data in the shared memory
>> modules, do not use pecl modules, it would be very nice to have a
>> function:
>>
>> opcache_get($key);
>> opcache_set($key, $value);
>
> Opcache is an opcode cache.
>
> A user data cache is something really different.
>
> We learn from the past, having both in the same extension (APC) was an
> mistake.
>
> So I really think, this doesn't have to be added in opache.
>
> And various extensions already exist (apcu, yac, memcache(d), redis...)
> each for different needs.

They are different thing. That said

Are we going to have race condition free shared memory API by default?

If yes, I'll use it for mm save handler (session save handler that
uses shared memory) storage. Mm save handler does not compile with ZTS
currently. Mm save handler would be nice for small web sites. It could
be default save handler and many apps/sites will have performance
boost.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net