Re: Persistent zvals
| From: | Luke Scott | Date: | Mon, 09 Apr 2012 20:30:03 +0000 |
| Subject: | Re: Persistent zvals | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-59546@lists.php.net to get a copy of this message | ||
On Apr 9, 2012, at 7:49 AM, Flavius Aspra <flavius.as@gmail.com> wrote:
> On 04/07/2012 05:21 AM, Luke Scott wrote:
>> From what I've gathered thus far, it is impossible to do without copying the
>>
>> non-persistent memory into persistent memory, and then back again.
>
> Hi, glad to see you again StackOverflow user:-)
>
> I think I've shown you the route by that [1] project, and yes, the emalloc() call is
> hardcoded in so many places that you'd have to do it this way.
The problem with that is serialization. You can pretty much do the
same thing with APC.
>
> But as Pierre said, an application server for PHP (PHP-FPM?) would be great. The stub part of a
> .phar file could play a big role there.
Yeah it would be. He also mentioned something about preloading
framework classes.. Would like to hear his thoughts on that!
Luke
>
> Regards,
> Flavius
>
> [1] https://github.com/flavius/php-persist
>