Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92754
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.48 as permitted sender)
MIME-Version: 1.0
References: <CALW=WECkP4D7QHbAt9LCE0DT=40qyYk5iEspUSpjG4MUKTi6Rg@mail.gmail.com>
 <571E2B75.6000909@gmail.com> <CALW=WEDHi86Z2_x5ggjKOWDjcdaoGfwTktHEx0ATrk-Zut7tZQ@mail.gmail.com>
 <571E5A62.9030502@gmail.com> <CALW=WEB7ctpzmrfURFQMAnJPLHSFuTcDuN2-zBLs8EeK7wSxwA@mail.gmail.com>
In-Reply-To: <CALW=WEB7ctpzmrfURFQMAnJPLHSFuTcDuN2-zBLs8EeK7wSxwA@mail.gmail.com>
Date: Mon, 25 Apr 2016 20:11:24 +0000
Message-ID: <CAL0xaBGwNGqo00HZt7wKCKgy9c6qjAvVQF+CZ7wgDNCrr2imBg@mail.gmail.com>
To: "S.A.N" <ua.san.alex@gmail.com>, Rowan Collins <rowan.collins@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1142b97a800da4053154c83a
Subject: Re: [PHP-DEV] Opcache::get($key), set($key, $value) to shared memory,
 is planned in PHP 7.1?
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--001a1142b97a800da4053154c83a
Content-Type: text/plain; charset=UTF-8

On Mon, 25 Apr 2016, 21:07 S.A.N, <ua.san.alex@gmail.com> wrote:

> 2016-04-25 20:56 GMT+03:00 Rowan Collins <rowan.collins@gmail.com>:
> > S.A.N wrote on 25/04/2016 18:49:
> >>>
> >>> There's not really a huge connection between opcode caching and
> >>> optimization
> >>> >(OpCache) and shared memory data caches (APCu, memcached, etc), so I
> >>> > don't
> >>> >think there's any particular logic to calling such functions
> "opcache".
> >>> >
> >>> >So I guess the question becomes: "should APCu be made part of core?"
> I'm
> >>> > not
> >>> >aware of anyone having proposed that, so don't know if there are
> strong
> >>> >feelings for or against such a thing.
> >>
> >> Yes, there are a lot of libraries to work with shared memory, but why
> >> should they if there OPcache in core PHP?
> >> Functions get, set key values will be useful and in demand.
> >
> >
> > Because different situations call for different functionality. If the
> only
> > reason not to use APCu was the need to install a PECL extension, then
> nobody
> > would have implemented a PECL extension for Memcache, or Redis, etc.
> >
> > Storing data in PHP's shared memory has several downsides - for instance,
> > inability to share with CLI / services built in other languages,
> > non-persistent across server restarts, not shareable across instances,
> etc.
> > For you, these may not be an issue, but to say that "if APCu
> functionality
> > was in core, nobody would need any other memory cache" is somewhat naive.
>
> I am not against third-party libraries, I want to have this
> functionality out of the box, it seems to me correct to make these
> functions in OPCache, instead of adding  Apcu to PHP core, IMHO...
>

A little history lesson - combining an opcode cache and data storage is one
of the reasons APC died - it got too complex and too convoluted in the end.
Yes, there were other reasons too, but this one was one of the big one.

Getting that functionality into the core is not bad idea, but never ever
ever mix it with the opcode cache. Keep them separate.

>

--001a1142b97a800da4053154c83a--