Peter (Peter Hedenskog)
Software Engineer, Wikimedia Foundation

Projects

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Monday

  • Clear sailing ahead.

User Details

User Since
Aug 17 2015, 6:48 PM (126 w, 4 d)
Availability
Available
IRC Nick
phedenskog
LDAP User
Unknown
MediaWiki User
PHedenskog (WMF)

Recent Activity

Thu, Jan 18

Peter added a comment to T176460: Test out the new Netinfo API coming in Chrome 62.

No collect it should be enough!

Thu, Jan 18, 9:55 AM · Performance-Team
Peter updated the task description for T185186: Explain the sudden change in First Visual Change in the Obama article for FF 57.
Thu, Jan 18, 9:13 AM · Performance-Team
Peter added a comment to T185186: Explain the sudden change in First Visual Change in the Obama article for FF 57.

Adding these for reference later.

Thu, Jan 18, 9:10 AM · Performance-Team
Peter renamed T185186: Explain the sudden change in First Visual Change in the Obama article for FF 57 from Show the to Explain the sudden change in First Visual Change in the Obama article for FF 57.
Thu, Jan 18, 9:07 AM · Performance-Team
Peter created T185186: Explain the sudden change in First Visual Change in the Obama article for FF 57.
Thu, Jan 18, 9:05 AM · Performance-Team
Peter added a comment to T175240: Set up a second permanent WebPageTest agent.

I've made the patches needed for separating IE, if they are ok we can go with that now and then setting up the linux agent "should" only be by adding a extra job in the Jenkins configuration file (with the right configuration) and then we can just run them side by side.

Thu, Jan 18, 7:58 AM · Patch-For-Review, WebPageTest, Performance-Team

Wed, Jan 17

Peter added a comment to T175240: Set up a second permanent WebPageTest agent.

To make it easy we should just move all tests for Internet Explorer to be in separate text files, then we can just add one extra job in Jenkins with different configuration (pointing to the Linux agent) and we are ready to go.

Wed, Jan 17, 10:40 PM · Patch-For-Review, WebPageTest, Performance-Team
Peter added a comment to T178973: Cleanup WebPageTest dashboards.

We should do this when we move to Linux and at the same time remove unused keys in Graphite to make it easier.

Wed, Jan 17, 9:21 AM · Performance-Team, WebPageTest
Peter added a comment to T153358: Consider moving WebPageTest from Amazon to our own setup.

Been thinking about it, I think the reason to have our own agent is to drive mobile phones.

Wed, Jan 17, 9:15 AM · WebPageTest, Performance-Team
Peter closed T181963: Update WebPageTest AMIs as Resolved.

Yep let the old version just stop to work and make sure we moved to Linux before.

Wed, Jan 17, 9:09 AM · Performance-Team, WebPageTest
Peter added a comment to T165626: Move to the new Linux-based WPT agents in AWS.

WebPageTest.org is now running on Linux https://twitter.com/patmeenan/status/951234346458984454 so I think we can move on, even though we had the problems. It's better to just run it side by side with the current version.

Wed, Jan 17, 9:02 AM · Performance-Team, WebPageTest
Peter added a comment to T181963: Update WebPageTest AMIs.

I think we can do like this: Let the current Windows agent die when the new Chrome version is released and move to Linux a month or two before that, since changing to the new Windows agent will affect metrics like SpeedIndex and FirstVisualChange.

Wed, Jan 17, 9:00 AM · Performance-Team, WebPageTest
Peter moved T178529: Switch from IE to Edge from Backlog to Radar on the Performance-Team board.
Wed, Jan 17, 8:55 AM · Performance-Team (Radar), Upstream, WebPageTest
Peter added a comment to T178529: Switch from IE to Edge.

This will not work until AWS has a new Windows version supporting Edge.

Wed, Jan 17, 8:54 AM · Performance-Team (Radar), Upstream, WebPageTest

Tue, Jan 16

Peter added a comment to T165272: Review research on performance perception.

I'll ask him about the difference between when images are finished loading and actually displayed on screen. Like if the difference is X seconds (as we seen before) that should influence the metric.

Tue, Jan 16, 2:17 PM · Performance-Team
Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

@Jdlrobson ah cool, l'll do some more testing first see if I can get a better environment on my phone. For the wikis, it would be best if we could test the exact same article.

Tue, Jan 16, 8:45 AM · Performance-Team

Fri, Jan 12

Jdlrobson awarded T184527: Test performance win with lazy references on a real mobile phone a Barnstar token.
Fri, Jan 12, 4:41 PM · Performance-Team
Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

Ok I got the WebPageReplay server working with my Alcatel. One thing though, I haven't rooted my device and installed the fake certificate instead I'm using ignore-certificate-errors-spki-list so I get a warning in Chrome and some blocked time on the first domain (400-500ms), however the blocking time are the same for both test so it should probably not matter. But I should root it to make sure, I'll try to do that the week after our team meeting.

Fri, Jan 12, 1:24 PM · Performance-Team
Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

Made another sheet on docs @Jhernandez it mostly look the same, have look when you have time. Did 21 runs here too and took the median. I'm gonna try again with WebPageReplay and see if we can comparable first visual change.

Fri, Jan 12, 6:20 AM · Performance-Team
Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

I was a little too fast on the trigger, it seems like mapping ports on my phone doesn't work so the traffic goes through the proxy, I need to look into but it could be quite much work to get it working.

Fri, Jan 12, 5:39 AM · Performance-Team

Thu, Jan 11

Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

I got the Android 6 phone late today and I've tested a couple of tests and I could actually make it work with WebPageReplay (that is actually pretty cool), I need to do a small hack but I'll be able to make the runs tomorrow to see if we can compare Speed Index and First Visual Change.

Thu, Jan 11, 7:20 PM · Performance-Team
Peter added a comment to T184580: Test out AWS device farm.

Had a quick look through the docs and it seems like you can only access the devices from your local server and not from you AWS server. It still could be usable but not as cool :)

Thu, Jan 11, 1:44 PM · Performance-Team
Peter added a comment to T184681: Document how to run performance tests on real phones.

@Jhernandez there's a base there now so you can at least start when you have some time, I'll go through it during the day, try to finish it. Feel free to change/edit things you find are wrong/don't work :)

Thu, Jan 11, 10:05 AM · Readers-Web-Backlog (Tracking), Mobile, Documentation, Performance-Team
Peter added a comment to T184681: Document how to run performance tests on real phones.

I'll continue adding docs https://wikitech.wikimedia.org/wiki/Measure_Performance#Testing_performance_on_your_Android_phone during the day.

Thu, Jan 11, 8:42 AM · Readers-Web-Backlog (Tracking), Mobile, Documentation, Performance-Team
Peter triaged T184681: Document how to run performance tests on real phones as Normal priority.
Thu, Jan 11, 7:33 AM · Readers-Web-Backlog (Tracking), Mobile, Documentation, Performance-Team

Wed, Jan 10

Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

Cool, I'll update https://wikitech.wikimedia.org/wiki/Measure_Performance with examples and how to:s, will start tomorrow morning. Today that only includes desktop testing.

Wed, Jan 10, 1:02 PM · Performance-Team
Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

I wanna keep my Huawei in the original setup, so I bought another phone in the lower spectrum with 512 mb ram but running Android 6. Will not get it until next week though and then I'm off to the perf team meetup. I can do the rest of the testing the 21 but I think the metrics we have from the Chrome timeline is really good, showing us how the improvement.

Wed, Jan 10, 9:18 AM · Performance-Team
Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

Ok, I'm stuck on reversing the traffic on the device using adb reverse ..., my device run Android 4 and reverse was introduced in 5.

Wed, Jan 10, 8:51 AM · Performance-Team
Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

Fixed everything for Visual Metrics but since beta isn't cached we get a much higher TTFB for that URL, so comparing first visual change/speed index will not be fair. I can try to get it to work with WebPageReplay but then I need to root my device and install the fake certificate. I had a go at that a couple of weeks ago but didn't get it to work, but can try again.

Wed, Jan 10, 7:38 AM · Performance-Team
Peter added a comment to T184527: Test performance win with lazy references on a real mobile phone.

I started testing yesterday but run into a bug with VisualMetrics, when getting metrics, I'll fix that first and continue later today.

Wed, Jan 10, 5:43 AM · Performance-Team
Peter added a subtask for T123328: [GOAL] Lazy load references in mobile skin: T184527: Test performance win with lazy references on a real mobile phone.
Wed, Jan 10, 5:24 AM · Readers-Web-Backlog (Tracking), Epic, Goal, Reading-Web-Planning, Reading-Admin
Peter added a parent task for T184527: Test performance win with lazy references on a real mobile phone: T123328: [GOAL] Lazy load references in mobile skin.
Wed, Jan 10, 5:23 AM · Performance-Team
Peter created T184580: Test out AWS device farm.
Wed, Jan 10, 5:19 AM · Performance-Team
Peter renamed T184527: Test performance win with lazy references on a real mobile phone from Test performance win with lazy references to Test performance win with lazy references on a real mobile phone.
Wed, Jan 10, 5:12 AM · Performance-Team
Peter moved T184527: Test performance win with lazy references on a real mobile phone from Inbox to Doing on the Performance-Team board.
Wed, Jan 10, 5:12 AM · Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

We had it running for a while now and it surely looks better. It's been running on a c4.large (same size as the other tests). We had one bug that I haven't looked into yet. It made us report 0 values (bad), I think the origin of the problem is from the Chromedriver when we get the trace log. The behavior changed a couple of versions ago (2.30) and the hack to fix it was to get the log two times. I'll look into it later this week.

Wed, Jan 10, 4:59 AM · Performance-Team

Tue, Jan 9

Peter created T184527: Test performance win with lazy references on a real mobile phone.
Tue, Jan 9, 3:02 PM · Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

The numbers looks better, specially on mobile. That should mean if we do it one instance larger, the numbers will look good on desktop too. I'll let it run like this today just to be 100% sure and then update to a larger instance + make a wrapper for devtools timeline and collect median/min/max, that should be doable tomorrow, so we have something with real numbers running till next week, so we can discuss how we can act on it.

Tue, Jan 9, 1:38 PM · Performance-Team
Peter added a comment to T181877: CSS loading sometimes delayed in Firefox; FOUC reproducibly displayed.

I can also reproduce it on the login page:
https://en.wikipedia.org/w/index.php?title=Special:UserLogin

Tue, Jan 9, 1:24 PM · Upstream, Performance-Team, Browser-Support-Firefox
Peter added a comment to T181413: Refactor NavigationTiming extension so that it can be used to oversample based on criteria.

This will be awesome! I miss docs describing limits and how we do it (but we can add that when it's merged). Like how should we keep track of different oversamplings running, can you run multiple at a time, what should you think about etc.

Tue, Jan 9, 9:30 AM · Patch-For-Review, MediaWiki-extensions-NavigationTiming, Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

I got this up and running on a new instance, will update the dashboard asap we got the metrics. If it works, I'll add so we send rendering/scripting etc and see how stable they are.

Tue, Jan 9, 9:02 AM · Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

Ok, I think we only needs to enable devtools.timeline category, then we can generate the following:

Tue, Jan 9, 8:28 AM · Performance-Team

Mon, Jan 8

Peter closed T180688: Firefox 57 improvement as Resolved.

I'll close it since there's no action for us to fix.

Mon, Jan 8, 9:22 PM · Upstream, Performance-Team
Peter closed T184394: Replay proxy machine stopped working 1/1 as Resolved.

Fixed so it cannot happen again (by setting the name) but not sure why it actually happened the first time.

Mon, Jan 8, 8:55 PM · Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

It do not look good on c4.xlarge either (300 ms diff):

Mon, Jan 8, 7:44 PM · Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

I've started this today by deploying to a c4.xlarge machine and pushing to Graphite with the trace log turned out ok. I also started to try out https://github.com/paulirish/devtools-timeline-model to parse the log.

Mon, Jan 8, 3:07 PM · Performance-Team
Peter moved T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy] from Next-up to Doing on the Performance-Team board.
Mon, Jan 8, 3:02 PM · Performance-Team
Peter added a comment to T184394: Replay proxy machine stopped working 1/1.

I made a couple of changes how we start the containers, giving them the same name, so this never can happen again + I've seen I've missed mapping the clock, so I added that too. I've updated the docs at Wikitech:

Mon, Jan 8, 8:18 AM · Performance-Team
Peter created T184394: Replay proxy machine stopped working 1/1.
Mon, Jan 8, 7:51 AM · Performance-Team

Dec 20 2017

Peter closed T175239: Write a guide on how to test performance locally before pushing changes as Resolved.

I've added an example of how to also run the WebPageReplay tests locally. Think we are done here for now, let me close the issue.

Dec 20 2017, 8:40 AM · Documentation, Performance-Team

Dec 19 2017

Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

Turning off the trace log got us back to those great values again 33 ms diff instead off 300 ms.

Dec 19 2017, 8:28 PM · Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

It doesn't seems it matter so much with that smaller screen with the log turned on, the diff is still 300 ms:

Dec 19 2017, 10:38 AM · Performance-Team
Peter added a comment to T182951: Change the alerts for JS and CSS sizes .

Changed the timespan for all those size graphs to use 3 h instead of average of 24 h (I guess I just copy/pasted that before).

Dec 19 2017, 10:36 AM · Performance-Team, WebPageTest
Peter added a comment to T176361: Run performance tests using local proxy.

Ok, cool. Let me know when you had time to read through the docs at https://wikitech.wikimedia.org/wiki/Performance/WebPageReplay and tried that you can access it @Gilles and I think we can close this issue.

Dec 19 2017, 10:20 AM · Performance-Team

Dec 18 2017

Peter moved T165626: Move to the new Linux-based WPT agents in AWS from Next-up to Doing on the Performance-Team board.
Dec 18 2017, 8:38 PM · Performance-Team, WebPageTest
Peter added a comment to T165626: Move to the new Linux-based WPT agents in AWS.

Added upstream issues:
https://github.com/WPO-Foundation/wptagent/issues/70
https://github.com/WPO-Foundation/wptagent/issues/71

Dec 18 2017, 6:55 AM · Performance-Team, WebPageTest
Peter added a comment to T176361: Run performance tests using local proxy.

Adding this so we remember it: We've been testing out with the viewport 1200x960 for WebPageReplay. With our current setup with WebPageTest we use 1024x768.

Dec 18 2017, 4:47 AM · Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

The setup I was testing was using 1920x1080, default we use 1200x960 for WebPageReplay (and on WebPageTest we use 1024x768).

Dec 18 2017, 4:43 AM · Performance-Team
Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

Ahh I went through the configuration and see that I was running a larger viewport than we do default. Firefox handles that good but not Chrome on AWS. Let me change that and rerun.

Dec 18 2017, 4:25 AM · Performance-Team

Dec 15 2017

Peter added a comment to T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].

I've tested turning on the Chrome trace log on one instance on AWS (c4.large) running with WebPageReplay and the instance is too small:


We are not close to the same stability in first visual change that we usually have. I'lll turn it off for now and check that the metrics looks like it should and then I'll make a quick try on a larger instance to check if it looks better.

Dec 15 2017, 9:07 PM · Performance-Team
Peter added a comment to T165626: Move to the new Linux-based WPT agents in AWS.

The WebPageTest docker containers aren't tagged per release so our old instructions of how to get it up and running isn't working anymore (at least for me), I've added issue upstream https://github.com/WPO-Foundation/webpagetest/issues/1069

Dec 15 2017, 2:13 PM · Performance-Team, WebPageTest
Peter added a comment to T165626: Move to the new Linux-based WPT agents in AWS.

Hmm our Docker instructions doesn't work anymore. Note to myself to update them when I get them to work.

Dec 15 2017, 8:36 AM · Performance-Team, WebPageTest
Peter added a comment to T165626: Move to the new Linux-based WPT agents in AWS.

@Imarlier yes, I'll ping you early next week if I don't get it going. I'll try to reproduce with the Docker containers locally first (I actually didn't try that before).

Dec 15 2017, 8:24 AM · Performance-Team, WebPageTest
Peter created T182951: Change the alerts for JS and CSS sizes .
Dec 15 2017, 6:37 AM · Performance-Team, WebPageTest
Peter created T182949: Get size compressed and uncompressed size of JS and CSS.
Dec 15 2017, 6:27 AM · Patch-For-Review, Performance-Team, WebPageTest

Dec 14 2017

Peter added a comment to T165626: Move to the new Linux-based WPT agents in AWS.

Let me start with this tomorrow, would be nice to have it fixed and then start the new year on Linux :)

Dec 14 2017, 3:28 PM · Performance-Team, WebPageTest
Peter added a comment to T165626: Move to the new Linux-based WPT agents in AWS.

Next step: We should run it on AWS but not on the automatic deploy. We should create a Linux instance (there's a Ubuntu install script so we should use Ubuntu I think). Then start the agent so it connects to our WebPageTest server (we probably need to reconfigure our setting on the server, I had problem with that the last time I tried). Then we make sure we start the agent with full logging and then locally we can fire 10 tests from https://github.com/wikimedia/wpt-reporter and compare the times and keep the log so we can attach it to the issue at Github. Maybe we can do a PR when we find the problem.

Dec 14 2017, 3:19 PM · Performance-Team, WebPageTest
Peter closed T182385: Cleanup WebPageReplay for running tests against production as Resolved.

Fixed the last things, now we can just wait 5 days until we have enough data in the alerts.

Dec 14 2017, 11:32 AM · Performance-Team
Peter closed T182385: Cleanup WebPageReplay for running tests against production, a subtask of T176361: Run performance tests using local proxy, as Resolved.
Dec 14 2017, 11:32 AM · Performance-Team
Peter updated the task description for T182385: Cleanup WebPageReplay for running tests against production.
Dec 14 2017, 11:31 AM · Performance-Team

Dec 12 2017

Peter updated the task description for T182385: Cleanup WebPageReplay for running tests against production.
Dec 12 2017, 10:13 AM · Performance-Team
Peter updated the task description for T182385: Cleanup WebPageReplay for running tests against production.
Dec 12 2017, 10:08 AM · Performance-Team

Dec 11 2017

Peter added a comment to T182200: Anonymous 3G speed indices fluctuating by 2000 on the en.wiki Barack Obama article starting on November 30th, 17:00.

Here are some screenshot for Facebook:
http://wpt.wmftest.org/video/compare.php?tests=171211_Z5_NK,171209_2Z_Q9,171209_Q4_64,171207_DR_F

Dec 11 2017, 9:07 PM · Readers-Web-Backlog (Tracking), Performance-Team, Regression
Peter moved T182385: Cleanup WebPageReplay for running tests against production from Inbox to Doing on the Performance-Team board.
Dec 11 2017, 8:52 PM · Performance-Team
Peter updated the task description for T182385: Cleanup WebPageReplay for running tests against production.
Dec 11 2017, 8:31 PM · Performance-Team
Peter renamed T182385: Cleanup WebPageReplay for running tests against production from Setup WebPageReplay for running tests against production to Cleanup WebPageReplay for running tests against production.
Dec 11 2017, 3:43 AM · Performance-Team

Dec 9 2017

Peter created T182510: Measure time spent in scripting/painting/rendering for Chrome [proxy].
Dec 9 2017, 11:41 PM · Performance-Team

Dec 8 2017

Peter closed T182386: Cleanup and find a better structure for the start script in Docker as Resolved.

This is done in Browsertime, see if it can get merge during the weekend and then we can start using that and have better flow for picking up new releases.

Dec 8 2017, 9:34 AM · Performance-Team
Peter closed T182386: Cleanup and find a better structure for the start script in Docker, a subtask of T176361: Run performance tests using local proxy, as Resolved.
Dec 8 2017, 9:34 AM · Performance-Team
Peter added a comment to T176361: Run performance tests using local proxy.

@Gilles and me got Firefox working a couple of days ago. Gilles did a hack with dnsmasq: https://github.com/gi11es/browsertime-replays/tree/ff54-dnsmasq/webpagereplay and I got working with the Firefox preferences network.dns.forceResolv it was introduced in Firefox 55, but we was running 54 since the https://github.com/firebug/har-export-trigger was broken in 55. Running in 57 it works (as long as we turn off getting a HAR).

Dec 8 2017, 5:11 AM · Performance-Team
Peter triaged T182386: Cleanup and find a better structure for the start script in Docker as High priority.
Dec 8 2017, 5:01 AM · Performance-Team
Peter renamed T182385: Cleanup WebPageReplay for running tests against production from Setup WebPageReplay for Production to Setup WebPageReplay for running tests against production.
Dec 8 2017, 4:55 AM · Performance-Team
Peter triaged T182385: Cleanup WebPageReplay for running tests against production as High priority.
Dec 8 2017, 4:54 AM · Performance-Team

Dec 5 2017

Peter added a comment to T181877: CSS loading sometimes delayed in Firefox; FOUC reproducibly displayed.

I've reported what you seen in https://bugzilla.mozilla.org/show_bug.cgi?id=712130, great work @Krinkle !

Dec 5 2017, 8:21 AM · Upstream, Performance-Team, Browser-Support-Firefox

Dec 4 2017

Peter closed T182036: Do the WebPageReplay instance pickup the fundraiser as Resolved.

Works ok, let me sync the viewport.

Dec 4 2017, 8:59 PM · Performance-Team
Peter added a comment to T182036: Do the WebPageReplay instance pickup the fundraiser.

Ok the thing is that the difference is so much lower on WPT but the increase is there for a couple of 100 points, so it is ok. I wonder of we are running different viewports that make the difference so big.

Dec 4 2017, 8:48 PM · Performance-Team
Peter created T182036: Do the WebPageReplay instance pickup the fundraiser.
Dec 4 2017, 8:43 PM · Performance-Team
Peter added a comment to T176361: Run performance tests using local proxy.

@Gilles no I did without Docker in the initial tests where AWS outperformed everything, however I'm not 100% sure that we got the exact same stable metrics as we got now.

Dec 4 2017, 12:31 PM · Performance-Team
Peter moved T180784: Strategy for WebPageTest and NavTiming annotation tags in Grafana from Doing to Next-up on the Performance-Team board.
Dec 4 2017, 12:29 PM · Performance-Team
Peter created T181963: Update WebPageTest AMIs.
Dec 4 2017, 9:06 AM · Performance-Team, WebPageTest
Peter added a comment to T181956: Oversample based on total load time.

I wonder if we could do something smart here with the Resource Timing API? Or what kind of things do we want to catch? Like if the latency looks the same for all resources there's no need to collect the data?

Dec 4 2017, 9:02 AM · MediaWiki-extensions-NavigationTiming, Performance-Team
Peter added a comment to T167403: Measure time-to-logo with ResourceTiming.

I wanna move this out of potential goals, I can't see how this will work.

Dec 4 2017, 6:22 AM · Performance-Team
Peter added a comment to T176361: Run performance tests using local proxy.

@chasemp I think we need your help here and guide us in the right direction. Let me do a summary:

Dec 4 2017, 4:47 AM · Performance-Team
Peter created T181959: Blog post: Why we measure performance.
Dec 4 2017, 4:13 AM · Performance-Team

Nov 30 2017

Peter added a comment to T176361: Run performance tests using local proxy.

Cool. I was to dismiss Fargate since to be able to set connectivity with tc you need to do that with Docker networks or set the right privileges on the host machine BUT we just do it on localhost for our tests, so that should work.

Nov 30 2017, 11:10 AM · Performance-Team
Peter added a comment to T180688: Firefox 57 improvement.

I've checked now and values are better than 54 after turning of downloading of tracking protection files. I'll add that to the upstream bug and also again ask about preferred setup.

Nov 30 2017, 10:37 AM · Upstream, Performance-Team
Peter renamed T180688: Firefox 57 improvement from Firefox 57 improvement/regressions to Firefox 57 improvement.
Nov 30 2017, 10:35 AM · Upstream, Performance-Team

Nov 29 2017

Peter added a comment to T178559: Chrome 62 performance regression.

Looking at p95 surprisingly many 62 has highs when we had few 62 users:

Nov 29 2017, 8:57 AM · Performance-Team, WebPageTest
Peter added a comment to T178559: Chrome 62 performance regression.

It's not easy to see:

Nov 29 2017, 8:54 AM · Performance-Team, WebPageTest
Peter added a project to T179436: Set up measurement of page loading timings: Performance-Team.
Nov 29 2017, 8:07 AM · Performance-Team (Radar), Wikipedia-iOS-App-Backlog, iOS-app-v5.7.4-Dachshund-On-An-Elk