Glide: Bitmap prepareToDraw() performance optimization
I noticed that master is using Bitmap.prepareToDraw(). Can you explain how this is being used, and a workaround for using it in an older version? I'm profiling my app right now and noticing in the GPU profiler consistently high sync/upload segments. The Android docs suggest using Bitmap.prepareToDraw() to help mitigate the issue. Specifically I'm looking to improve the scroll performance of my app.
christopherperry
>All comments
You can probably add a call to prepareToDraw by subclassing or wrapping the existing Bitmap decoder in v3.
It basically just starts uploading the texture a little bit earlier. If you're seeing consistently high upload segments you're probably equally or better served by decreasing the size of the bitmaps you're loading, especially if you're loading a lot at once (in a list or a grid).
sjudd
on 20 May 2017
Related issues
ersen-osman
路
3Comments
Morteza-Rastgoo
路
3Comments
MrFuFuFu
路
3Comments
Tryking
路
3Comments
sergeyfitis
路
3Comments
Most helpful comment
You can probably add a call to prepareToDraw by subclassing or wrapping the existing Bitmap decoder in v3.
It basically just starts uploading the texture a little bit earlier. If you're seeing consistently high upload segments you're probably equally or better served by decreasing the size of the bitmaps you're loading, especially if you're loading a lot at once (in a list or a grid).