-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Comments
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
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. |
Thank you! |
Switch to justified latency thresholds (fixes #609)
#608
I didn't care about it, but the 400ms threshold seems reasonable.
The text was updated successfully, but these errors were encountered: