Here’s a common problem that I’m sure you’ve run into: It’s time to load a new bitmap for your apps’ social media stream, or whatever, but you're out of memory. You can’t load in the new bitmap, without first destroying one of the existing bitmaps already in memory. But, which one should you get rid of?
Well, as Colt McAnlis, points out, you could learn 60 years of history of Cache replacement algorithms; that’ll help.. or, you could just use Android’s LRUCache container.
This container keeps a list of objects, and ranks them based upon how many times they’ve been accessed. When it’s time to evict one of them (to make space for a new object) the LRUCache already knows which ones to get rid of. All done without you having to worry about any of it.
100 Days of Google Dev / 100 developer videos over 100 days / #GoogleDev100
Watch more Android Performance Patterns here:
Join the G+ Community here :
Subscribe to the Google Developers channel here:
Mdp.lt is not the owner of this text/video/image/photo content, the real source of content is Youtube.com and user declared in this page publication as Youtube.com user,
if you have any question about video removal, what was shared by open community, please contact Youtube.com directly or report bad/not working video links directly to video owner on Youtube.com. Removed video from Youtube.com will also be removed from here.
#shorts SnapMaker J1 IDEX 3d printer creation satisfaction
Dirt bike and quadbike event at Crazy Ferma 2022-02-06