Lines Matching full:memory
30 to help OEMs optimize and configure Android 4.4 for low-memory devices. Several
36 <h3 id="opt-mgmt">Improved memory management</h3>
38 <li>Validated memory-saving kernel configurations: Kernel Same-page Merging
46 <li>Tuned memory use of low-RAM devices: tighter out-of-memory (OOM) adjustment
50 <h3 id="opt-mem">Reduced system memory</h3>
62 Added a new Developer Option to show memory state and application memory usage
63 ranked by how often they run and amount of memory consumed.
69 when running on low memory devices and choose to disable large-RAM features.
72 <h3 id="opt-track">Memory tracking</h3>
74 New memtrack HAL to track graphics memory allocations, additional information
84 they should turn off specific memory-intensive
85 features that work poorly on low-memory devices.</p>
92 <p>System-wide JIT memory usage is dependent on the number of applications
100 memory usage, but if set too low will send the JIT into a thrashing mode. For
101 the really low-memory devices, we recommend the JIT be disabled entirely.</p>
109 using live-wallpaper. Low-memory devices should not pre-install any live wallpapers. </p>
117 of memory (either directly or due to faulting in a new page) and the kernel
118 has used all available free memory. This requires the kernel to block the
129 few MB of memory in background reclaim. This means any process that quickly
136 of memory free.</p>
142 in the kernel (if it exists). A high value will increase the amount of memory
144 lowmemorykiller to kill earlier. A low value allows more memory to be used by
147 on screen size. 0 prevents keeping any extra memory over what the kernel keeps
155 ActivityManager. A positive value will increase the amount of memory that the
157 lowmemorykiller to kill earlier. A negative value allows more memory to be
170 memory or if more services have been added, the thresholds can be increased. </p>
172 <p>The thresholds can be reduced if too much memory is being reserved for file
179 keeping more memory in the file cache and preventing I/O thrashing, but
180 allowing fewer processes to stay in memory. A low value will keep more
181 processes in memory but may cause thrashing if set too low. Overrides the
182 default value chosen by ActivityManager based on screen size and total memory
191 fire earlier, keeping more memory in the file cache and preventing I/O
192 thrashing, but allowing fewer processes to stay in memory. A low value will
193 keep more processes in memory but may cause thrashing if set too low. Directly
195 size and total memory for the largest lowmemorykiller bucket, and scaled
203 memory that have been marked <code>MADV_MERGEABLE</code> by user-space. If two pages are
205 copy-on-write page of memory.</p>
207 <p>KSM will save memory over time on a running system, gaining memory duplication
209 measure whether the power tradeoff is worth the memory savings you get by
227 memory is mapped to what process, which processes use the most KSM memory.
228 Once you have found a chunk of memory that looks worth exploring you can use
233 <p>zRAM swap can increase the amount of memory available in the system by
234 compressing memory pages and putting them in a dynamically allocated swap area
235 of memory.</p>
237 <p>Again, since this is trading off CPU time for a small increase in memory, you
256 zramsize</code> is mandatory and indicates how much uncompressed memory you want
269 <li>By default, the Linux kernel swaps in 8 pages of memory at a time. When
271 and may help in case the device is under extreme memory pressure. To read
276 <li>The memory cgroups are automatically configured at boot time if the
278 <li>If memory cgroups are available, the ActivityManager will mark lower
279 priority threads as being more swappable than other threads. If memory is
280 needed, the Android kernel will start migrating memory pages to zRAM swap,
281 giving a higher priority to those memory pages that have been marked by
285 <h3 id="carveouts">Carveouts, Ion and Contiguous Memory Allocation (CMA)</h3>
287 <p>It is especially important on low memory devices to be mindful about
293 <p>If hardware permits discontiguous memory allocations, the ion system heap
294 allows memory allocations from system memory,
296 allocations to eliminate TLB pressure on peripherals. If memory regions must
297 be contiguous or confined to a specific address range, the contiguous memory
308 href="http://developer.android.com/training/articles/memory.html">Managing your
309 App's Memory</a> and these past blog posts on the same topic:
312 href="http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html">http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html</a></li>
314 href="http://android-developers.blogspot.com/2011/03/memory-analysis-for-android.html">http://android-developers.blogspot.com/2011/03/memory-analysis-for-android.html</a></li>
316 href="http://android-developers.blogspot.com/2009/02/track-memory-allocations.html">http://android-developers.blogspot.com/2009/02/track-memory-allocations.html</a></li>
344 user) for any reason. These all add memory load to the system. In this case
347 their pss size then is very important as part of their memory load.</p></li>
353 metric here, showing how much memory load the app is creating while in use.</p></li>
358 memory state -- normal, moderate, low, critical is based on how many of these
360 is the pss; these processes should try to get their memory footprint down as
369 releasing memory when going into the background. Excluding CACHED_EMPTY state
405 <p>Run for longer durations and track the memory of the process. Does it
