Avoiding Allocations in onDraw() (100 Days of Google Dev)
15 919
34
Google Developers2.41 млн
Следующее
23.06.15 – 17 2972:59Популярные
11 дней – 55 7406:59
12 дней – 41 1303:44Опубликовано 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
Свежие видео
5 дней – 1 0480:24
7 дней – 7 4550:24
8 дней – 294 1158:36
10 дней – 8 8060:11
12 дней – 1 01429:31
13 дней – 15 4192:39Случайные видео
135 дней – 21 5492:11
01.05.23 – 4 566 20614:48
13.04.23 – 1 5937:24
02.07.22 – 3 453 92714:55
08.12.21 – 23 56029:01
16.04.12 – 48 8283:53
1 день – 1760:11
6 дней – 3058:04
6 дней – 246 07910:02
7 дней – 116 17714:24
8 дней – 24 14018:23
8 дней – 1 5444:14
11 дней – 14 8686:41
2 дня – 97 75611:48