Avoiding Allocations in onDraw() (100 Days of Google Dev)
15 911
34
Google Developers2.39 млн
Следующее
23.06.15 – 17 2892:59Популярные
36 дней – 4 27512:09
76 дней – 4 5800:31Опубликовано 23 июня 2015, 16:52
One of the common problems with memory issues in an Android Application has to do with Memory Churn; that is, allocating a bunch of objects, in a short period of time. This issue can kick off a load of Garbage Collection events, which eats into your potential framerate.
In this video, Ian Ni-Lewis takes a deep loop at one of the most common causes of memory-churn : Doing allocations inside of an onDraw() function. But the main question is, why would an allocation in onDraw() be worse than an allocation anywhere else?
Watch more Android Performance Patterns here: goo.gl/4ZJkY1
Join the G+ Community here : goo.gl/g7mxmI
100 Days of Google Dev / 100 developer videos over 100 days / #GoogleDev100
Subscribe to the Google Developers channel here: goo.gl/mQyv5L
In this video, Ian Ni-Lewis takes a deep loop at one of the most common causes of memory-churn : Doing allocations inside of an onDraw() function. But the main question is, why would an allocation in onDraw() be worse than an allocation anywhere else?
Watch more Android Performance Patterns here: goo.gl/4ZJkY1
Join the G+ Community here : goo.gl/g7mxmI
100 Days of Google Dev / 100 developer videos over 100 days / #GoogleDev100
Subscribe to the Google Developers channel here: goo.gl/mQyv5L
Свежие видео
8 дней – 1 8540:33
8 дней – 7 4147:13
16 дней – 9911:00
20 дней – 5 4083:04
Случайные видео
23 дня – 28 6802:16
340 дней – 81 98813:27
353 дня – 18 48431:54
17.06.23 – 18 5080:31
12.07.20 – 65 47410:15
15.10.18 – 34 88926:00
21 час – 2 7350:28
7 часов – 1484:51
5 дней – 5960:30
6 дней – 7171:25
7 дней – 1 5770:38
9 дней – 820:38
17 часов – 9771:00