Talk:PHP accelerator

"NuSphere?"[edit]

I've never heard of "NuSphere," and I do plenty of work with PHP and opcode optimizers. 158.228.11.38 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) apparently added it at the top, and I can only assume that it's conflict of interest and the person is promoting his/her obscure product. At the very least, it doesn't deserve to be ahead of any of those listed on the page to begin with. If anyone thinks that "NuSphere" fits Wikipedia's notability requirements, please speak up. Otherwise, I'm going to assume that it's okay to give it the axe due to it not being notable. --koder 20:06, 9 June 2007 (UTC)[reply]

Since nobody spoke up, I yanked it. --slakr 23:22, 17 June 2007 (UTC)[reply]

NuSphere has been around for MANY years. I've heard of their IDE and other products many times in the past. I'm sure the IA Archive's WayBack machine could verify this if needed.--Bobbozzo (talk) 04:54, 7 August 2008 (UTC)[reply]

roadsend PHP Compiler[edit]

This is technically a PHP accelerator, though its a completely different idea. It compiles code from PHP scripts without using the Zend engine:

http://code.roadsend.com/pcc

I think it should be added. —Preceding unsigned comment added by Informedbanker (talk • contribs) 18:07, 25 September 2007 (UTC)[reply]

Not really. Unless it's changed radically and fundamentally from when I last looked, it's a translator from PHP to Scheme that then uses a 3rd party tool to convert Scheme to C followed by compilation from C to a target architecture using whatever C compiler is available. Due in part to the Scheme engine, the end result may or may not be faster than the original PHP code. PHP accelerators as pertaining to the article would give a speedup for all non-trivial cases, operate seamlessly and in real time. Due to the nature of how it works, the steps involved and the end product, none of these are characteristics of Roadsend.

Moggie2002 (talk) 23:54, 23 September 2008 (UTC)[reply]

I think since HipHop for PHP, the topic of PHP compilers/transformers warrants its own topic, or at least a subsection or a link here on this page.

--Demonkoryu (talk) 13:01, 2 September 2010 (UTC)[reply]

Why not part of standard PHP[edit]

There must be a reason why bytecode caching is not already done by PHP itself. To be informative, this article should explain this reason. — Timwi (talk) 18:46, 28 February 2008 (UTC)[reply]

There are two reasons: 1) commercial Zend solution. 2) APC is probably going to get built into php6 as a first free project with code and licence that allows it. Feel free to find sources if you care, for me it's low impact information. 194.30.179.66 (talk) 09:15, 4 February 2011 (UTC)[reply]

http://www.php.net/~derick/meeting-notes.html#add-an-opcode-cache-to-the-distribution-apc

http://talks.php.net/show/php6-unicode-webdeal/2

--Demonkoryu (talk) 09:46, 4 February 2011 (UTC)[reply]

Turck MMCache discountinued?[edit]

How can an open source product be"discontinued"? 24.16.145.189 (talk) 21:24, 22 September 2008 (UTC)[reply]

The lead developer, Dmitry Stogov, left to go and work for Zend (IIRC he told me at the time that this was partly for commercial reasons), and as a result the project halted. Despite being opensource and under the GPL, I seem to remember some issues that hampered the project being continued as it was (perhaps because of the name), and the project eventually forked successfully as EAccelerator. With the lead developer gone, new versions of PHP up and coming to be supported and the project forked as a new opensource codebase with active developers, the last release of the original codebase became out of date and stagnant, to exist only for historical interest. If there were to be any new fork it would be from the latest EAccelerator codebase and not from the MMCache codebase. So the product became discontinued under the name Turck MMCache, and continued to live on as EAccelerator.

Moggie2002 (talk) 22:32, 22 September 2008 (UTC)[reply]

APC !== PHP accelerator[edit]

APC is a type of PHP accelerator, but it should be moved to its own page. It has its own history and topics that are distinct from the general subject of PHP Accelerators. --Isnoop (talk) 08:46, 5 February 2009 (UTC)[reply]

APC is not the PHP Accelerator (PHPA), the project that, after discussions with Nick L. around 2001/2002, spurred George S. to improve APC to support direct execution from SHM rather than de-serialising the compiled code from SHM on each request (this was the trick that APC was missing and why APC was significantly slower at the time than Zend Cache and PHPA). However, as you say, APC is a (type of) PHP accelerator so it should certainly be listed here. That doesn't mean that it couldn't have its own page as well in the same way that some other software products do, such as Microsoft Office.

Moggie2002 (talk) 11:55, 5 February 2009 (UTC)[reply]