markzhai / markzhai/AndroidPerformanceMonitor
默认判定卡顿的阀值为什么是500ms而不是16ms呢？
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 6.7k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
看了原理：在主线程处理消息的前后记录时间，算出差值，与阀值进行比较从而判断卡顿
疑问：主线程处理消息时间差值为什么能判断卡顿呢？如果我的理解没错的话，主线程16ms一次接收到垂直信号，然后进行下一帧画面的绘制。那么这个绘制的消息的处理时间不应该不超过16ms吗？（不影响到下一次接收信号）
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the implementation that records main-thread message timing and compares the difference with the 500ms threshold. Trace the Android frame-scheduling assumptions described in the issue; done means documenting why this threshold is used and how it relates to the 16ms frame interval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100