Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67393
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain oracle.com designates 141.146.126.69 as permitted sender)
Message-ID: <518D5069.90903@oracle.com>
Date: Fri, 10 May 2013 12:54:17 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Pierre Schmitz <pierre@archlinux.de>
CC: internals@lists.php.net
References: <ec8323fa7c2a52a381bf7c18a8242bb2@archlinux.de>
In-Reply-To: <ec8323fa7c2a52a381bf7c18a8242bb2@archlinux.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 5.5 and APC user cache upgrade path
From: christopher.jones@oracle.com (Christopher Jones)



On 05/09/2013 05:02 AM, Pierre Schmitz wrote:
> Hi,
>
> I am testing PHP 5.5 atm and how we can package it for Arch Linux and
> provide an upgrade path for users. The RC1 looks pretty solid so far.
>
> As the new opcache does not provide a user cache to store custom
> variables, I would be glad if you could clarify what the best migration
> from 5.4 would be.
> * Is APC basically dead and wont support PHP 5.5?

 From the lack of APC activity and from comments Rasmus has made in the
bugs (e.g. [1]) this is a safe assumption.

> * Should APC users switch to opcache and APCu? (with APCu replacing the
> APC package)

OPcache is definitely the opcode cache solution for PHP 5.5

For user data caches, there are a number of alternatives, as you
noted.  During this initial transition phase it isn't clear what the
directions of each solution will be.  It isn't clear that there will
be one dominant solution.  I'll leave it to Laruence and Joe to
state their cases for world domination of YAC and APCu, respectively.

Chris

[1] https://bugs.php.net/bug.php?id=64625


> For PHP application developers:
> * Regarding APCu: it provides the old PHP interface function as well as
> their own apcu_* functions. They are aliases right now. Should
> application developers think about switching to the apcu_-API as new
> features will be available only here?
>
> Bonus question:
> * Right now very similar functionality is provided by APCu, XCache,
> WinCache, YAC etc.. Are there plans to include such functionality inside
> PHP in future to make application developers life a little easier? At
> least a common API would be great. There were several bugs in
> applications as these modules behave a little different regarding return
> values etc..
>
> Greetings,
>
> Pierre
>

-- 
christopher.jones@oracle.com  http://twitter.com/ghrd
Newly updated, free PHP & Oracle book:
http://www.oracle.com/technetwork/topics/php/underground-php-oracle-manual-098250.html