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

Expand discussion about timing vs external pressure #252

Merged
merged 3 commits into from
Mar 6, 2024

Conversation

kenchris
Copy link
Contributor

@kenchris kenchris commented Mar 6, 2024

No description provided.

@kenchris kenchris requested review from anssiko and arskama March 6, 2024 11:04
README.md Outdated
Web apps can also suffer from high CPU pressure beyond the apps control, which can result in a degraded interactivity experience. This can impact the time it takes
for complex components to render and thus increase the response time to interactions, resulting in a degraded user experience. This can be mitigated by rendering
simpler content or skeleton content in cases where the CPU pressure is high.
It the use-cases is to adopt the user experience to the user system at hand, measuring the time to archieve
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If

README.md Outdated
@@ -66,10 +66,10 @@ These popular [real-time applications](https://en.wikipedia.org/wiki/Real-time_c
are classified as _soft_. That is, the quality of service degrades if the system is exercised beyond certain states, but does not lead to a total system failure.
These _soft_ real-time applications greatly benefit from being able to adapt their workloads based on CPU consumption/pressure.

It the use-cases is to adopt the user experience to the user system at hand, measuring the time to archieve
certain tasks is an option, but web apps can also suffer from unusual high CPU pressure beyond the apps control.
If the use-cases is to adopt the user experience to the user system at hand, measuring the time to archieve
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"are to adapt"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

README.md Outdated
@@ -66,10 +66,10 @@ These popular [real-time applications](https://en.wikipedia.org/wiki/Real-time_c
are classified as _soft_. That is, the quality of service degrades if the system is exercised beyond certain states, but does not lead to a total system failure.
These _soft_ real-time applications greatly benefit from being able to adapt their workloads based on CPU consumption/pressure.

It the use-cases is to adopt the user experience to the user system at hand, measuring the time to archieve
certain tasks is an option, but web apps can also suffer from unusual high CPU pressure beyond the apps control.
If the use-cases is to adopt the user experience to the user system at hand, measuring the time to archieve
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

time to achieve

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

Copy link
Contributor

@arskama arskama left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kenchris kenchris merged commit d5ece7c into w3c:main Mar 6, 2024
2 checks passed
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.

2 participants