[reply] [-] Description Fred Bauder 2013-11-06 02:40:49 UTC Please see the short discussion at https://www.mediawiki.org/w/index.php?title=Project:Support_desk&offset=...
If it is necessary in the sense that something must be changed in the mediawiki software to utilize this php accelerator if present, and it would improve performance, please include support for the Zend_OPcache_v7.0.3-dev I have no idea what is involved other than that gained from reading the Wikipedia article https://en.wikipedia.org/wiki/List_of_PHP_accelerators [reply] [-] Comment 1 Andre Klapper 2013-11-06 09:42:22 UTC (In reply to comment #0)
Please see the short discussion at https://www.mediawiki.org/w/index.php?title=Project: Support_desk&offset=20131104170209#Zend_OPcache_v7.0.3-dev_35188
Could you please summarize it here, and come up with one sentence that describes what this bug report is about, and put that sentence into the "Summary" field? Status: NEW → UNCONFIRMED Ever confirmed: false Severity: normal → enhancement [reply] [-] Comment 2 Fred Bauder 2013-11-06 11:38:16 UTC (In reply to comment #1)
(In reply to comment #0)
Please see the short discussion at https://www.mediawiki.org/w/index.php?title=Project: Support_desk&offset=20131104170209#Zend_OPcache_v7.0.3-dev_35188
Could you please summarize it here, and come up with one sentence that describes what this bug report is about, and put that sentence into the "Summary" field?
I'm not sure what the summary field is or how to put anything in it, but when installing Mediawiki the installer searches for an extension to php that would do data caching and looks for APC Xcache Wincach. Does Zend_OPcache_v7.0.3-dev add anything to Mediawiki functionality and is support for it needed? Or does it function without anything being added to Mediawiki software? It was added to the latest version of PHP in March, 2013.
I guess the summary would be Support for Zend_OPcache_v7.0.3-dev [reply] [-] Comment 3 Andre Klapper 2013-11-06 11:43:41 UTC So does Zend OPcache support data caching? [reply] [-] Comment 4 Fred Bauder 2013-11-06 11:50:19 UTC Not according to the wikipedia article, however it does "opcaching" Is Mediawiki configured to use what it does do? [reply] [-] Comment 5 Andre Klapper 2013-11-06 12:39:13 UTC Refering to the Support Desk thread where you asked "Would this Zend OPcache v7.0.3-dev do the same thing?", you answered this yourself by "No" in comment 4.
So I don't know what you request in this bug report is and what you would like to achieve.
Also see https://www.mediawiki.org/wiki/Manual:MediaWiki_architecture#Caching and https://meta.wikimedia.org/wiki/Talk:PHP_caching_and_optimization for general information. [reply] [-] Comment 6 Fred Bauder 2013-11-06 15:25:15 UTC I am not a reliable source with respect to a question that I don't know the answer to. There is no use in rephrasing the support request repeatedly, but here goes: is Zend_OPcache_v7.0.3-dev supported by Mediawiki; what does it de; should it be supported? [reply] [-] Comment 7 Andre Klapper 2013-11-06 15:31:43 UTC Closing as INVALID, a bugtracker is not the place to discuss this. Please refer to the support desk or the mediawiki-l mailing list at https://lists.wikimedia.org/mailman/listinfo/mediawiki-l Status: UNCONFIRMED → RESOLVED Resolution: --- → INVALID
Rather like the other bug I submitted 10 years ago. Dismissed... but how about Zend_OPcache_v7.0.3-dev_35188?
Fred
Also see https://www.mediawiki.org/wiki/Manual:MediaWiki_architecture#Caching
which has this: "The last caching layer consists of the PHP opcode cache, commonly enabled to speed up PHP applications. Compilation can be a lengthy process; to avoid compiling PHP scripts into opcode every time they're invoked, a PHP accelerator can be used to store the compiled opcode and execute it directly without compilation. MediaWiki will "just work" with many accelerators such as APC, PHP accelerator and eAccelerator.
Because of its Wikimedia bias, MediaWiki is optimized for this complete, multi-layer, distributed caching infrastructure. Nonetheless, it also natively supports alternate setups for smaller sites. For example, it offers an optional simplistic file caching system that stores the output of fully rendered pages, like Squid does. Also, MediaWiki's abstract object caching layer lets it store the cached objects in several places, including the file system, the database, or the opcode cache.
So does Zend_OPcache_v7.0.3-dev_35188 just work?
Fred
On Nov 6, 2013 11:38 AM, "Fred Bauder" fredbaud@fairpoint.net wrote:
[reply] [-] Comment 7 Andre Klapper 2013-11-06 15:31:43 UTC Closing as INVALID, a bugtracker is not the place to discuss this. Please refer to the support desk or the mediawiki-l mailing list at https://lists.wikimedia.org/mailman/listinfo/mediawiki-l Status: UNCONFIRMED → RESOLVED Resolution: --- → INVALID
Rather like the other bug I submitted 10 years ago. Dismissed... but how about Zend_OPcache_v7.0.3-dev_35188?
This is not an appropriate way to move discussion from bug to the mailing list.
You copy/pasted some or all of a bugzilla bug but didn't state the bug number. You moved discussion first to bugzilla and then to this list without referring readers in the first place you posted to the latter instances. (better link: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Zend_OPcache_v7.0...) That wall of text is made substantially less readable because of the ways it was transformed from the original to plain text. (overescaped entities, no line breaks between comments, etc. also the metadata seems to be missing too.) You should typically just *link* the URL for the bug but not copy/paste wholesale.
If you want an answer you should give the bug number in question and a brief summary of the question.
On Nov 6, 2013 12:07 PM, "Fred Bauder" fredbaud@fairpoint.net wrote:
Also see https://www.mediawiki.org/wiki/Manual:MediaWiki_architecture#Caching
which has this: "The last caching layer consists of the PHP opcode cache, commonly enabled to speed up PHP applications. Compilation can be a lengthy process; to avoid compiling PHP scripts into opcode every time they're invoked, a PHP accelerator can be used to store the compiled opcode and execute it directly without compilation. MediaWiki will "just work" with many accelerators such as APC, PHP accelerator and eAccelerator.
Because of its Wikimedia bias, MediaWiki is optimized for this complete, multi-layer, distributed caching infrastructure. Nonetheless, it also natively supports alternate setups for smaller sites. For example, it offers an optional simplistic file caching system that stores the output of fully rendered pages, like Squid does. Also, MediaWiki's abstract object caching layer lets it store the cached objects in several places, including the file system, the database, or the opcode cache.
So does Zend_OPcache_v7.0.3-dev_35188 just work?
That's a bit better. Have you considered that you may have to answer the question yourself?
If you care so much about getting an answer then why don't you test it? or ask Zend if they have?
What's your goal anyway? surely APC will have a bigger share of MediaWiki instances for the foreseeable future, right? is there a reason *not* to use APC?
Also, based on my reading of your thread there's 2 different kinds of caching being discussed: object and opcode caching. I'm unsure if you've noticed that difference or which your asking about. (both are mentioned at https://www.mediawiki.org/wiki/Manual:Cache ; see first 2 sections after TOC)
-Jeremy
mediawiki-l@lists.wikimedia.org