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

Add documentation on Performance Expectations #698

Merged
merged 2 commits into from
Feb 6, 2023
Merged

Conversation

joehoyle
Copy link
Member

No description provided.

@joehoyle joehoyle requested a review from rmccue October 25, 2022 13:12
docs/performance-expectations.md Outdated Show resolved Hide resolved
docs/performance-expectations.md Outdated Show resolved Hide resolved
docs/performance-expectations.md Outdated Show resolved Hide resolved
docs/performance-expectations.md Outdated Show resolved Hide resolved
Co-authored-by: Ryan McCue <me@ryanmccue.info>
@joehoyle joehoyle requested a review from rmccue October 26, 2022 08:04
@johnbillion
Copy link
Member

This has likely been discussed elsewhere prior to writing this page, but what do we expect a client to do with this information? The CDN and origin cache response times are effectively fixed, as they rely on known infrastructure and any variation indicates a platform problem that should be escalated, but the origin response time for uncached responses will vary greatly.

The information I want to get from this page is, given my website is responding in X milliseconds, is that within an expected range or is that a problem that needs to be investigated by the delivery team or the cloud team?

The 150ms response time for a base WordPress site is not going to happen for many sites, so perhaps a range of expected response times could help set expectations.

@joehoyle
Copy link
Member Author

joehoyle commented Feb 6, 2023

@johnbillion the intention is to provide baseline metrics so people deploying on Altis Cloud can understand the delta between their "site additions" and what a blank slate vanilla WordPress is likely to perform at. It also provides a baseline so they understand what minimum numbers are viable (if for example, they expect to optimize their code to get things responding in 50ms).

I think this doc could be fleshed out in the future though, with some more example setups. I don't think we should be blocking merging it now though.

@joehoyle joehoyle merged commit 15b21b6 into master Feb 6, 2023
@joehoyle joehoyle deleted the perf-expectations branch February 6, 2023 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants