Hello and welcome to the latest edition of the WMF Engineering Roadmap and Deployment update.
The full log of planned deployments next week can be found at: https://wikitech.wikimedia.org/wiki/Deployments#Week_of_September_15th
A quick list of notable items...
== Monday == * Revert Wikidata to a known-good version due to issues that were found on Thursday's deploy
* Update CentralNotice to remove dependency on jquery.json ** https://gerrit.wikimedia.org/r/158103
* Japanese Wikipedia to get Cirrus Search as the primary search experience
== Tuesday == * Commons to will get the new CirrusSearch as the primary search engine
* MediaWiki deploy ** group1 to 1.24wmf21: All non-Wikipedia sites (Wiktionary, Wikisource, Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites) ** https://www.mediawiki.org/wiki/MediaWiki_1.24/wmf21
== Wednesday == * Russian Wikipedia to get Cirrus Search as the primary search experience
== Thursday == * MediaWiki deploy ** group2 to 1.24wmf21 (all Wikipedias) ** group0 to 1.24wmf22 (test/test2/testwikidata/mediawiki)
* There will be a method to opt-in to using the new HHVM-powered backend for all WMF wikis. It'll be implemented via a BetaFeature to make it as easy as possible for people to participate. There should be no noticeable negative impact and hopefully only positive impacts.
Thanks and as always, questions and comments welcome,
Greg
<quote name="Greg Grossmeier" date="2014-09-12" time="13:55:16 -0700">
== Tuesday ==
- Commons to will get the new CirrusSearch as the primary search engine
This was an errant copy/paste mistake. Commons already has Cirrus Search as the primary search engine.
On Fri, 12 Sep 2014 13:55:16 -0700, Greg Grossmeier greg@wikimedia.org wrote:
Hello and welcome to the latest edition of the WMF Engineering Roadmap and Deployment update.
The full log of planned deployments next week can be found at: https://wikitech.wikimedia.org/wiki/Deployments#Week_of_September_15th
A quick list of notable items...
[snip]
== Thursday ==
- MediaWiki deploy
** group2 to 1.24wmf21 (all Wikipedias) ** group0 to 1.24wmf22 (test/test2/testwikidata/mediawiki)
- There will be a method to opt-in to using the new HHVM-powered backend for all WMF wikis. It'll be implemented via a BetaFeature to make it as easy as possible for people to participate. There should be no noticeable negative impact and hopefully only positive impacts.
Greg,
The last dot point. Is it there against Thursday 18th? Is it to mark it against another point? The HHVM component sits against next month on the deployment page, so the uncertainty.
Further, as an 'ambassador', I am not sure how to take that dot point to the community, nor to how to explain it. [[mw:HHVM]] doesn't particularly help me, so for a nonce like me, it would be helpful if we could provide some pertinent dot points on what we can/should relay to wiki communities, and we should be looking for if things are going well or poorly.
Thanks. Regards, Billinghurst
<quote name="billinghurst" date="2014-09-13" time="09:38:47 +1000">
- There will be a method to opt-in to using the new HHVM-powered backend for all WMF wikis. It'll be implemented via a BetaFeature to make it as easy as possible for people to participate. There should be no noticeable negative impact and hopefully only positive impacts.
Greg,
The last dot point. Is it there against Thursday 18th? Is it to mark it against another point? The HHVM component sits against next month on the deployment page, so the uncertainty.
To answer all of your questions I'll try to rephrase things in a different manner and add some more details. It might be a little too detailed at first, I'll try to tl;dr at the end:
HHVM is a virtual machine for PHP which improves the performance of the servers by... a lot. We're a little shy of sharing predictions of how improved the performance will be, but it'll be worth the effort.
Thus far HHVM has been deployed to the Beta Cluster, which is our testing environment based in WMF Labs. It has been running there for about a month so far.
Along side that we have a few servers in the production cluster that have been migrated to HHVM. These servers are only sent user traffic if and only if the user sets a cookie in their browser.
In addition to that there are safe-guards in place where if a request to an HHVM server fails, our Varnish layer will take note of that and resend requests to a normal (non-HHVM) server.
The confusion you have regarding HHVM being in the "Next Month" section is because this work is on-going. There were more bullets in that list initially and we will work through them as we get closer to the full rollout/completion.
What is happening next week is this: There will be a new Beta Feature available to all users that will allow them to opt-in to using the HHVM servers by default (the Beta Feature simply sets the cookie I mentioned above). That will happen on Thursday after the normal MediaWiki deploy.
If things go well, users who opt-in will have a better experience: pages should load faster and edits should save faster, for example.
If things don't go well, users who opt-in shouldn't see anything worse than normal (given that safe-guard I mentioned above in the Varnish layer).
tl;dr:
HHVM, an improved (faster) php server, is in the process of being tested at scale and rolled out. We are still at the beginning stages but we feel comfortable enough with the stability we've gained in the Beta Cluster to open it up to more users through a Beta Feature. This Beta Feature will be available for all users on Thursday afternoon (Pacific timezone). Users who opt-in should have a faster wiki experience and in the worst case will not see anything different than normal.
I hope that helps. If you have any more questions please don't hesitate to reply and cc wikitech-l, where the experts on the matter can answer more questions.
Best,
Greg
Thanks Greg. There was nothing mentioned in today's Tech news, so I have just appended some information to enWS. At the WSes we load some big transcluded pages and I have set a little challenge for users to make some comparisons. Are you going to be running data comparisons? Is this something that user (anecdotal) semi-quantitative data is of value? If yes, to the last point, what sort of direct data comparison might be of value?
Regards, Billinghurst
On Fri, 12 Sep 2014 17:42:14 -0700, Greg Grossmeier greg@wikimedia.org wrote:
<quote name="billinghurst" date="2014-09-13" time="09:38:47 +1000"> > > * There will be a method to opt-in to using the new HHVM-powered > > backend > > for all WMF wikis. It'll be implemented via a BetaFeature to make
it
as easy as possible for people to participate. There should be no noticeable negative impact and hopefully only positive impacts.
Greg,
The last dot point. Is it there against Thursday 18th? Is it to mark it against another point? The HHVM component sits against next month on
the
deployment page, so the uncertainty.
To answer all of your questions I'll try to rephrase things in a different manner and add some more details. It might be a little too detailed at first, I'll try to tl;dr at the end:
HHVM is a virtual machine for PHP which improves the performance of the servers by... a lot. We're a little shy of sharing predictions of how improved the performance will be, but it'll be worth the effort.
Thus far HHVM has been deployed to the Beta Cluster, which is our testing environment based in WMF Labs. It has been running there for about a month so far.
Along side that we have a few servers in the production cluster that have been migrated to HHVM. These servers are only sent user traffic if and only if the user sets a cookie in their browser.
In addition to that there are safe-guards in place where if a request to an HHVM server fails, our Varnish layer will take note of that and resend requests to a normal (non-HHVM) server.
The confusion you have regarding HHVM being in the "Next Month" section is because this work is on-going. There were more bullets in that list initially and we will work through them as we get closer to the full rollout/completion.
What is happening next week is this: There will be a new Beta Feature available to all users that will allow them to opt-in to using the HHVM servers by default (the Beta Feature simply sets the cookie I mentioned above). That will happen on Thursday after the normal MediaWiki deploy.
If things go well, users who opt-in will have a better experience: pages should load faster and edits should save faster, for example.
If things don't go well, users who opt-in shouldn't see anything worse than normal (given that safe-guard I mentioned above in the Varnish layer).
tl;dr:
HHVM, an improved (faster) php server, is in the process of being tested at scale and rolled out. We are still at the beginning stages but we feel comfortable enough with the stability we've gained in the Beta Cluster to open it up to more users through a Beta Feature. This Beta Feature will be available for all users on Thursday afternoon (Pacific timezone). Users who opt-in should have a faster wiki experience and in the worst case will not see anything different than normal.
I hope that helps. If you have any more questions please don't hesitate to reply and cc wikitech-l, where the experts on the matter can answer more questions.
Best,
Greg
On Mon, Sep 15, 2014 at 4:53 PM, billinghurst billinghurst@gmail.com wrote:
Thanks Greg. There was nothing mentioned in today's Tech news, so I have just appended some information to enWS.
The HHVM Beta Feature will be featured in the next edition of Tech News: https://meta.wikimedia.org/w/index.php?diff=9857348
I decided to wait until people could enable it before announcing it :)
cc'ing wikitech-l for your questions to get answers direct from the source instead of me playing telephone :)
<quote name="billinghurst" date="2014-09-16" time="00:53:18 +1000">
Thanks Greg. There was nothing mentioned in today's Tech news, so I have just appended some information to enWS. At the WSes we load some big transcluded pages and I have set a little challenge for users to make some comparisons. Are you going to be running data comparisons? Is this something that user (anecdotal) semi-quantitative data is of value? If yes, to the last point, what sort of direct data comparison might be of value?
Regards, Billinghurst
On Fri, 12 Sep 2014 17:42:14 -0700, Greg Grossmeier greg@wikimedia.org wrote:
<quote name="billinghurst" date="2014-09-13" time="09:38:47 +1000"> > > * There will be a method to opt-in to using the new HHVM-powered > > backend > > for all WMF wikis. It'll be implemented via a BetaFeature to make
it
as easy as possible for people to participate. There should be no noticeable negative impact and hopefully only positive impacts.
Greg,
The last dot point. Is it there against Thursday 18th? Is it to mark it against another point? The HHVM component sits against next month on
the
deployment page, so the uncertainty.
To answer all of your questions I'll try to rephrase things in a different manner and add some more details. It might be a little too detailed at first, I'll try to tl;dr at the end:
HHVM is a virtual machine for PHP which improves the performance of the servers by... a lot. We're a little shy of sharing predictions of how improved the performance will be, but it'll be worth the effort.
Thus far HHVM has been deployed to the Beta Cluster, which is our testing environment based in WMF Labs. It has been running there for about a month so far.
Along side that we have a few servers in the production cluster that have been migrated to HHVM. These servers are only sent user traffic if and only if the user sets a cookie in their browser.
In addition to that there are safe-guards in place where if a request to an HHVM server fails, our Varnish layer will take note of that and resend requests to a normal (non-HHVM) server.
The confusion you have regarding HHVM being in the "Next Month" section is because this work is on-going. There were more bullets in that list initially and we will work through them as we get closer to the full rollout/completion.
What is happening next week is this: There will be a new Beta Feature available to all users that will allow them to opt-in to using the HHVM servers by default (the Beta Feature simply sets the cookie I mentioned above). That will happen on Thursday after the normal MediaWiki deploy.
If things go well, users who opt-in will have a better experience: pages should load faster and edits should save faster, for example.
If things don't go well, users who opt-in shouldn't see anything worse than normal (given that safe-guard I mentioned above in the Varnish layer).
tl;dr:
HHVM, an improved (faster) php server, is in the process of being tested at scale and rolled out. We are still at the beginning stages but we feel comfortable enough with the stability we've gained in the Beta Cluster to open it up to more users through a Beta Feature. This Beta Feature will be available for all users on Thursday afternoon (Pacific timezone). Users who opt-in should have a faster wiki experience and in the worst case will not see anything different than normal.
I hope that helps. If you have any more questions please don't hesitate to reply and cc wikitech-l, where the experts on the matter can answer more questions.
Best,
Greg
Wikitech-ambassadors mailing list Wikitech-ambassadors@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
On 9/12/14, 1:55 PM, Greg Grossmeier wrote:
Hello and welcome to the latest edition of the WMF Engineering Roadmap and Deployment update.
The full log of planned deployments next week can be found at: https://wikitech.wikimedia.org/wiki/Deployments#Week_of_September_15th
A quick list of notable items...
== Monday ==
On Monday we will also be removing the "renameuser" right from all bureaucrats on SUL-linked wikis. See https://meta.wikimedia.org/w/index.php?title=Wikimedia_Forum&oldid=9811444#Change_in_renaming_process for more details. The corresponding config change is https://gerrit.wikimedia.org/r/#/c/160158/.
-- Kunal / Legoktm
wikitech-ambassadors@lists.wikimedia.org