Symbian3/PDK/Source/GUID-CE308C71-D8B2-43B3-97FD-B868285ED5FB.dita
changeset 5 f345bda72bc4
child 14 578be2adaf3e
equal deleted inserted replaced
4:4816d766a08a 5:f345bda72bc4
       
     1 <?xml version="1.0" encoding="utf-8"?>
       
     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
       
     3 <!-- This component and the accompanying materials are made available under the terms of the License 
       
     4 "Eclipse Public License v1.0" which accompanies this distribution, 
       
     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
       
     6 <!-- Initial Contributors:
       
     7     Nokia Corporation - initial contribution.
       
     8 Contributors: 
       
     9 -->
       
    10 <!DOCTYPE concept
       
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
       
    12 <concept id="GUID-CE308C71-D8B2-43B3-97FD-B868285ED5FB" xml:lang="en"><title>OOM
       
    13 Monitor Priority</title><shortdesc>This section explains the OOM Monitor priority and the values that
       
    14 can be set.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
       
    15 <section id="GUID-950C05B0-1FA9-44D0-90F0-D3AB1EEF4476"><p>To release RAM
       
    16 the OOM Monitor uses priorities to determine the order of closing the applications.
       
    17 The OOM Monitor assigns priority for each application which determines the
       
    18 order (in relation to other applications) of closing the application. </p><p>A
       
    19 priority of an application is a measure of impact to the mobile device user
       
    20 in case the OOM Monitor closes that application. Thus closing a low priority
       
    21 application means that it will have a minimum impact on the user. And closing
       
    22 of high priority application will have a high impact on the user.</p><p>The
       
    23 OOM Monitor closes the lowest priority application first as this will have
       
    24 the smallest impact on the user. It will continue to close the applications
       
    25 until the amount of the free RAM is above the <keyword>GOOD_RAM_THRESHOLD</keyword> value.</p><p>If
       
    26 two or more applications have the same priority the OOM Monitor closes these
       
    27 applications based on their idle time. The application that has stayed idle
       
    28 for the longest time will be closed first.</p></section>
       
    29 <section id="GUID-0E58AC12-78BD-4FFC-906E-08EBB46CA26C"><title>Priority for
       
    30 internal application</title><p> The priority of each internal application
       
    31 can be defined in the OOM Monitor configuration file. If the priority of an
       
    32 application is not defined it will have the default priority. Default priority
       
    33 is also defined in the configuration file. </p><p>The priority of an application
       
    34 is not always constant. OOM Monitor configuration file can contain rules that
       
    35 determine how the priority is changed for an application when its idle time
       
    36 gets longer or when the foreground application is changed. For more information
       
    37 on the rules that can be set to change priorities, refer to <xref href="GUID-54D5CBD5-0A1F-4835-B5F3-492728B9F51E.dita">Rules
       
    38 to change priority dynamically</xref></p><p/></section>
       
    39 <section id="GUID-6D51C8AD-6217-4924-8E55-E5A9459F78A0"><title>Priority for
       
    40 third-party application</title><p>Third-party applications can use the following
       
    41 priorities:</p><ul>
       
    42 <li><p><codeph>Normal</codeph> (default priority)</p></li>
       
    43 <li><p><codeph>High</codeph></p></li>
       
    44 <li><p><codeph>Busy</codeph> (infinite priority)</p></li>
       
    45 </ul><p>By default the priority of a third-party application is <codeph>Normal</codeph> but
       
    46 it is possible to change the priority as required. For information on increasing
       
    47 the priority of a third-party application, see <xref href="GUID-1E4FFC56-8473-4E0A-B2E2-4E8DE8B1D00F.dita">Increasing
       
    48 the Priority of a Third-Party Application</xref></p><p>The OOM Monitor cannot
       
    49 close a foreground application. The device user can also define the <codeph>Busy</codeph> priority
       
    50 for background applications which means that those applications are never
       
    51 closed by the OOM Monitor. For information on how to change the priority of
       
    52 an application to <codeph>Busy</codeph>, refer to <xref href="GUID-8F8E3814-7ED6-4218-BEEF-741AE0E9366F.dita">Changing
       
    53 the Priority</xref>.</p></section>
       
    54 </conbody></concept>