Thu, Jul 4
I did some digging on this task during today's chores. Here's what I think I know:
In the last 24 hour period, 11 more ReadingDepth events with odd URLs have caused processing errors. See https://logstash.wikimedia.org/goto/dbe9713837e22a6d5a0d64f09fae1ec2. For these events, the QSON is terminated as we expect but it's prefixed with either iorg_domain_internal=... or operator_user=....
Tue, Jul 2
Noise in EventLogging should be considered a high priority to fix as it creates problems for all people working with our infrastructure, so I suggest we fix this sooner rather than later.
In today's grooming ritual, we wondered aloud whether the MinervaPageActions config is actually needed – it was but is it still?
Mon, Jul 1
- tags (which contain lots of useful information such as MediaWiki version, language, skin...) are handled extremely poorly by kibana in their current format. They should be converted into top-level properties (preferably with field names matching those in PHP errors so that Kibana visualisations / saved searches can be reused). Not sure what's the right place for that: client, EventGate, logstash filter? (The last one has its own domain language so it would be the most painful to maintain.)
Thu, Jun 27
Following on from @DIKW_Pyramid's comment above:
Tue, Jun 25
Thu, Jun 20
Wed, Jun 19
Can we use MediaWiki API caching instead and drop the cache?
Tue, Jun 18
Could we also consider moving the Wikimedia-specific instrumentation for the main menu into the WikimediaEvents extension?
As I mentioned in today's grooming, there's a whole bunch of (now overly-complicated) machinery that we created in order to defer the parsing/DOM construction for the main menu as it's the very top element in #mw-mf-viewport. I think that reevaluating this machinery is well worth it!
Jun 11 2019
I think this could be as simple as adding the following rules:
Is the level of specificity of some of the example CSS rules required, e.g. .mw-rcfilters-ui-filterTagMultiselectWidget-views-select-widget.oo-ui-widget.oo-ui-widget-enabled.oo-ui-selectWidget.oo-ui-selectWidget-unpressed.oo-ui-selectWidget-depressed.oo-ui-buttonSelectWidget ?
Jun 7 2019
… gIven that the bugs are minor.
I've kicked off the request for a physical KaiOS device for @Edtadros.
Jun 6 2019
@phuedx - Do you know which user property controls the "group" preference for this question?
Jun 5 2019
Jun 3 2019
May 24 2019
[Which] combinations of filters are popular?
May 23 2019
May 21 2019
Ian Marlier participated in the site maps project as his own personal initiative, but it has always been out of scope for the Performance Team. And his knowledge of that project left with him, so we're not better equipped than anyone else to do something about this.
- Delete PageSplitTester and PageSplitTesterTest from Wikibase (this will move to Core in T209319)
- Delete PageRandomLookup and PageRandomLookupTest
- Delete related configuration variables from Wikibase
May 14 2019
How frequently is live updates enabled?
@MNeisler: As discussed: I'll take How frequently to users change the limit and days parameters?
May 9 2019
AIUI this isn't High priority but a nice to have. Is that correct, @bearND?
Ping @Jdlrobson (the extension's author IIRC).
May 8 2019
Setting up a development environment could be as trivial as adding the following to MobileFrontendHooks::onOutputPageParserOutput:
Apr 29 2019
Increase in JS bundlesizes should be consistent with the removal of the size of ResourceLoader's mobile.startup module. Change in bytes shipped to client should be recorded.
There are a few nitpicks (their words) from Timo Tijhof on @Jdrewniak's change: https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/RelatedArticles/+/502529/3/resources/ext.relatedArticles.cards/CardView.js
I feel comfortable signing this off in @ovasileva's absence.
Apr 26 2019
Moving to radar as further steps of code chnages to Quicksurveys to fix loading issues with JS should be done by (i think) @phuedx team?
Document the oversampling behaviour for AMC on the schema's talk page so Tilman can understand it