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

Reconsider color of latency value #609

Closed
hatoo opened this issue Nov 23, 2024 · 2 comments
Closed

Reconsider color of latency value #609

hatoo opened this issue Nov 23, 2024 · 2 comments

Comments

@hatoo
Copy link
Owner

hatoo commented Nov 23, 2024

#608

I didn't care about it, but the 400ms threshold seems reasonable.

@AMDmi3
Copy link
Contributor

AMDmi3 commented Nov 23, 2024

400ms for green/yellow, or yellow/red? And which would be another threshold?

So far I've found a relevant SO thread, another one, and the above mentioned article.

Values mentioned there include

  • 400ms Doherty threshold
  • 100ms with references to 30 year old studies on human-computer interaction, many mentions as commonly used target values and a claim from a neuroscientist

    the average amount of time for an individuals minimum reaction speed or input-response detection is ~200ms. to be certain there is no detectable difference, this threshold could be lowered to around 100ms

  • 50ms from Google study, which measure search requests decline based on artificially introduced delay (where 50ms has no effect, and 100ms leads to measurable 0.2% decline, however it doesn't mentione which their base response times are), and a mention of Amazon study claiming there's 1% sales drop for each 100ms (I didn't see the study itself)
  • 2 sec from Akamai, link to study is broken, and the guess is that it refers to untolerable delay as opposed to unperceivable delay

This gives me a picture where most agree that 100ms may be considered as "instant", and that can be a reasonable choice for green/yellow threshold. Longer response times gradually affect UX, and it's hard to pick a fixed value there, but 400ms is at least based on one respected study, seems to be value which doesn't cause much discomfort to me personally, and provides meaningful 4x corridor of tolerable values above the desired one. There could be another threshold around 1-2 seconds which denotes performance problems and undeniable discomfort for users, but adding it to oha would probably compilcate things.

Summarizing, IMO 100ms and 400ms are reasonable generic choice for use in oha.

@hatoo
Copy link
Owner Author

hatoo commented Nov 24, 2024

Thank you!
I agree with the 100ms and 400ms threshold.
Would you mind creating PR? (Just change the threshold and add a comment about justification (link to this issue is enough))

@hatoo hatoo closed this as completed in 14a95b6 Nov 25, 2024
hatoo added a commit that referenced this issue Nov 25, 2024
Switch to justified latency thresholds (fixes #609)
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

No branches or pull requests

2 participants