leichunfeng / leichunfeng/Image-Decompression-Benchmark
大图解码
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 23
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
大神，我有个问题想请教你，我们项目中，cell中所用的图片比较大52083733，解码图片显示的话，会造成内存暴增，不解码图片显示的话，会有些卡顿，苹果官网有一个渐进式解码的示例代码（sdweb里也有一个类似的解码），所用的图片是703310110，解码时的内存大概在27m左右；但是当我将这个demo运用在我的项目中的时候，解码时的内存大概在90左右，反而增大了很多！这个有什么比较好一点的方法来获取这个解码与卡顿之间的平衡！大神能否指点下！
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 comparing the project's large-image decoding behavior with Apple's progressive decoding example and the similar SDWebImage implementation mentioned in the issue. Measure memory usage and scrolling responsiveness for the 5208×3733 image, then identify an approach that balances decoding memory against cell display smoothness.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c
- Domain
- mobile-dev, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100