Peter (Peter Hedenskog)
Software Engineer, Wikimedia Foundation

Projects (6)

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Wednesday

  • Clear sailing ahead.

User Details

User Since
Aug 17 2015, 6:48 PM (174 w, 17 m)
Availability
Available
IRC Nick
phedenskog
LDAP User
Unknown
MediaWiki User
PHedenskog (WMF) [ Global Accounts ]

Recent Activity

Today

Peter added a comment to T205870: Provision >= 50% of statsd/Graphite-only metrics in Prometheus.

Yes, - browsertime is the correct one, the other one we should remove.

Mon, Dec 17, 2:16 PM · Performance-Team (Radar), Patch-For-Review, monitoring, Operations

Fri, Dec 14

Peter added a comment to T211579: Test on multiple phones using one server.

I think works now, want I want to test out is reverse tethering so the phone can use a limited connection for the server. Or if there's a better way to use a set connectivity. That way we can also use these tests to test without WPR: - we can test full user flow (login etc) or google -> wikipedia.

Fri, Dec 14, 8:07 AM · Performance-Team
Peter closed T181959: Blog post: Why we measure performance as Resolved.

This is done: https://phabricator.wikimedia.org/phame/live/7/post/131/why_performance_matters/

Fri, Dec 14, 7:47 AM · Performance-Team

Thu, Dec 13

Peter added a comment to T211579: Test on multiple phones using one server.

I've been running the same tests today (with auto update turned off) and then for Obama changed from 5 to 7 runs and Facebook from 5 to 9 (see the blue vertical line when the change happened). Looks much better but still a spike on one of the phone. That phones runs without a memory card, I wonder if that matters? Let see if I can update that phone too so they look the same + add a couple of more URLs to test. Then I'll look into what kind of difference we can expect.

Thu, Dec 13, 5:58 PM · Performance-Team
Peter created T211851: Remove unused keys in Graphite for WebPageReplay/WebPageTest.
Thu, Dec 13, 7:34 AM · WebPageTest, WebPageReplay, Performance-Team

Wed, Dec 12

Peter added a comment to T211579: Test on multiple phones using one server.

I've had this running during the day BUT I missed turning off auto updates and I could see that at least some spikes correlated:




Wed, Dec 12, 7:03 PM · Performance-Team
Peter added a comment to T211579: Test on multiple phones using one server.

I got this up and running, sending metrics to Graphite/Grafana on a local instance. I'll try to keep running through the day so we have some stats. I test two different URLs (one on each phone) at the same time, 5 runs and then sleep for 2 minutes and run again. I hope we can see how stable it will be. I collect SpeedIndex, first visual change and all CPU metrics. At the moment I just remove all files, but I can set it up to dump on S3 the coming days so we all can look at it.

Wed, Dec 12, 12:33 PM · Performance-Team
Peter created T211747: Graphite generates a lot of 502 in Grafana.
Wed, Dec 12, 6:44 AM · monitoring, Graphite, Operations, Performance-Team

Tue, Dec 11

Peter added a comment to T211579: Test on multiple phones using one server.

Woho, I got this working today. Two phones (both Moto G5), one computer, starting two containers containing WebPageReplay. I made a couple of runs and the metrics looks stable and I couldn't see that one of the phones affected the other one (but I need to look closer).

Tue, Dec 11, 8:01 PM · Performance-Team

Mon, Dec 10

Peter reassigned T181959: Blog post: Why we measure performance from Peter to Imarlier.

Wow this is your post :)

Mon, Dec 10, 9:09 PM · Performance-Team
Peter created T211618: New alert strategy: One URL can fire first visual change .
Mon, Dec 10, 7:19 PM · WebPageReplay, Performance-Team
Peter created T211579: Test on multiple phones using one server.
Mon, Dec 10, 1:17 PM · Performance-Team

Fri, Dec 7

Peter placed T210416: Upgrade grafana to 5.x up for grabs.

I've checked the WebPageTest and WebPageReplay dashboards and they look ok. There's some GUI fine-tuning I need to do: The new version always displays the row title (Dashboard Row by default) so I need to edit the dashboards so either remove the title or add a meaningful name, but I'll do that when we done the switch.

Fri, Dec 7, 9:50 PM · Performance-Team (Radar), Patch-For-Review, Operations, monitoring, User-CDanis

Thu, Dec 6

Peter created T211352: Add info boxes on each graph/dashboard for WebPageReplay.
Thu, Dec 6, 4:14 PM · Performance-Team, WebPageReplay

Sat, Dec 1

Peter created T210911: Request on mobile isn't recorded in the replay proxy.
Sat, Dec 1, 7:48 AM · WebPageReplay, Performance-Team

Wed, Nov 28

Peter added a comment to T210583: Add slow emulated mobile tests.

[2018-11-28 08:52:14] INFO: 26 requests, 416.83 kb, backEndTime: 939ms (±0.27ms), firstPaint: 1.32s (±0.54ms), firstVisualChange: 1.33s (±0.00ms), DOMContentLoaded: 1.36s (±0.98ms), Load: 1.90s (±1.25ms), speedIndex: 1354 (±0.47), visualComplete85: 1.33s (±0.00ms), lastVisualChange: 3.13s (±7.78ms), rumSpeedIndex: 1566 (±0.82) (3 runs)

Wed, Nov 28, 8:54 AM · WebPageReplay, Performance-Team
Peter closed T210583: Add slow emulated mobile tests as Resolved.

Each run takes 1.5 min, I think that is ok for now. The metrics is so stable though so maybe we could do just one run.

Wed, Nov 28, 8:52 AM · WebPageReplay, Performance-Team
Peter created T210583: Add slow emulated mobile tests.
Wed, Nov 28, 8:41 AM · WebPageReplay, Performance-Team
Peter added a comment to T210549: Firefox tests fail sending metrics to S3.

I added so we surely read export the setting on reboot in @reboot in the crontab (before we start the job).

Wed, Nov 28, 6:00 AM · Performance-Team, WebPageReplay

Tue, Nov 27

Peter closed T210549: Firefox tests fail sending metrics to S3 as Resolved.

I stopped and started the container. It works now, but I need to follow up to look what went wrong.

Tue, Nov 27, 9:39 PM · Performance-Team, WebPageReplay
Peter triaged T210549: Firefox tests fail sending metrics to S3 as High priority.
Tue, Nov 27, 9:33 PM · Performance-Team, WebPageReplay
Peter created T210549: Firefox tests fail sending metrics to S3.
Tue, Nov 27, 9:32 PM · Performance-Team, WebPageReplay
Peter added a comment to T197847: Collect performance metrics from a mobile over time.

This is my setup: On my local machine I run Graphite/Grafana with docker-compose and then I use Ubuntu in Parallels running a simple bash script:

Tue, Nov 27, 8:34 AM · Performance-Team

Mon, Nov 26

Peter claimed T210125: Add documentation for how to instrument frontend measurements.
Mon, Nov 26, 9:02 PM · Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

I think this is done for now, to add more the trace pickup needs to be fixed: https://github.com/sitespeedio/chrome-trace/issues/6

Mon, Nov 26, 7:07 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team

Fri, Nov 23

Peter added a comment to T207251: Test out different trace settings for Chrome .

This worked as before so let us keep that over the weekend + run on desktop.

Fri, Nov 23, 1:15 PM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

I'm doing one more test, just enabling the trace logs for the timeline (on mobile):

Fri, Nov 23, 12:59 PM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

I reverted back. With the change, timings are reported to different threads, and the script that calculates the time using the main thread didn't fix that. I've seen there been changes in Chrome 70 but we where not affected since we used to use only a high level trace log.

Fri, Nov 23, 12:45 PM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

Ooops, this works fine (as in fine for looking at the trace log) but it broke the calculation on a higher level:

Fri, Nov 23, 12:27 PM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

To get yargs to work I changed:

Fri, Nov 23, 8:40 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

A couple of things: Lighthouse seems to skip the toplevel and use disabled-by-default-lighthouse from Chrome 71 (they moved events to that log that they need) to decrease the size of the trace log. According to issues in Lighthouse 10% of the runs of mobile phone on WPT fails because of a huge trace log.

Fri, Nov 23, 7:38 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

This worked good for mobile testing, I'll enable it for desktop too.

Fri, Nov 23, 7:32 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

Trying one more thing:

Fri, Nov 23, 7:24 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter committed rPPERb2ccfeb640a3: Let us by default go to compare for HAR and viewer for trace logs. (authored by Peter).
Let us by default go to compare for HAR and viewer for trace logs.
Fri, Nov 23, 7:11 AM

Thu, Nov 22

Peter created T210125: Add documentation for how to instrument frontend measurements.
Thu, Nov 22, 8:49 AM · Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

This looks good for the URLs I checked. Maybe a little increase in last visual change but as long a the metrics are stable it doesn't matter (the vertical line is when I updated):

Thu, Nov 22, 8:47 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T209857: Create ISP ranking based on RUM data.

Interesting, thanks @Gilles for sharing! In Sweden kind the mobile situation is like this: We have main provider Telia Company AB that was previously owned by the public sector, What differs for them than the rest, is that they have support for the whole of Sweden. For example if you are up in the north of Sweden, out in the wilderness that's the only provider that works, so I guess their p-high is higher than the rest, but it's because they are the only one that support far away places. Also (if I remember correctly) Hi3G only support larger cities its interesting that they don't have the best score.

Thu, Nov 22, 8:38 AM · MW-1.33-notes (1.33.0-wmf.8; 2018-12-11), Patch-For-Review, Performance-Team

Wed, Nov 21

Peter committed rPPERb3c3d46fcad9: Add link for trace log to devtools timeline viewer (authored by Peter).
Add link for trace log to devtools timeline viewer
Wed, Nov 21, 1:44 PM
Peter committed rPPER3e07d9a68d90: Add link for trace log to devtools timeline viewer (authored by Peter).
Add link for trace log to devtools timeline viewer
Wed, Nov 21, 1:44 PM
Peter added a comment to T207251: Test out different trace settings for Chrome .

The metrics are still very stable for mobile so I will enable it for desktop too before I move on and add more categories.

Wed, Nov 21, 1:03 PM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

I've pushed that on mobile testing for enwiki and the rest on that server.

Wed, Nov 21, 12:42 PM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

It looks like

toplevel,devtools.timeline, disabled-by-default-devtools.timeline, disabled-by-default-devtools.timeline.stack, v8, disabled-by-default-v8.runtime_stat

can be a good first candidate, let me try on enwiki.

Wed, Nov 21, 12:35 PM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

Argh it was a mistake by me in the settings. When you set trace categories in Chrome, you should start with "-*" as frist category to clean the old settings, however the CLI handling then disabled the full string. Skipping -* works. I've got pretty good trace with

toplevel,blink,v8,cc,gpu,blink.net,disabled-by-default-v8.runtime_stat, disabled-by-default-devtools.timeline.frame, disabled-by-default-blink.feature_usage, v8.execute, blink.user_timing, blink.console, devtools.timeline, disabled-by-default-devtools.timeline, disabled-by-default-devtools.timeline.stack
Wed, Nov 21, 11:42 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T207251: Test out different trace settings for Chrome .

Another thing to test is to make sure we can get deeper traces, so it's easier to actually see things. Let me look into that.

Wed, Nov 21, 10:41 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter added a comment to T210046: Integrate https://chromedevtools.github.io/timeline-viewer/ to our trace logs.

Ok, I was really over optimistic about removing dependencies for accessing other domains, that will not work since the whole timeline panel is loaded from https://chrome-devtools-frontend.appspot.com and others. But maybe it's still ok. I will try to get the unpacking to work (the loading and unpacking works locally at the moment except that the result isn't shown :) ).

Wed, Nov 21, 9:13 AM · Patch-For-Review, WebPageReplay, Performance-Team
Peter updated subscribers of T207251: Test out different trace settings for Chrome .

I tried this yesterday but couldn't get any change. Or rather, I changed to use the default lighthouse, default WepPageTest: We collect more trace logs but we don't get any of value (or more value).

Wed, Nov 21, 7:03 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team
Peter created T210046: Integrate https://chromedevtools.github.io/timeline-viewer/ to our trace logs.
Wed, Nov 21, 6:59 AM · Patch-For-Review, WebPageReplay, Performance-Team

Tue, Nov 20

Peter moved T207251: Test out different trace settings for Chrome from Current Quarter Goals to Doing on the Performance-Team board.
Tue, Nov 20, 8:27 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team

Mon, Nov 19

Peter moved T192050: Use Docker version of WebPageTest agents from Current Quarter Goals to Blocked on the Performance-Team board.
Mon, Nov 19, 7:54 PM · WebPageTest, Performance-Team
Peter added a comment to T192050: Use Docker version of WebPageTest agents.

There's a lot of work going on in the Mozilla team for there WebPageTest setup. Lets wait and see, either they may fix the Docker setup (tagging per browser version) or we can do something together.

Mon, Nov 19, 7:53 PM · WebPageTest, Performance-Team
Peter closed T154895: Investigate late first visual change/start render in Firefox as Declined.

This is what it looks like:


Mon, Nov 19, 7:51 PM · Performance-Team
Peter closed T204300: [investigate] Increase in instability in metrics as Resolved.

Moved to a larger instance, decreased the variance:

Mon, Nov 19, 7:46 PM · WebPageReplay, WebPageTest, Performance-Team
Peter moved T203543: Chrome 69 increase time for first visual change in synthetic testing from Doing to Current Quarter Goals on the Performance-Team board.
Mon, Nov 19, 2:22 PM · WebPageReplay, Upstream, Performance-Team
Peter moved T197847: Collect performance metrics from a mobile over time from Doing to Current Quarter Goals on the Performance-Team board.
Mon, Nov 19, 2:22 PM · Performance-Team
Peter moved T209025: Drive a Moto G5 Chrome from a Raspberry Pi from Doing to Current Quarter Goals on the Performance-Team board.
Mon, Nov 19, 2:22 PM · Performance-Team
Peter moved T205722: Prepare materials for internal synthetic testing presentation from Backlog: Impact / Goals to Doing on the Performance-Team board.
Mon, Nov 19, 2:22 PM · Performance-Team

Nov 12 2018

Peter placed T208999: [Bug] lastVisualChange osciallating by ~1s and fullyLoaded oscillating by ~.5s on Obama enwiki prod desktop ~Nov 4 2018 up for grabs.
Nov 12 2018, 9:46 PM · WebPageTest, Performance, Readers-Web-Backlog (Tracking), Performance-Team
Peter updated subscribers of T208999: [Bug] lastVisualChange osciallating by ~1s and fullyLoaded oscillating by ~.5s on Obama enwiki prod desktop ~Nov 4 2018.

When I look at these kind of things I always first look at screenshots/videos. There's two reasons: Either there's content that do the change (running a banner etc) or it's bug in the tool, for example Chrome could have change changed the size of the small loading bar at the bottom of screen.

Nov 12 2018, 9:45 PM · WebPageTest, Performance, Readers-Web-Backlog (Tracking), Performance-Team
Peter moved T207440: Chrome 69 -> Chrome 70 changes in metrics from Doing to Current Quarter Goals on the Performance-Team board.
Nov 12 2018, 9:06 PM · WebPageTest, WebPageReplay, Performance-Team
Peter moved T209025: Drive a Moto G5 Chrome from a Raspberry Pi from Current Quarter Goals to Doing on the Performance-Team board.
Nov 12 2018, 9:05 PM · Performance-Team
Peter moved T209025: Drive a Moto G5 Chrome from a Raspberry Pi from Inbox to Current Quarter Goals on the Performance-Team board.
Nov 12 2018, 9:05 PM · Performance-Team

Nov 9 2018

Peter added a comment to T209025: Drive a Moto G5 Chrome from a Raspberry Pi.

Puh, I spent all night getting this to work but no look so far. To get a new version of adb, I've used https://github.com/wjfsanhe/aaddbb_arm_with_boringssl that's a version that works with reverse tethering and newer Chromedrivers. However when I use that version (and other "newer" adbs) it fails earlier then before. The browser doesn't start:

Nov 9 2018, 8:09 AM · Performance-Team

Nov 8 2018

Peter added a comment to T209025: Drive a Moto G5 Chrome from a Raspberry Pi.

Chromedriver works now (after installing apt-get install libnss3 webp libxss1 libxcursor1 libminizip-dev) but there are still a mismatch between adb and the driver. The browser start on the phone (woho!) but then exit. I'll try to compile a new adb version.

Nov 8 2018, 1:34 PM · Performance-Team
Peter added a comment to T209025: Drive a Moto G5 Chrome from a Raspberry Pi.

The instructions works so far. I've got what i need installed and adb finds my phone:

Nov 8 2018, 1:24 PM · Performance-Team
Peter added a comment to T209025: Drive a Moto G5 Chrome from a Raspberry Pi.

I've started following the instructions on https://github.com/WPO-Foundation/webpagetest/blob/master/docs/Private%20Instances/MobileAgentRaspberryPi.md

Nov 8 2018, 12:00 PM · Performance-Team
Peter added a comment to T197847: Collect performance metrics from a mobile over time.

We had the same spike on AWS but it looks differently:


Nov 8 2018, 9:25 AM · Performance-Team
Peter added a comment to T197847: Collect performance metrics from a mobile over time.

I had it up and running for some time yesterday until my battery run out of power. The next I will try more runs to see if we can get more stable metrics. There was two things, checkout the spike in First Visual Change that correlates to really low time spent in JS:


Nov 8 2018, 9:20 AM · Performance-Team
Peter added a comment to T209025: Drive a Moto G5 Chrome from a Raspberry Pi.

The problem at the moment is with Adb. When I run it standalone it starts and I can see that it listens on the correct port for tcp traffic but when I try to start Chrome on the phone I get:

Nov 8 2018, 9:14 AM · Performance-Team
Peter added a comment to T209025: Drive a Moto G5 Chrome from a Raspberry Pi.

I've been trying to drive my phone from my Raspberry but no luck so far. I've been trying both standalone Chromedriver/adb and everything in a pre-baked Docker container.

Nov 8 2018, 9:10 AM · Performance-Team
Peter triaged T209025: Drive a Moto G5 Chrome from a Raspberry Pi as Normal priority.
Nov 8 2018, 8:55 AM · Performance-Team

Nov 7 2018

Peter added a comment to T197847: Collect performance metrics from a mobile over time.

One of the problems was that Browsertime automatically tries to download Chromedriver, but since there's no pre-built on ARM it fails. I've added so it just skips installing on ARM and then I'll try to see if I can get a matching version to work.

Nov 7 2018, 3:26 PM · Performance-Team
Peter added a comment to T197847: Collect performance metrics from a mobile over time.

I had a go trying out to drive the phone from my Raspberry but got stuck on installing Chromedriver (that you need to drive chrome). Chromedriver doesn't support ARM, Docker containers needs to be built upon ARM base containers. I tried that too but then the container can't install the driver.

Nov 7 2018, 2:35 PM · Performance-Team
Peter added a comment to T197847: Collect performance metrics from a mobile over time.

I got this up and running today. I need to fine-tune the start script a little but more (removing Docker data etc after each run) but I've been able to have it up and running for a couple of hours at least. At the moment we do 5 runs (the blur vertical line is when I turned on devtools.timeline):

Nov 7 2018, 1:11 PM · Performance-Team

Nov 6 2018

Peter added a comment to T197847: Collect performance metrics from a mobile over time.

Argh I need to write down the fix for this since I spent many hours to try to solve it:
I've been working on to minimize and understand the difference in firstPaint and firstVisualChange when running on Android. Since we use WebPageReplay and I want it to all "just work" I use the Docker container, and that only works on Linux. I run Ubuntu 16 in Parallels on my other laptop and to be able to do changes locally on Ubuntu, I rebuild the container ...

docker build -t XXX ..

But on my machine I couldn't build because it couldn't find any dependency for the container from archive.ubuntu.com. After some searching I found the fix. Change /etc/default/docker and enable the row:

Nov 6 2018, 8:58 PM · Performance-Team

Nov 4 2018

rafidaslam awarded Blog Post: Best friends forever a Orange Medal token.
Nov 4 2018, 1:38 PM · Performance-Team

Nov 1 2018

Peter added a comment to T197847: Collect performance metrics from a mobile over time.

I started this again today. I got a new computer and I can use my old running Ubuntu for a couple of days. My plan is to get it up and running early next week.

Nov 1 2018, 1:08 PM · Performance-Team
Peter closed T206301: Prepare presentation for our synthetic testing for Mozilla as Resolved.
Nov 1 2018, 1:02 PM · Performance-Team
Peter closed T206301: Prepare presentation for our synthetic testing for Mozilla, a subtask of T205722: Prepare materials for internal synthetic testing presentation, as Resolved.
Nov 1 2018, 1:02 PM · Performance-Team

Oct 29 2018

Peter moved T207440: Chrome 69 -> Chrome 70 changes in metrics from Inbox to Doing on the Performance-Team board.
Oct 29 2018, 9:14 PM · WebPageTest, WebPageReplay, Performance-Team

Oct 24 2018

Peter added a comment to T207440: Chrome 69 -> Chrome 70 changes in metrics.

They are all updated. Lets have a new go at looking at the metrics.

Oct 24 2018, 3:44 AM · WebPageTest, WebPageReplay, Performance-Team
Peter added a comment to T207440: Chrome 69 -> Chrome 70 changes in metrics.

Yep that was the problem. That vertical line to the right is when I made the change (adding back the start white parameter).

Oct 24 2018, 3:25 AM · WebPageTest, WebPageReplay, Performance-Team

Oct 23 2018

Peter added a comment to T207440: Chrome 69 -> Chrome 70 changes in metrics.

I've deployed a version for enwiki/group 0 etc that uses the --startWhite again to see if we see any difference. Hopefully we do, else I need to dig into the color swapping and that's more complicated (if that's the cause). It probably need to run until tomorrow for us to know for sure.

Oct 23 2018, 8:42 AM · WebPageTest, WebPageReplay, Performance-Team
Peter added a comment to T207440: Chrome 69 -> Chrome 70 changes in metrics.

Hmm. I've been going through what it looks like for different wikis and for enwiki it's looks like 70 introduced more deviation. But looking at the group0 wikis we can see that it's an upgrade of Browsertime that causes more unstable metrics:

Oct 23 2018, 7:37 AM · WebPageTest, WebPageReplay, Performance-Team

Oct 22 2018

Peter added a comment to T207440: Chrome 69 -> Chrome 70 changes in metrics.

Another interesting thing is that Chrome 70 increased deviation between runs:

Oct 22 2018, 1:08 PM · WebPageTest, WebPageReplay, Performance-Team

Oct 19 2018

mmodell awarded Blog Post: Best friends forever a Orange Medal token.
Oct 19 2018, 9:28 PM · Performance-Team
Peter created T207440: Chrome 69 -> Chrome 70 changes in metrics.
Oct 19 2018, 7:52 AM · WebPageTest, WebPageReplay, Performance-Team

Oct 18 2018

Peter closed T207252: Upgrade to Chrome 70 as Resolved.

This is done now, I'll add some graphs later on,

Oct 18 2018, 7:27 AM · Performance-Team, WebPageReplay

Oct 17 2018

Peter added a comment to T207252: Upgrade to Chrome 70.

Sometimes I feel I miss a more high level version of the Chrome changelog: https://chromium.googlesource.com/chromium/src/+log/69.0.3497.100..70.0.3538.67?pretty=fuller&n=10000

Oct 17 2018, 12:53 PM · Performance-Team, WebPageReplay
Peter added a comment to T133646: Run performance test on commits.

Did you see https://tech.trivago.com/2018/10/12/building-fast-and-reliable-web-applications/ @Krinkle

Oct 17 2018, 6:03 AM · MW-1.32-notes (WMF-deploy-2018-08-28 (1.32.0-wmf.19)), Patch-For-Review, Epic, Performance-Team
Peter created T207252: Upgrade to Chrome 70.
Oct 17 2018, 5:49 AM · Performance-Team, WebPageReplay
Peter created T207251: Test out different trace settings for Chrome .
Oct 17 2018, 5:41 AM · Browser-Support-Google-Chrome, WebPageReplay, Performance-Team

Oct 12 2018

Peter closed T206594: Move from c4.xlarge to c5.xlarge and c4.large to c5.large as Resolved.

Moved the last one to c5.large (and updated the docs) just now.

Oct 12 2018, 5:45 AM · WebPageReplay, Performance-Team

Oct 11 2018

Peter added a comment to T175708: Add annotations per URL tested in WebPagetest.

5.3.0 has been released.

Oct 11 2018, 8:17 PM · WebPageReplay, Performance-Team, WebPageTest
Peter moved T197847: Collect performance metrics from a mobile over time from Current Quarter Goals to Doing on the Performance-Team board.
Oct 11 2018, 6:28 PM · Performance-Team
Peter renamed T206594: Move from c4.xlarge to c5.xlarge and c4.large to c5.large from Move from c4.xlarge to c5.xlarge to Move from c4.xlarge to c5.xlarge and c4.large to c5.large.
Oct 11 2018, 8:45 AM · WebPageReplay, Performance-Team
Peter added a comment to T206594: Move from c4.xlarge to c5.xlarge and c4.large to c5.large.

I've updated the Firefox server to c5.xlarge and changed ewiki to also run on c5 series (c5.large). That one is also cheaper and a little bit faster.

Oct 11 2018, 8:45 AM · WebPageReplay, Performance-Team

Oct 10 2018

phuedx awarded Blog Post: Best friends forever a Mountain of Wealth token.
Oct 10 2018, 4:13 PM · Performance-Team
Peter created T206594: Move from c4.xlarge to c5.xlarge and c4.large to c5.large.
Oct 10 2018, 6:47 AM · WebPageReplay, Performance-Team

Oct 8 2018

Peter closed T205603: Setup alerts for Firefox as Resolved.

Enabled them just now. 40 ms/40 points for Speed Index for all tests for now.

Oct 8 2018, 9:09 AM · Performance-Team, WebPageReplay
Peter added a comment to T204300: [investigate] Increase in instability in metrics.

This is what it looks like going back 90 days:

Oct 8 2018, 8:02 AM · WebPageReplay, WebPageTest, Performance-Team