search

w3c / longtasks

Long Task API
https://w3c.github.io/longtasks/
Other
246 stars 32 forks source link

Provide explanation for the 50ms threshold #59

Closed marcelduran closed 5 years ago

marcelduran commented 5 years ago

Throughout the specs, it's not clear why 50ms was chosen as the long task duration threshold. Under Security and privacy considerations, it just states such threshold also provides adequate protection against security attacks.

npm1 commented 5 years ago

I see the spec mentions:

"RAIL performance model suggests that applications should respond in under 100ms to user input; for touch move and scrolling in under 16ms. Our goal with this API is to surface notifications about tasks that may prevent the application from hitting these targets."

But maybe the explanation of why 50ms should be made more explicit. @spanicker would you like to elaborate on this or should I do it?

marcelduran commented 5 years ago

Measure Performance with the RAIL Model has more info on the 50ms rationale too.