Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write content: Chapter 7: Performance #171

Closed
3 tasks done
rviscomi opened this issue Sep 25, 2019 · 12 comments · Fixed by #249
Closed
3 tasks done

Write content: Chapter 7: Performance #171

rviscomi opened this issue Sep 25, 2019 · 12 comments · Fixed by #249
Assignees
Labels
ASAP This issue is blocking progress writing Related to wording and content

Comments

@rviscomi
Copy link
Member

rviscomi commented Sep 25, 2019

Part Chapter Authors Reviewers Analysts Metrics Analysis
II. User Experience 7. Performance @rviscomi @JMPerez @OBTo @sergeychernyshev @zeman @rviscomi @raghuramakrishnan71 #9 #88

Due by: October 7

Refer to the Authors' Guide for writing advice.

@rviscomi rviscomi added the writing Related to wording and content label Sep 25, 2019
@rviscomi rviscomi added this to the Content written milestone Sep 25, 2019
@rviscomi
Copy link
Member Author

@zeman I've sketched out a very rough outline of the chapter here. How does that look to you?

Any questions/concerns about the lab data in the results sheet?

@zeman
Copy link

zeman commented Sep 29, 2019

@rviscomi the outline looks promising. Unfortunately this is really poor timing for me as I'm away on holiday till the 14th. If the deadline is the 7th then I'm afraid I can't take on the writing. I'm still happy to be a reviewer when I'm back.

@rviscomi
Copy link
Member Author

rviscomi commented Oct 2, 2019

Ahh ok thanks for the update @zeman. We can stall the release of this chapter, or at least the Lab section, until you're available. I'd still love to have your contributions. I'll check in with you again after you're back from holiday.

@rviscomi rviscomi added the ASAP This issue is blocking progress label Oct 4, 2019
@rviscomi
Copy link
Member Author

rviscomi commented Oct 9, 2019

@JMPerez @OBTo @sergeychernyshev please have a look at this draft of the field performance section. When @zeman's lab performance section is complete we can work on a unified intro/conclusion.

@foxdavidj
Copy link
Contributor

@rviscomi I'm planning on reviewing this over the weekend. I'll let you know when I've finished :)

@sergeychernyshev
Copy link

Same here.

@rviscomi
Copy link
Member Author

Thanks @OBTo and @sergeychernyshev!

@sergeychernyshev
Copy link

Left a few comments in the doc.

@rviscomi
Copy link
Member Author

I heard from Mark via email that he's unable to commit to writing the Lab section. Given the state of the deadline let's stretch the Field section to the entire chapter. I'll work on rewriting it to fit the new context.

@rviscomi
Copy link
Member Author

rviscomi commented Oct 18, 2019

@logicalphase
Copy link
Contributor

logicalphase commented Oct 19, 2019 via email

This was referenced Oct 22, 2019
@rviscomi
Copy link
Member Author

I'll be rewriting a bit of our FCP and FID analysis to include new and unreleased (shhhh!) PSI thresholds:

Metric Fast Slow Moderate
FCP p75 at 1000ms p25 at 3000ms Everything else
FID p95 at 100ms p05 at 300ms Everything else

Notable changes:

  • rename "average" to "moderate"
  • lower barrier to fast FCP from p90 to p75
  • increase barrier to fast FID from 50ms to 100ms

I plan to include the old results for comparison and also for a more accurate representation of "the state of web performance as of July 2019". Having these new thresholds in the Almanac will go a long way to making these results more relevant at CDS.

cc @igrigorik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ASAP This issue is blocking progress writing Related to wording and content
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants