Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92250
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAKSD0w6ji0JgnnU0BSCv64_bu+RNnLTRyz7XPyCv2gcK-+6BBg@mail.gmail.com>
References: <CAKSD0w6ji0JgnnU0BSCv64_bu+RNnLTRyz7XPyCv2gcK-+6BBg@mail.gmail.com>
Date: Wed, 13 Apr 2016 18:32:33 +0200
Message-ID: <CADyq6sJLQ1h1g=1RT_8HKfXtbGHpUdpG9_uxn4kRhFP-rz8-Zg@mail.gmail.com>
To: Lin Yo-An <cornelius.howl@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a114022c655ff32053060542c
Subject: Re: [PHP-DEV] Proposal: Startup snapshot for optimizing app load time
From: ocramius@gmail.com (Marco Pivetta)

--001a114022c655ff32053060542c
Content-Type: text/plain; charset=UTF-8

While this seems interesting, how would it address storing any context
information of extension?

The code above (in your examples) only stores information about the
autoload stack, but anything that would rely on any extension (core or pecl
or custom) would have to serialize information that is possibly not even
available in userland.

Any clue on that? Would it be acceptable to have it just fail/fatal?


Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

On 13 April 2016 at 17:55, Lin Yo-An <cornelius.howl@gmail.com> wrote:

> Hi internals,
>
>
> The javascript engine V8 uses a strategy called "startup snapshot" to
> optimize app load time (see
> http://v8project.blogspot.tw/2015/09/custom-startup-snapshots.html for
> more
> details)
>
> The approach used by V8 creates a snapshot from heap, so the V8Context
> could be reused directly without re-running the bootstraping code.
>
> I think running javascript app in the browser is somehow like we run php
> script for each requests where the app bootstrapping code is required to be
> executed repeatedly for each request.
>
> Currently, our opcache extension can cache the byte codes, but the byte
> codes still need to be executed every time when bootstrapping an app, and
> which increases the overhead for each request.
>
> For example, a lot of applications use composer to initialize the class
> loader via the statement below:
>
>     require "vendor/autoload.php";
>
> The statement above produces thousands of byte code to run, which is to
> make an app ready. (If you use vld extension to show the opcodes)
>
> However, if we can support a simple syntax to describe what is doing
> "bootstrap", we are able to create a startup snapshot from it.
>
>
> The proposal here want to introduce some new syntax to optimize app load
> time though the below syntax:
>
>     bootstrap "vendor/autoload.php";  // caches the context after running
> this script.
>
> Or
>
>     bootstrap {
>            require "vendor/autoload.php";
>            // do something else for making app ready
>     };
>
> And of course, we might detect the bootstrap script automatically without
> creating new syntax and opcodes, but I think it's hard to do because PHP
> applications can be written by many ways...
>
>
> Questions
> ========
>
> I don't know if this approach is doable or not. Or maybe we can support
> this in a separated extension instead of changing the zend core?
>
> Do you guys think it's doable? would you like to share your idea for this?
>
>
>
>
>
>
> Best Regards,
>
> Yo-An Lin
>

--001a114022c655ff32053060542c--