去年十一月出 PHP 7.2，現在已經更新到 7.2.5，各家軟體的相容性也都修的差不多了，差不多該升級了。
在「PHP 7.2 的效能改善」這邊有提到與 PHP 7.1 的效能改善主要來自於同時間有多人同時存取時的最佳化。
同樣 wiki 也跟著更新了，來看看效果如何...
所以有新的 streaming protocol 取代本來的 RCStream：「Get live updates to Wikimedia projects with EventStreams」。
這次新的 protocol 是走標準協定：
EventStreams is built on the w3c standard Server Sent Events (SSE). SSE is simply a streaming HTTP connection with event data in a particular text format. Client libraries, usually called EventSource, assist with building responsive tools, but because SSE is really just HTTP, you can use any HTTP client (even curl!) to consume it.
MediaWiki 系統提供的 API 在維基基金會上的專案都關掉了。主要是因為維基基金會的專案量太大，前方有大量的 cache 擋住，後端能提供的資料其實沒有意義。取而代之的是另外規劃出來的 API。
實際測試發現資料從 2015/07/01 開始，每日更新的速度還不錯，像是 UTC 還是 2016/07/31 的現在可以取到 2016/07/30 的資料了。舉例來說，想要拉中文版 Kalafina 在 2016 七月由人閱覽的資料：
先前 MediaWiki 所提供的「變更通知」都只有在信件裡「通知」，而沒有在信件裡列出「改變的內容」，這使得讀信的人要再點進去看... (於是就懶的點了)
而前陣子看到有人寫了 extension 來輸出 diff，解決了這個問題：「MediaWiki extension EmailDiff: notification emails improved」。
Version differences: @@ -846,5 +887,3 @@ In cattle, temperament can affect production traits such as carcass and meat quality or milk yield as well as affecting the animal's overall health and -reproduction. Cattle temperament is defined as "the consistent behavioral and physiological -difference observed between individuals in response to a stressor or environmental +reproduction. If you succeed in tipping a cow only partway, such that only one +of its feet is still on the ground, you have created lean beef. Such a feat is +well done. Naturally, being outside, the cow is unstable. When it falls over, +it becomes ground beef. Cattle temperament is defined as "the consistent behavioral +and physiological difference observed between individuals in response to a stressor or environmental challenge and is used to describe the relatively stable difference in the behavioral predisposition of an animal, which can be related to psychobiological mechanisms.
這邊講的「付費帳號」被定義為 undisclosed paid advocacy，也就是存在利益衝突但故意不揭露的情況。維基百科的人還產生了一張圖來說明這次 381 個帳號被停權檢查的情況：(黃色是 IP address，綠色是 username，可以看出很多重疊的情況)
在「Get help editing Wikipedia with the new “Co-op” mentorship program」這邊看到英文版維基百科引入了導師的制度。
以往比較資深的編輯都是直接修正，或是到新手的 Talk 頁上提出建議，現在則是引入了導師的制度，從而得到了不錯的成果。
Mentored editors were more productive than compared to editors who were not mentored. During the pilot, mentored editors made 7 times as many edits (35 vs. 4.5 in median edits). They also edited more articles during the pilot (10 vs. 3 on average).
68% of mentored editors remained active in April 2015, the month after the end of pilot, whereas only 22% of non-mentored editors remained active.
Editors using the Co-op waited far less time for mentorship to begin (12 hours) compared to the only other mentorship space on en.wiki, Adopt-a-user (4 days).
Despite being geared toward newer editors, the Co-op was utilized by more experienced editors who reported having positive and constructive experiences through mentorship.
整個計畫到實作完成長達十年 (大約從 2004 年開始有想法)，接下來進入最後階段：
This week, we will begin the process of renaming the remaining 1.46 million accounts – those which have not responded to all attempts at outreach. That process is expected to take approximately one to two weeks.
維基基金會在報告裡有提供一些 PV 相關的數據，包括 comScore 的數字與自己 server log 所統計出來的數據。另外也包含了財務狀況。
可以看到在測試 HHVM 的計畫，而且目前看起來還不錯：「[Wikitech-l] [Engineering] Migrating test.wikipedia.org to HHVM」，拿了 test.wikipedia.org 測試，其中 speed test 的部份有大幅改善：
1) Speed test: measure the time taken to request the page 1000 times over just 10 concurrent connections: HHVM Zend diff Mean time (ms): 233 441 -47% 99th percentile (ms): 370 869 -57% Request/s: 43 22.6 +90%
2) Load test: measure how much thoughput we obtain when hogging the appserver with 50 concurrent requests for a grand total of 10000 requests. What I wanted to test in this case was the performance degradation and the systems resource consumption HHVM Zend diff Mean time (ms): 355 906 -61% 99th percentile (ms): 791 1453 -45% Request/s: 141 55.1 +156% Network (Mbytes/s) 17 7 +142% RAM used (GBs): 5(1) 11(4) CPU usage (%): 90(75) 100(90)
維基百科之所以沒有遇到太多問題，主要是因為所使用的軟體是 open source 而且夠大的關係，直接成為 HHVM 測試的一環：「Compatibility Update」。
另外一方面，搜尋引擎的更換就沒有這麼順利，雖然換到 Elasticsearch 後改善不少，不過可以看到八月的報告這樣寫：
tarted deploying Cirrus as the primary search back-end to more of the remaining wikis and we found what looks like our biggest open performance bottleneck. Next month's goal is to fix it and deploy to more wikis (probably not all). We're also working on getting more hardware.
In September we worked to mitigate the performance bottleneck that we found in August. We found there to be no silver bullet but used the information we learned to pick and order appropriate hardware to handle the remaining wikis. We also implemented out significantly improved wikitext Regular Expression search. In October we've begun rolling out the wikitext Regular Expression search and received some of the hardware we need to finish cutting over the remaining wikis. We believe we'll get it all installed in October and cut the remaining wikis over in November.
In October we prepared for November in which we deployed Cirrus to all the remaining wikis by installing new servers installing new versions of Elasticsearch and our plugins. We also fixed up regex search which had caused a search outage.