Describe Memory Management in Smart Devices Coursework (Coursework Sample)

Memory management in smart devices
Name
Course
Date
MEMORY MANAGEMENT IN SMART DEVICES
A smart device refers to an electronic gadget, which can share, connect and to interact with those who use it as well as other smart devices. Memory management is the process of coordinating and controlling memory of a device by conveying some portions known as to a variety of running programs. Background application management is smart devices especially smart phones maintains background applications in memory that are inactive and also allows for fast reactivation of these applications so that they can be used or accesses later.
By the help of such an application in the storage of data, it is possible for the battery to last longer because the energy used in reloading applications is reduced. Recent static memory management policies put a specific number of stored background applications without taking into consideration their use patterns which have the potential to misuse memory space for storing applications that do not require to be used again. Such kind of inefficiency in the storage of data has grown as the smart devices are also increasing. This has negatively resulted to the throwing out of some memory pages which are valuable so as to stick to the fixed and stipulated number of background applications in a given cache.
Random Access Memory (RAM) is one of the crucial parts of the smart devices together with dispensation cores and the graphics that are dedicated (Schiesser, 2012). When looking at a smart device’s RAM capacity, it is important to consider one with more capacity because of the larger space, the more the content that can be stored in the device and the more it gives quick access to other systems as well as enabling quick storage. When managing memory one should not be bothered by the fact that larger storage uses more power because when this is done it is only a small part of the system's power that is used up.
Memory management of IOS
Smart devices have a memory that is limited and for the applications of these devices to operate effectively there is a need to divide the limited space available in memory among all the apps. There are two ways in which memory management can be achieved. One of them is the Manual-Retain-Release method whereby memory is managed exclusively by tracking the objects that an individual owns by use of a method referred to as reference counting.
The second method through which memory management in smart devices can be achieved is by use of Automatic Reference Counting (ARC). It uses reference counting too, but the unique part of it is that it does it routinely by way of putting up the required memory management method. Some critical rules are followed in Manual-Retain –Release memory management method. These rules are that; you get the possession of what you create; ownership can be passed to you if you retain an object, when you no longer need an object you have to hand over the ownership of that particular object and finally you are not supposed to hand over ownership of an object that you do not own (Premaratne, 2013).
In creating an object ‘alloc’ method is used by rule one which states that we are in possession of the string that is returned by alloc.
Following the above rules, any object that gets created by use of a method with a name beginning with ‘copy,' ‘alloc, ‘new' in the object it should be passed on to another person when it is no longer needed. To achieve this transfer of an object, one should send to the object to be transferred a message to release or a message to auto release. When we are through with an object, we carry out the transfer of ownership by way of sending a message to the object. The process of transferring the ownership of an object is what is referred to as releasing. It is always necessary to pass ownership of an object before one’s reference to such an object is lost. If one wants to pass ownership of an object using the release method, then it is necessary that the string is detached before it is returned and such a method has a tendency to return an object that is invalid.
The transfer of ownership of someone’s objects can be executed by carrying out a method referred to as dealloc. The dealloc method to be implemented is defined by the NSO object class. This method happens obviously when any particular object lacks an owner. The function of the dealloc method is to set free the memory of an object as well as to get rid of any resources that are held by the object taking into account even the possession of an object’s illustration variables.
In using the Manual- Release- Retain techniques, and it happens that some of your classes have some properties that are considered objects, it is your duty to ensure that in the setting of an object the value that it has is not removed while still in use. To achieve this, one has to declare that you are the owner of the object and you have the right to transfer the ownership of the object when you have finished using it.Release and retain method to carry out management of memory by use of a model known as reference counting.
Memory management of Android
The Android Runtime (ART) together with Dalvik virtual machines make use of memory mapping and paging to carry out memory management. This implies that any kind of memory that an application molds by, for example, touching of mapped pages and the allocation of latest objects remains part of the random access memory and cannot be erased. The only way in which memory can be released from such an application is by first of all releasing the references of the object held by the application and hence availing such kind of memory to the recycle bin. That is to say, that files that are mapped without modification, for example, a code face the risk of being erased from the RAM if the system finds it necessary to use the memory somewhere else.
A memory that is in a managed environment, for example, the Android Runtime can keep track of each and every memory that is allocated. When it identifies that a certain piece of memory is not by the different programs, it carries out a process that releases it back to the pile, this is done without the help of a programmer. Garbage collection is the means by which unused memory is reclaimed in an environment where memory is managed. The goals of garbage collection are to: repossess resources use by objects and to search objects of data in a program that stand no chance of being accessed in future.
The memory heap of Andr...