Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59628 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36368 invoked from network); 10 Apr 2012 08:02:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Apr 2012 08:02:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=luke@cywh.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=luke@cywh.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain cywh.com from 209.85.212.42 cause and error) X-PHP-List-Original-Sender: luke@cywh.com X-Host-Fingerprint: 209.85.212.42 mail-vb0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:58823] helo=mail-vb0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 62/D9-34074-819E38F4 for ; Tue, 10 Apr 2012 04:02:33 -0400 Received: by vbjk13 with SMTP id k13so3286174vbj.29 for ; Tue, 10 Apr 2012 01:02:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=5B30p75jYUYi5i6Rmxbx2CmM6j16VHxO3mic8BY7FeU=; b=bu2QpryDMG5ht7QL2KibaH3fpes7nwlphupdsel+VgA0NuVdZ4WV/YAWqa1F9UulAn vuup7KnivjDHoFEDH8OGf73rRPKA6lBUCTIGrRyWQBrPf99WQajQLXMVcyemB1hZfwcb bExOB4UAeylyf0rNmCtAubf8go7WShjUxS5DT0gY/HMhXmJLCP0Dc9bTcRN2vGBZqmLk l7OdrWtTy7DNzBZ6IDhd+jhqQIVtYaajEPXP6BXyh3YbAtnuT4D0mFYH/GkS8c9xfLIQ 2DfW8eMb0gokvOc8DH8NB+anqrF7scgrGoRnTtxuPJJgv6vFCXzNNyTCO5LnMRlE7eBM 2FIQ== Received: by 10.220.141.84 with SMTP id l20mr5226771vcu.31.1334044949923; Tue, 10 Apr 2012 01:02:29 -0700 (PDT) References: <11343239.3338.1333757773882.JavaMail.mobile-sync@iakr3> <2087324446797252296@unknownmsgid> <4F82F6E9.7050900@php.net> <1366176333732756257@unknownmsgid> <4F83E02F.8030902@php.net> In-Reply-To: <4F83E02F.8030902@php.net> Mime-Version: 1.0 (1.0) Date: Tue, 10 Apr 2012 01:02:27 -0700 Message-ID: <4023768252257297068@unknownmsgid> To: "flavius@php.net" Cc: "internals@lists.php.net" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlnFxa+zzRDYCjAapgLLD12dBMjagDzhQ7ge0nGAGVTSACWcc3t7ZWRRRWm3S4+8ahPYDdL Subject: Re: [PHP-DEV] Persistent zvals From: luke@cywh.com (Luke Scott) On Apr 10, 2012, at 12:24 AM, Flavius Aspra wrote: > On 04/09/2012 10:30 PM, Luke Scott wrote: >> Yeah it would be. He also mentioned something about preloading >> framework classes.. Would like to hear his thoughts on that! > > I also subscribe to the opinion of object persistency not being worth it. In an application server, you could probably achieve more by keeping the entire phar in RAM. > > Currently, you can also simulate that by putting the phar on a ramdisk or similar. This is just the php code though isn't it? It still needs to be converted to opcodes, then executed. Is it possible to execute the phar in a "ready state" (before request, after init of several objects) and make a snapshot of that and use that for every request? (Shouldn't have to be a phar though.) Luke