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.

Sign up for GitHub

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
Merged

Expand discussion about timing vs external pressure #252

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
deab7a5
Expand discussion about timing vs external pressure
kenchris Mar 6, 2024
6c96569
Fixed to the text
kenchris Mar 6, 2024
2de0749
Fix nits
kenchris Mar 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,9 +66,13 @@ 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.

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.
If the use-cases is to adapt the user experience to the user system at hand, measuring the time to achieve
certain tasks is an option, but web apps can also suffer from unusual high CPU pressure beyond the app's control.

As an example, external pressure can result in a degraded interactivity experience by making certain tasks take longer than usual. e.g,
increasing the time it takes for complex components to render and thus increase the response time to interactions,
resulting in a degraded user experience. This example can be mitigated by rendering simpler content or skeleton content
in cases where the CPU pressure is high.

Specifically, v1 aims to facilitate the following adaptation decisions for these use cases:

Expand Down
Loading