Closing this one after https://phabricator.wikimedia.org/T270177#6740607
Thu, Jan 21
Sounds good, thanks @Bstorm. I verified that I have access to the CloudVPS project and I can see the VM flavours.
Tue, Jan 19
Could this be a caching related issue that either got resolved or is only affecting specific cases?
Wed, Jan 13
It looks very interesting. Overall it seems like all the metrics between engines are similar except of the total blocking time.
I am wondering how the numbers would changed if the benchmark setup is not just a main div in the DOM but also includes other elements where a map is nested.
Ok, lets use "maps-experiments" instead
Closing this task after T271952
Tue, Jan 12
Some updates from our beta environment:
Mon, Jan 11
Regarding tegola config, I captured all the work done so far here: https://github.com/johngian/openmaptiles-tegola
It involves patches:
- On tegola to make the openmaptiles SQL queries compatible with the tegola config
- On openmaptiles-tools to add a helper tool to generate the tegola config
Wed, Jan 6
Is there a way to figure out what are the articles used for testing? Maybe we can exclude them from wikifeeds. Other than that it doesn't look like an issue in the wikifeeds service level.
Tue, Jan 5
Dec 17 2020
Dec 16 2020
Dec 15 2020
Dec 9 2020
It looks like the debian package was also able to be built on stretch if backports are enabled. I uploaded a debian package built for stretch here:
Can we easily re-use the diff script we had when we evaluated imposm to sample if the output of the new environment is valid ?
I think we should have an item to check if there are any scheduled tasks so when we disable replication and tile-pregeneration there are no in-flight tasks pending.
Dec 8 2020
I wrapped up (partially out of curiosity) the packaging of imposm3 with deb build dependencies, in case we prefer to avoid vendoring:
Dec 4 2020
Dec 3 2020
Regarding the packaging part, here is some context about the state of imposm3 and debian: https://phabricator.wikimedia.org/T238753
Just to add to what Mateus said, our ideas was to investigate how complicated would be to build a debian package for our needs or at least just for the interim for testing purposes.
Dec 1 2020
I think that the SLO definition should be a subtask of this ticket. We need to know what kind of service metrics we maintain and what are the user facing / product driven aspects that we need to keep track to define the SLO.
Nov 24 2020
Although chromium 87 is released, debian buster is still using an old version (83.0.4103.116-1~deb10u3) .
The puppeteer package that we install from npm comes with pre-bundled binaries for browsers. Should we consider using that instead of the debian package?
Usually we prefer software packaged for debian but it might take a while until packages for 87 reach buster.
Nov 23 2020
Added links here: https://wikitech.wikimedia.org/wiki/Push_notifications#Dashboards
Nov 20 2020
Here is the report of the spike addressing the points that the team raised after reviewing it.
Nov 16 2020
I used the same scripts pointing to restbase.svc.eqiad.wmnet and proton.svc.eqiad.wmnet but since it didn't show any issues I didn't paste the whole run output.
Nov 10 2020
Some findings regarding localization alternatives
Nov 9 2020
@akosiaris More from debugging on this issue: