Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103499
To: Marco Pivetta <ocramius@gmail.com>, Zeev Suraski <vsuraski@gmail.com>
CC: PHP Internals List <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [mini-RFC] Disable opcache per script using
 "declare(cache=0)"
Thread-Index:
 AQHUgxKMYogqZPZudUmsS4r/pLxAKaVdIu2AgAAsRayAALAvgIAACOsAgADiJoCAAG9OgIAAmGKAgAEVAgCAAAJ0gIAAp1Je
Date: Mon, 26 Nov 2018 07:51:25 +0000
Message-ID:
 <BY1PR02MB1260BE27F8CA388956EB37AABFD70@BY1PR02MB1260.namprd02.prod.outlook.com>
References:
 <BY1PR02MB12606B0B2C6878B6F73D151BBFD40@BY1PR02MB1260.namprd02.prod.outlook.com>
 <CAF+90c_6Vwz+GguSfCGQw5ncmcSBGXnXP4yo1KymLDMEaL19Hw@mail.gmail.com>
 <BY1PR02MB1260D6A74881B45987CC462EBFD40@BY1PR02MB1260.namprd02.prod.outlook.com>
 <F1BA9936-6BCD-47C8-90B8-B011B472A610@gmail.com>
 <CAJHtznxOm=YR8FcUDx_M-Fv9WgP-PtT+vg4G5_sMom2EJK5iEA@mail.gmail.com>
 <1cb7fecd-22ba-0ded-5bd6-e70208053012@gmail.com>
 <7f65012b-e26a-fb58-718b-b35569e53d03@gmail.com>
 <CADyq6sLWz3rZaPCu-AZtCoKCQGC4SiJra66w+6cdeFvk58FJ_A@mail.gmail.com>
 <CAJHtznxQOnZZEhnXP-KY+iMSQ-0BBwWFhHaofU2+R+=ZxXx0VQ@mail.gmail.com>,<CADyq6sKGg6vnzqTsBprz8NuuPjnw_fZuC-it=K_ExoBnoXRcbw@mail.gmail.com>
In-Reply-To:
 <CADyq6sKGg6vnzqTsBprz8NuuPjnw_fZuC-it=K_ExoBnoXRcbw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: zend.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_BY1PR02MB1260BE27F8CA388956EB37AABFD70BY1PR02MB1260namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6842654b-7afc-4b3f-d155-08d65373f7aa
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Nov 2018 07:51:25.8242
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 32210298-c08b-4829-8097-6b12c025a892
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR02MB1242
Subject: Re: [PHP-DEV] [mini-RFC] Disable opcache per script using
 "declare(cache=0)"
From: dmitry@zend.com (Dmitry Stogov)

--_000_BY1PR02MB1260BE27F8CA388956EB37AABFD70BY1PR02MB1260namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

OK. I didn't think, this feature required explanation. I saw this like a si=
mple way to separate "data" and "code".

Anyway, now I see, this can't be accepted without RFC etc


Thanks. Dmitry.

________________________________
From: Marco Pivetta <ocramius@gmail.com>
Sent: Monday, November 26, 2018 12:43:15 AM
To: Zeev Suraski
Cc: PHP Internals List
Subject: Re: [PHP-DEV] [mini-RFC] Disable opcache per script using "declare=
(cache=3D0)"

Is that space rrrrrrreeeeeally a problem?

Take the example ZF loader from the RFC: that barely makes any difference
at all.

A stronger reasoning for another language construct (that changes engine
behaviour) is kinfa required.

On 25 Nov 2018 22:34, "Zeev Suraski" <vsuraski@gmail.com> wrote:



On Sun, Nov 25, 2018 at 7:03 AM Marco Pivetta <ocramius@gmail.com> wrote:

> Adding to the pile of "it's an edge case", since the preload scripts will
> be procedural, wouldn't it be sufficient to call
> `opcache_invalidate(__FILE__)` at the end of them?
>
> That would actually not do anything useful - as the file will (in all
likelihood) never be accessed again anyway.  Invalidating a file only
ensures it won't be fetched again from the opcache - it doesn't actually
free up the space it consumes.  Invalidate it or not, in both cases the
outcome is the same - a bit of memory consumed by a file that will never
again be fetched from the opcache.  I believe this is what Dmitry's
proposal was about - not putting the file into the opcache to begin with,
to save the bit of memory that it would otherwise consume (but I could be
wrong, as the savings are likely to be so small I'm not sure why we would
care about them...).

Zeev

--_000_BY1PR02MB1260BE27F8CA388956EB37AABFD70BY1PR02MB1260namp_--