WO2019137252A1

WO2019137252A1 - Memory processing method, electronic device, and computer-readable storage medium

Info

Publication number: WO2019137252A1
Application number: PCT/CN2018/125225
Authority: WO
Inventors: 陈岩
Original assignee: Oppo广东移动通信有限公司
Priority date: 2018-01-10
Filing date: 2018-12-29
Publication date: 2019-07-18
Also published as: CN110018902A; CN110018902B

Abstract

A memory processing method, comprising: acquiring a reclaimable memory page occupied by a pending application; acquiring a dependency ratio where the pending application is depended on by a foreground application; determining the reclaiming number of the reclaimable memory pages according to the reclaimable memory pages and the dependency ratio; and selecting the reclaiming number of memory pages from the reclaimable memory pages for reclaiming.

Description

Memory processing method, electronic device, computer readable storage medium

Cross-reference to related applications

This application claims priority to Chinese Patent Application No. 201810023232.7 filed on Jan. 10, 2018, entitled "Memory Processing Method and Apparatus, Electronic Apparatus, Computer Readable Storage Medium", the entire contents of which is hereby incorporated by reference. This is incorporated herein by reference.

Technical field

The present application relates to the field of data processing, and in particular, to a memory processing method, an electronic device, and a computer readable storage medium.

Background technique

Applications installed on electronic devices require a certain amount of memory when they are running. Memory is the primary storage medium for data that is applied during the run. Due to the limited memory capacity on the electronic device, when the background application occupies too much memory, it will affect the operating efficiency of the foreground application. Therefore, the memory needs to be recycled to improve the operating efficiency of the foreground application.

The traditional approach to memory processing is to reclaim all of the memory occupied by a single application running in the background. However, completely reclaiming the memory used by a single application will cause the application to reload almost all of the reclaimed memory during the next startup and execution, resulting in a significantly slower running of the application that is reclaiming memory.

Summary of the invention

An in-memory processing method, an electronic device, and a non-transitory computer readable storage medium are provided in accordance with various embodiments of the present application.

An in-memory processing method includes: acquiring a reclaimable memory page occupied by an application to be processed; acquiring a dependency ratio of the to-be-processed application to be relied upon by the foreground application; determining, according to the reclaimable memory page and the dependency ratio, Recycling the number of reclaimable memory pages; selecting the reclaimed memory page from the recyclable memory page for recycling.

An electronic device comprising a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, causing the processor to execute the memory processing method described in the embodiments of the present application A step of.

A computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the steps of the memory processing method described in various embodiments of the present application.

In the embodiment of the present application, the reclaimable memory page occupied by the to-be-processed application and the dependency ratio of the to-be-processed application depended on by the foreground application are obtained, and the reclaimed quantity is determined according to the dependency ratio and the reclaimable memory page, and the reclaimed memory page is selected from the reclaimable memory page. Recycling the number of memory pages for recycling. Since the recovered objects are recyclable memory pages, and not all recyclable memory pages are reclaimed, the amount of reclaimed is determined according to the proportion of dependencies that the application to be processed is dependent on by the foreground application. Reduces the operational impact of the application to be processed, and the reclaimed memory pages can be released for use by other applications, which improves the overall processing efficiency of the system and ensures that the negative impact on each application is minimized when the overall system memory becomes large. , maintaining a balance between the recycling and operation of the application memory to be processed.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present application, and other drawings can be obtained according to the drawings without any creative work for those skilled in the art.

FIG. 1 is a schematic diagram showing the internal structure of an electronic device in an embodiment.

2 is a partial block diagram of a system in an electronic device in an embodiment.

3 is a flow chart of a memory processing method in one embodiment.

4A is a schematic diagram of a recovery ratio curve for an unrelated application in one embodiment.

Figure 4B is a schematic diagram of the recovery ratio curve for a linear application in one embodiment.

4C is a schematic diagram of a recovery ratio curve for a non-linear application in one embodiment.

Figure 5 is a flow chart of a memory processing method in another embodiment.

Figure 6 is a block diagram showing the structure of an internal memory processing device in an embodiment.

Figure 7 is a block diagram showing a portion of the structure of a handset in an embodiment.

Detailed ways

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

In one embodiment, as shown in FIG. 1, an internal structure diagram of an electronic device is provided. The electronic device includes a processor, memory, and display screen connected by a system bus. The processor is used to provide computing and control capabilities to support the operation of the entire electronic device. The memory is used to store data, programs, and/or instruction codes, etc., and the memory stores at least one computer program, which can be executed by the processor to implement the memory processing method applicable to the electronic device provided in the embodiments of the present application. The memory may include a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (ROM), or a random storage memory (Random-Access-Memory, RAM). For example, in one embodiment, the memory includes a non-volatile storage medium and an internal memory. Non-volatile storage media stores operating systems, databases, and computer programs. The database stores data related to implementing an in-memory processing method provided by the above various embodiments, such as storing a name of each application and a memory page allocated for each application. The computer program can be executed by a processor for implementing an in-memory processing method provided by various embodiments of the present application. The internal memory provides a cached operating environment for operating systems, databases, and computer programs in non-volatile storage media. The display screen can be a touch screen, such as a capacitive screen or an electronic screen, for displaying interface display information of the foreground application, and can also be used for detecting a touch operation acting on the display screen, and generating corresponding instructions, such as performing front and back applications. Switch instructions, etc.

A person skilled in the art can understand that the structure shown in FIG. 1 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the electronic device to which the solution of the present application is applied. The specific electronic device may be It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements. For example, the electronic device further includes a network interface connected through a system bus, and the network interface may be an Ethernet card or a wireless network card, etc., for communicating with an external electronic device, for example, for communicating with a server. For example, there is no display connected through the system bus on the electronic device, or an external display device can be connected.

In one embodiment, as shown in FIG. 2, a partial architectural diagram of an electronic device is provided. The architecture of the electronic device includes a JAVA spatial layer 210, a local framework layer 220, and a kernel space layer 230. The JAVA spatial layer 210 may include a freeze management application 212. The electronic device may implement a freeze policy for each application through the freeze management application 212, and perform freezing and thawing management operations on the related applications of the background power consumption. The resource priority and restriction management module 222 and the platform freeze management module 224 are included in the local framework layer 220. The electronic device can maintain different applications in different priorities and different resource organizations through the resource priority and limit management module 222, and adjust the resource group of the application according to the requirements of the upper layer to achieve optimized performance and save power. effect. The electronic device can allocate the tasks that can be frozen in the background to the frozen layer corresponding to the preset different levels according to the length of the entering freeze time through the platform freeze management module 224. Optionally, the frozen layer can include three, respectively: the CPU Limit sleep mode, CPU freeze sleep mode, process deep freeze mode. The CPU restricts the sleep mode to limit the CPU resources occupied by the related processes, so that the related processes occupy less CPU resources, and the free CPU resources are tilted to other unfrozen processes, thereby limiting the occupation of CPU resources. It also limits the occupation of network resources and I/O interface resources by the process; CPU freeze sleep mode means that the related process is prohibited from using the CPU, but the memory usage is reserved. When the CPU resources are forbidden, the corresponding network resources and I The /O interface resource is also forbidden; the process deep freeze mode means that in addition to prohibiting the use of CPU resources, the memory resources occupied by the related processes are further recovered, and the recovered memory can be used by other processes. The kernel space layer 230 includes a UID management module 231, a Cgroup module 232, a Binder management module 233, a process memory recovery module 234, and a freeze timeout exit module 235. The UID management module 231 is configured to implement an application-based User Identifier (UID) to manage resources of a third-party application or freeze. Compared with the Process Identifier (PID) for process management and control, it is easier to uniformly manage the resources of a user's application through UID. The Cgroup module 232 is used to provide a complete set of Central Processing Unit (CPU), CPUSET, memory, input/output (I/O), and Net related resource restriction mechanisms. The Binder management module 233 is used to implement the priority control of the background binder communication. The interface module of the local framework layer 220 includes a binder interface developed to the upper layer, and the upper layer framework or application sends a resource restriction or frozen instruction to the resource priority and restriction management module 222 and the platform freeze management module 224 through the provided binder interface. . The process memory recovery module 234 is configured to implement the process deep freeze mode, so that when a third-party application is in a frozen state for a long time, the file area of the process is mainly released, thereby saving the memory module and speeding up the application next time. The speed at startup. The freeze timeout exit module 235 is configured to resolve an exception generated by the freeze timeout scenario. Through the above architecture, the memory processing method in various embodiments of the present application can be implemented.

In an embodiment, as shown in FIG. 3, an in-memory processing method is provided. This embodiment is applied to the electronic device shown in FIG. 1 as an example for description. The method includes:

In operation 302, a reclaimable memory page occupied by the application to be processed is obtained.

The pending application indicates that an application that needs to recycle memory is needed. The memory (also known as random access memory, RAM) indicates the memory used when running the program (that is, running memory). It can only temporarily store data for exchanging cache data with the CPU, but the memory itself cannot be used. Store data for a long time. Typically, the pending application is a background application. The background app is an app that runs in the background. Correspondingly, the application running in the foreground is the foreground application. The operation of an application (APP) is usually reflected by the operation of multiple related processes. A process is a running activity of a program on a computer on a data set. It is the basic unit for resource allocation and scheduling, and is the basis of the operating system structure. The process involved in the foreground application runtime is the foreground process, and the process involved in the background application runtime is the background process.

The application needs to occupy memory space in the running state to store data during the running process. The memory space occupied by different applications in different running states may not be the same. The memory page is the unit that the operating system manages the memory. The memory size of the memory page set by different electronic devices is not necessarily the same. For example, the memory space in the electronic device is divided into 100000 memory pages, and the memory page occupied by the to-be-processed application is the memory page 100 to the memory page 200, and the memory page 130 to the memory page 200 are recyclable memory pages.

In one embodiment, the electronic device may pre-record all memory pages occupied by the application to be processed and obtain retrievable memory pages from the all memory pages. Recyclable memory pages represent memory pages that can be recycled and that have no impact on the operation of the application and other applications after they are recycled.

In an embodiment, the electronic device can record, among the memory pages, which memory pages are recyclable memory pages, which memory pages are non-recyclable memory pages, and obtain recyclable memory pages occupied by the to-be-processed application according to the record information. .

Operation 304: Obtain a proportion of dependencies that the to-be-processed application is dependent on by the foreground application.

Wherein, the dependency representation indicates that an application needs to utilize data of another application or applications to smoothly implement the relationship of execution of the one application. There are two applications of dependencies, namely the dependent application and the dependent application. Since the operation of an application is usually manifested by the operation of multiple related processes, the dependencies between applications also appear as dependencies between processes. For example, a certain process a in the application A depends on a certain process b in the application B, that is, the process b is dependent on the process a, and the process a needs to utilize the data of the process b to implement the execution of the process a, and also illustrates the application. A depends on application B, or application B is dependent on application A. Application A needs to utilize the data of application B to implement the execution of application A. At this time, application A is the dependent application. It can be understood that the dependent application may also be the first application, and the second application may be the background application. The electronic device can detect from the background application collection to query whether there is a background application that is dependent on the foreground application.

The dependency ratio reflects the degree of dependency of the application to which the dependent application is dependent. The greater the degree of dependency, the greater the dependency ratio. In one embodiment, the electronic device can record the proportion of each application's dependence on other applications and read the proportion of dependencies that the pending application is applied by the foreground among the many dependent ratios recorded.

In one embodiment, the dependency ratio is zero when the pending application is not dependent on the foreground application.

Operation 306, determining the amount of recycling of the recyclable memory page based on the reclaimable memory page and the dependency ratio.

The amount of recycling is the amount of recycling to the memory page, which is an integer. The number of different dependencies and the total number of different recyclable memory pages are different depending on the number of recycles. This total represents the total number of all recyclable memory pages. The electronic device may preset a correspondence between different total numbers under different dependency ratios and the number of recyclings, and according to the corresponding relationship, the corresponding recycling quantity may be determined. Among them, the amount of recycling is positively correlated with the total number of recyclable memory pages, and negatively correlated with the proportion of dependencies. The larger the total number of recyclable memory pages, and/or the smaller the dependency ratio, the larger the corresponding recovery amount.

In one embodiment, the recycling ratio of the recyclable memory pages may be determined according to the dependency ratio, and the number of reclaimed memory pages may be determined according to the recycling ratio and the total number of recyclable memory pages. Among them, the recycling ratio represents the proportion of the recycling of the memory to be recycled, and the recycling ratio is used to guide the recovery of the recyclable memory. For example, the recycling ratio is 50%, which means that 50% of the occupied memory can be recovered. There is a negative correlation between the recovery ratio and the proportion of dependence. The larger the dependency ratio, the smaller the recovery ratio. The correspondence between the different proportions of the application and the different recycling ratios can be established, and the corresponding recycling ratio is obtained according to the corresponding relationship.

The amount of recycling can be the product of the total number of recyclable memory pages and the determined recycling ratio. When the product is not an integer, an integer approximating the product may be selected. For example, the nearest integer may be determined as a number of rounds according to rounding, or the corresponding integer may be determined according to a truncation method or a carry method. As the amount of recycling.

The example of determining the recoverable quantity by rounding is taken as an example. For example, when there are 100 pages of recyclable memory pages, when the dependency ratio is 20%, if the proportion of the hand protection determined according to the dependency ratio is 30.5%, the product obtained is 30.5, and the number of recovery is determined to be 31, if corresponding When the recovery ratio is 21.2%, it is determined that the recovery amount is 21.

Operation 308, select a reclaimed number of memory pages from the reclaimable memory page for recycling.

The electronic device may select, according to the determined quantity of recycling, the reclaimed memory page from the recyclable memory page occupied by the to-be-processed application to reclaim the reclaimed memory page for the foreground application or other The application is used to improve the overall processing efficiency of the system. The selected reclaimable memory page is a memory page whose stored data is not dependent on the foreground application. Optionally, the electronic device may recover the memory page from the reclaimable memory page according to the recovery ratio by using the process memory recovery module 234, so that after the memory page is reclaimed, the impact on the to-be-processed application is also small.

For example, if the recycling ratio is 30% and the recyclable memory page has 100 pages, then 30 pages of memory pages are reclaimed from the 100-page recyclable memory page, that is, 30 pages of recyclable memory pages are released, making the electronic The device's free memory pages are increased by 30 pages for use by foreground applications or other back-end applications.

The memory processing method described above obtains the reclaimed memory page occupied by the to-be-processed application and the dependency ratio of the to-be-processed application that is dependent on the foreground application, and then determines the amount of recycling according to the dependency ratio and the reclaimable memory page, and recovers the memory page from the reclaimable memory page. Select a reclaimed number of memory pages for recycling. Since the reclaimed objects are recyclable memory pages, and not all recyclable memory pages are reclaimed, the reclaimed quantity is determined according to the proportion of dependencies that the pending application is dependent on by the foreground application. While reducing the impact of the memory occupied by the pending application on the foreground application, it also reduces the operational impact of the application to be processed, and the reclaimed memory page can be released for use by other applications, thereby improving the overall processing efficiency of the system. Recycling by selecting the determined number of memory pages from the reclaimable memory page ensures that the negative impact on each application is minimized in the case where the entire system memory becomes large, and the recovery and operation of the application memory to be processed is maintained. The balance between.

In one embodiment, operation 304 includes detecting whether data stored in each recyclable memory page is dependent on the foreground application; determining, based on the detection result, a dependency ratio of the application to be processed that is dependent on the foreground application.

The detection results include that the memory page is not dependent on the foreground application or is dependent on the foreground application. The electronic device may detect, for each recyclable memory page allocated for the application to be processed, whether the data stored in the corresponding memory page is used by the foreground application within a preset time period, and if yes, determine that the memory page is used by the foreground The application depends. Alternatively, for the foreground application, it is detected whether it uses data stored in the recyclable memory page allocated for the application to be processed within a preset time period, and determines that the used memory page is dependent on the foreground application. The preset time period may be a preset time period of the current time, that is, the latest time period, and the duration of the latest time period is a preset duration, and the preset duration may be any set according to an empirical value. The appropriate length of time is, for example, 10 minutes, or half an hour. Or the preset time period may also be a time period in which the foreground application is currently running in the foreground. For example, if the foreground application is running in the foreground from 10:35:20 to the current time, the current time period is 10:35:20 to the current time.

Alternatively, the dependency ratio may be the ratio of the total number of dependencies of the reclaimable memory pages on which the foreground application depends and the total number of memory pages received by the client. By detecting whether the data stored in each recyclable memory page is dependent on the foreground application; and further determining the dependency ratio of the to-be-processed application to be dependent on the foreground application according to the detection result, the accuracy of the determined dependency ratio can be improved.

In one embodiment, operation 308 includes selecting a reclaimed number of memory pages that are not dependent on the foreground application for recycling from the reclaimable memory pages.

The electronic device can further eliminate the memory page that is relied upon by the foreground application, select the reclaimed memory page from the reclaimable memory page that is not depended by the foreground application, and recycle the selected memory page. The amount of recovery may not exceed the number of memory pages that are not dependent on the foreground application. By reclaiming the reclaimed memory page from a memory page that is not dependent on the foreground application, the memory pages that are relied upon by the foreground application are prevented from being recycled and affect the foreground application.

In an embodiment, before the operation 306, the method further includes: obtaining a correspondence between a recycling ratio corresponding to the to-be-processed application and a secondary startup duration; the operation 306 includes: according to the reclaimable memory page, the dependency ratio, and the recycling ratio The correspondence between the secondary startup durations determines the amount of memory page reclaimed.

The second startup duration refers to the length of time taken after the reclaimed memory page occupied by the application to be processed is recycled. The electronic device can set a corresponding relationship between the corresponding recycling ratio and the secondary startup time for each application. The corresponding relationship indicates the corresponding secondary startup time after reclaiming different proportions of recyclable memory in the memory occupied by the application. Optionally, the correspondence may be a comparison table between the corresponding recovery ratio and the secondary startup time, or a recovery ratio curve. The curve is the corresponding secondary start time under different recovery ratios. According to the correspondence, the appropriate recycling ratio is selected with reference to different secondary startup durations as the recovery ratio of the recyclable memory pages occupied by the application.

Optionally, the electronic device may set a corresponding startup duration threshold, and when the secondary startup duration reaches the startup duration threshold, the corresponding ratio is used as a reference ratio to the reclaimable memory page. The startup duration threshold may be a preset empirical value, and the startup duration thresholds of different applications may not be the same. For example, the corresponding startup time threshold may be determined according to the normal startup time of the corresponding application, and the duration of 1.5 times or 2 times of the normal startup time is used as the startup duration threshold. The reference scale represents a reference to the memory page recycling ratio. Based on the determined reference ratio, combined with the dependency ratio and the total number of reclaimable memory pages, determine the amount of recycling for recyclable memory pages.

In an embodiment, the correspondence between the recovery ratio and the secondary startup duration is not necessarily the same for applications of different application types. The application type is a type set according to the operational impact of the application to be processed after the memory is reclaimed. Application types include irrelevant classes, linear classes, and nonlinear classes. The irrelevant class indicates that after the reclaimable memory of the application to be processed is recycled, no matter how much it is recycled, it has no significant effect on the corresponding application. The linear class indicates that as the recovery ratio of recyclable memory increases, the secondary startup time of the corresponding application also increases, wherein the relationship between the secondary startup time and the recovery ratio is linear or nearly linear. Non-linear classes represent other types that are neither extraneous nor nonlinear. Among them, there is no significant influence that the ratio of the second startup time corresponding to different recovery ratios is smaller than the preset ratio range. The near linearity indicates that the difference between the second recovery time and the second startup time when the different recovery ratios are fitted according to the corresponding approximate slope does not exceed the error within the preset range.

For example, as shown in Figures 4A, 4B through 4C, the recovery ratio curves for applications of irrelevant, linear, and nonlinear classes, respectively, in one embodiment. Wherein, the abscissa in the recovery ratio curve represents the recovery ratio, and the ordinate represents the secondary startup time in the corresponding recovery ratio. Among them, the irrelevant class recovery ratio curve reflects that the corresponding application in the recyclable memory page after the recovery according to different recycling ratios, the corresponding secondary startup time has no change or little change. The recovery ratio curve of the linear type has no change or small change in the corresponding recovery ratio, and the recovery ratio curve of the nonlinear type has a large slope, and the slope of some places is relatively small. For non-linear applications, the recovery ratio corresponding to the minimum slope can be chosen as the recovery ratio for recyclable memory pages.

For different applications, the electronic device reclaims the corresponding secondary startup time according to different recycling ratios, sets the application type to which the application belongs, and sets a reference ratio corresponding to the application type. The corresponding amount of recycling is determined based on the recyclable memory page, the dependency ratio, and the reference ratio. Further, according to the reference ratio and the dependency ratio, the recycling ratio of the recyclable memory page occupied by the application to be processed may be determined, and the determined recycling ratio may be multiplied by the total number of recyclable memory pages, and the calculated product is used as the recycling quantity.

By determining the amount of recycling according to the secondary startup time, the balance between the recycling and operation of the application memory to be processed is further maintained.

In one embodiment, operation 308 includes reclaiming a reclaimed number of memory pages from the recyclable memory page at equal intervals of the memory page number.

Optionally, the electronic device may randomly collect the recovered memory pages according to the collected quantity, or select a collected number of memory pages from the recyclable memory page according to the serial number of the memory page for recycling. The memory page number is a number set by the electronic device to the memory page, and may be sequentially numbered according to 1, 2, 3, and the like. For example, when the recovery ratio is 33%, the determined uniform recovery interval is 2 memory pages per interval. For example, if the reclaimable memory page is from memory page 1 to memory page 100, the memory page 1 can be sequentially recovered. , memory page 4, memory page 7, memory page 10... memory page 97, memory page 100, to achieve the recovery of 33% of recyclable memory pages. By recycling at even intervals, each segment of memory is not completely reclaimed, making the application more stable when it is reopened.

In one embodiment, operation 302 includes querying all memory pages of memory occupied by the application to be processed; and obtaining recyclable memory pages from all memory pages.

Optionally, the electronic device can record the memory pages of the memory occupied by different applications in real time, and further record in real time whether the memory pages can be recycled for each occupied memory page. For example, when there is data in a certain memory page being used by another application or the application to be processed, it is determined that the memory page is a non-recyclable memory page, and when the data recorded in the occupied memory page is in no application. When the usage state, or the duration of the non-application use state exceeds the preset duration, the memory page is determined to be a reclaimable memory page.

For the pending application, all the memory pages occupied by the occupied information can be queried from the pre-recorded information, and according to the recorded usage status of each memory page, it is determined whether it is a recyclable memory page, and then all the recyclable memory is obtained. page.

In one embodiment, querying all memory pages of the memory occupied by the application to be processed includes: traversing a memory mapped file of the to-be-processed application; and querying all memory pages occupied by the to-be-processed application through the memory mapped file.

Memory-Mapped Files are mappings from one file to one memory. The electronic device establishes a corresponding memory mapping file for the to-be-processed application, and the memory mapping file stores a memory page occupied by the corresponding application, by traversing the memory mapping file corresponding to the to-be-processed application, and traversing from each The memory map file is used to read the memory page occupied by the to-be-processed application, so that all the memory pages occupied by the to-be-processed application can be obtained, and the query efficiency and the comprehensiveness of the query of the memory page occupied by the application to be processed are improved.

In one embodiment, the reclaimable memory page is obtained from all of the memory pages, including: removing the memory page carrying the occupied mark from all the memory pages; and obtaining the recyclable memory page from the rejected memory page.

The electronic device can detect whether each of the queried memory pages carries an occupation mark or is occupied by multiple applications, for all the memory pages occupied by the queried application. The occupancy mark indicates that the data stored in the corresponding memory page is being used by the application to be processed, or the data therein is indispensable data in the process of the pending application being kept in normal operation, and when the data is deleted, The pending application may not be able to run normally, or it may need to repeatedly occupy a new memory page to store corresponding data. For such detected data, the electronic device may set an occupancy flag on the memory page storing the data to indicate the corresponding Memory pages cannot be recycled.

The memory page occupied by the application to be processed, the data stored therein may also be used by other applications, that is, multiple applications are using the data in the memory page, and the memory page may also be set to occupy the mark. , so that the electronic device also culls it to indicate that it is not recycled from the memory page.

For the culled memory page, the reserved memory page is a recyclable memory page from which the electronic device can perform memory reclamation.

In an embodiment, the electronic device may invoke the resource priority and restriction management module 222 as shown in FIG. 2 to traverse the memory mapped file of the to-be-processed application; query all memory pages occupied by the to-be-processed application through the memory-mapped file, and The resource priority and limit management module 222 detects whether each memory page is a reclaimable memory page, sets a corresponding occupation mark for the non-recyclable memory page, and records whether each memory page is occupied by multiple applications, and queries from the query. All memory pages are excluded from carrying memory tags and/or memory pages occupied by multiple applications; retrievable memory pages are obtained from the rejected memory pages.

In an embodiment, the method further includes: determining that the to-be-processed application is dependent on the foreground application when there is a communication mechanism or a synchronization mechanism between the to-be-processed application and the foreground application.

In one embodiment, when there is socket communication, binder communication, memory sharing or lock waiting between the to-be-processed application and the foreground application, it is determined that there is a communication mechanism between the background process and the foreground application.

You can detect whether there is a background process that has communication mechanism with the foreground application by any one or several of the following methods:

(1) detecting whether there is a background process that has socket and/or binder communication with the foreground application;

(2) detecting whether there is a background process for memory sharing with the foreground application;

(3) Detect whether there is a background process waiting for the foreground application to wait on the lock resource.

The electronic device can set a detection mechanism for the Binder communication between the foreground application and the background process in the Binder driver, and call the detection mechanism set in the Binder driver to detect the background process that the Binder communication exists with the foreground application, and the detection will be detected. The background process is determined to be a background process that is dependent on the foreground application.

In one embodiment, the electronic device can detect individual lock resources, including thread locks, file handles, signals, and the like. For each lock resource, it can be detected whether a lock wait occurs, that is, the lock resource waits. When it is detected that a lock wait is generated, it may be further detected whether the behavior of the occurrence of the wait occurs on the foreground application. If so, all the background processes waiting for the lock resource are traversed, and the detected background processes waiting on the lock resource are all determined to be background processes that are depended by the foreground application.

In one embodiment, the electronic device may set a lock resource monitoring module and a priority adjustment module in a kernel space of the operating system, and embed the lock resource monitoring module into the kernel's native waiting interface. Through the lock resource monitoring module, detecting thread locks, file handles, signals, etc. lock various lock resources, whether a wait occurs, whether the waiting behavior occurs in the foreground application, and if it occurs on the foreground task, it will detect The message is sent to the priority adjustment module. Through the priority adjustment, all the background threads waiting for the lock resource are traversed, and these background processes are determined as the background processes that are depended by the foreground application.

In an embodiment, when there is a synchronization mechanism between the background process and the foreground application, it is determined that the to-be-processed application with the synchronization mechanism is a background process that is dependent on the foreground application.

The electronic device can also detect the background process in the background process set by calling the futex system call, whether there is a background process having a synchronization mechanism with the foreground application, and determine the background process with the synchronization mechanism as the background process that is depended by the foreground application.

In concurrent programming, access to public variables must be restricted by each process. This constraint is called synchronization. In the operating system, the user mode synchronization mechanism can be implemented by calling the futex system call. Among them, the user state refers to the non-privileged state. Synchronization mechanisms include semaphores, mutex locks, and more. When a background process that detects any kind of synchronization mechanism with the foreground application is detected by the futex system call, the detected background process may be determined as a background process that is dependent on the foreground application.

By detecting the communication mechanism and/or the synchronization mechanism between the foreground application and the background process, the detected background process having the communication mechanism and/or the synchronization mechanism with the foreground application is determined to be a background process dependent on the foreground application, which can be improved. The efficiency of detection of pending applications that are relied upon by the foreground application.

In one embodiment, as shown in FIG. 5, another memory processing method is provided, the method comprising:

Operation 502: traverse the memory mapped file of the to-be-processed application; query all memory pages occupied by the to-be-processed application through the memory mapped file.

In one embodiment, the electronic device may trigger a memory reclamation mechanism when detecting that the memory usage of the system exceeds a preset ratio or receiving a memory reclamation instruction triggered by a user operation, and from all running applications. Identify the application that needs to be recycled, and the determined application is the pending application.

In one embodiment, the electronic device may trigger a memory reclamation mechanism for the application after detecting that an application is switched from the foreground to the background and the platform freeze management module 224 sets the application to the process deep freeze mode.

The electronic device can traverse the memory mapping file of the to-be-processed application by using the resource priority and restriction management module 222, and query the memory page occupied by the application to be processed from each memory mapping file traversed, so that the memory can be queried. All memory pages occupied by the pending application.

Operation 504, the memory page carrying the occupied mark is removed from all the memory pages; and the reclaimable memory page is obtained from the rejected memory page.

For each memory page that is queried, a second traversal can be performed, and the second traversal is used to detect whether each of the queried memory pages is a recyclable memory page, and when the memory page carrying the occupied mark is detected, the memory is determined. The page is a non-recyclable memory page, and the memory page is culled. The memory page obtained after the second traversal is a recyclable memory page, and the electronic device can select a memory page from all the recyclable memory pages for recycling. Through the second traversal, the comprehensiveness of the detection of recyclable memory pages can be improved.

Operation 506, detecting whether data stored in each recyclable memory page is dependent on the foreground application; determining, according to the detection result, a proportion of dependencies that the to-be-processed application is dependent on by the foreground application.

Wherein, when there is a communication mechanism or a synchronization mechanism between the to-be-processed application and the foreground application, it is determined that the to-be-processed application is dependent on the foreground application, and detecting which reclaimable memory pages are specifically dependent on the foreground application, according to the detection The result determines the dependency ratio. The detection results include that the memory page is not dependent on the foreground application or is dependent on the foreground application. The dependency ratio can be the ratio of the total number of dependencies of the reclaimable memory pages that the foreground application depends on to the total number of pages that the client receives. When the pending application is not dependent on the foreground application, the dependency ratio is zero.

For the detected memory page that is dependent on the application, a corresponding dependency identifier may be set for the memory page, so that according to the dependency identifier, it is known which specific applications the corresponding memory page is dependent on. Further, according to whether each recyclable memory page is set with a corresponding dependency identifier, and whether the dependency identifier is represented by the foreground application, the proportion of dependencies that the to-be-processed application is dependent on by the foreground application can be calculated. In an embodiment, the validity of the corresponding dependency identifier may be determined according to the preset time period, and when the preset dependency period is within the corresponding preset time period, the set dependency identifier is kept valid, when the preset time period is outside, The set dependency ID can be canceled. By setting the dependency identifier, the efficiency of calculating the dependency ratio can be improved.

Operation 508, obtaining a correspondence between the recovery ratio corresponding to the application to be processed and the secondary startup duration.

The secondary startup time is the length of time that the reclaimed memory page occupied by the application to be processed is reclaimed after being recycled. The correspondence relationship may be a comparison table between the corresponding recovery ratio and the secondary startup time, or a recovery ratio curve. The curve is the corresponding secondary start-up duration at different recovery ratios, which may be the curves as shown in Figures 4A through 4C. The correspondence relationship may be determined according to the corresponding secondary detection duration under different detection ratios recorded under a preset number of times. For example, 100 tests can be performed, each time a different recovery ratio can be detected, and the corresponding secondary start time is long, and the average value of the secondary start time in the same ratio is taken as the second corresponding to the recovery ratio in the corresponding relationship. Startup time.

Operation 510, determining the number of reclaimed memory pages according to a correspondence between the recyclable memory page, the dependency ratio, and the reclaim ratio and the secondary boot duration.

The electronic device may select an appropriate ratio as the corresponding reference ratio according to the correspondence between the recycling ratio and the secondary startup time, and then determine the recovery ratio of the recyclable memory page according to the reference ratio and the dependency ratio, and then determine the ratio. The product of the recycling ratio and the total number of recyclable memory pages is used as the recycling quantity.

In one embodiment, the recovery ratio of the recyclable memory page may be determined according to the reference ratio and the dependency ratio, for example, the reference ratio is a, the dependency ratio is b, and the recovery ratio of the recyclable memory page is c. When the sum of a and b is not more than 1, c=a can be taken directly; when the sum of a and b is not more than 1, c=1-b can be taken directly. It not only improves the efficiency of the calculation of the recovery ratio, but also makes the memory pages that are not subject to the foreground application depend on the memory pages that are subsequently recovered, and the effect of the application to be processed is small, and the memory pages are collected as much as possible.

In operation 512, a reclaimed memory page that is not dependent on the foreground application is selected from the reclaimable memory page for recycling.

In one embodiment, a reclaimed number of memory pages may be reclaimed from memory pages that are not dependent on the foreground application at equal intervals of the memory page number.

The impact on the foreground application can be further reduced by reclaiming memory pages that are not dependent on the foreground application.

It should be understood that although the operations in the flowcharts of FIGS. 3 and 5 are sequentially displayed as indicated by the arrows, these operations are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these operations is not strictly limited, and the operations may be performed in other sequences. Moreover, at least some of the operations in FIGS. 3 and 5 may include multiple sub-operations or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, or The order of execution of the stages is also not necessarily sequential, but may be performed alternately or alternately with at least a portion of the sub-operations or stages of other operations or other operations.

In one embodiment, as shown in FIG. 6, an in-memory processing device is provided. The device includes a memory page acquisition module 602, a dependency determination module 604, and a memory recovery module 606. The memory page obtaining module 602 is configured to obtain a reclaimable memory page occupied by the to-be-processed application; the dependency determining module 604 is configured to obtain a dependency ratio of the to-be-processed application that is dependent on the foreground application; and the memory recycling module 606 is configured to use the reclaimable memory page. And the dependency ratio determines the amount of reclaimed reclaimable memory pages; select the reclaimed amount of memory pages from the reclaimable memory pages for recycling.

In one embodiment, the memory page obtaining module 602 is further configured to query all memory pages of the memory occupied by the application to be processed; the memory page carrying the occupied mark is removed from all the memory pages; and the reclaimable memory page is retrievable. Memory page.

In one embodiment, the memory page obtaining module 602 is further configured to traverse a memory mapped file of the to-be-processed application; and query all memory pages occupied by the to-be-processed application through the memory mapped file.

In one embodiment, the dependency determination module 604 is further configured to detect whether data stored in each recyclable memory page is dependent on the foreground application; determining, according to the detection result, a dependency ratio of the to-be-processed application being dependent on the foreground application; the detection result includes the memory page Not dependent on the foreground application or dependent on the foreground application.

The memory reclamation module 606 is further configured to select, from the reclaimable memory page, a reclaimed number of memory pages that are not dependent on the foreground application for recycling.

In an embodiment, the memory recovery module 606 is further configured to obtain a correspondence between a recycling ratio corresponding to the to-be-processed application and a secondary startup duration; the secondary startup duration refers to that the reclaimable memory page occupied by the to-be-processed application is recycled. The time taken to start again after the corresponding recovery ratio; determine the number of memory pages to be recycled based on the correspondence between the recyclable memory page, the dependency ratio, and the recycling ratio and the secondary startup duration.

In one embodiment, the memory reclamation module 606 is further configured to reclaim a reclaimed number of memory pages from the recyclable memory page at equal intervals of the memory page number.

In one embodiment, the dependency determination module 604 is further configured to determine that the to-be-processed application is dependent on the foreground application when there is a communication mechanism or a synchronization mechanism between the to-be-processed application and the foreground application.

The above-mentioned memory processing device determines the amount of recycling according to the dependency ratio and the recyclable memory page, and obtains the reclaimed memory page according to the dependency ratio and the reclaimable memory page, by acquiring the recyclable memory page occupied by the application to be processed and the dependency ratio of the to-be-processed application being relied upon by the foreground application. Select a reclaimed number of memory pages for recycling. Since the reclaimed objects are recyclable memory pages, and not all recyclable memory pages are reclaimed, the reclaimed quantity is determined according to the proportion of dependencies that the pending application is dependent on by the foreground application. While reducing the impact of the memory occupied by the pending application on the foreground application, it also reduces the operational impact of the application to be processed, and the reclaimed memory page can be released for use by other applications, thereby improving the overall processing efficiency of the system. Recycling by selecting the determined number of memory pages from the reclaimable memory page ensures that the negative impact on each application is minimized in the case where the entire system memory becomes large, and the recovery and operation of the application memory to be processed is maintained. The balance between.

The division of each module in the above memory processing device is for illustrative purposes only. In other embodiments, the memory processing device may be divided into different modules as needed to complete all or part of the functions of the memory processing device.

For the specific definition of the memory processing device, reference may be made to the definition of the memory processing method in the above, and details are not described herein again. Each of the above-described memory processing devices may be implemented in whole or in part by software, hardware, and combinations thereof. Each of the above modules may be embedded in or independent of the processor in the electronic device, or may be stored in a memory in the electronic device in a software format, so that the processor calls to perform operations corresponding to the above modules.

The implementation of each module in the memory processing device provided in the embodiments of the present application may be in the form of a computer program. The computer program can run on an electronic device such as a terminal or a server. The program module of the computer program can be stored on a memory of the electronic device. When the computer program is executed by the processor, the operation of the memory processing method described in the embodiment of the present application is implemented.

In one embodiment, an electronic device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, the memory processing provided by the above embodiments being implemented when the processor executes the computer program The operation of the method.

In one embodiment, there is also provided a computer readable storage medium having stored thereon a computer program for performing memory processing as described in various embodiments of the present application when executed by a processor The operation of the method.

In one embodiment, a computer program product comprising instructions, when executed on a computer, causes the computer to perform the memory processing methods described in various embodiments of the present application.

The embodiment of the present application also provides a computer device. As shown in FIG. 7 , for the convenience of description, only the parts related to the embodiments of the present application are shown. If the specific technical details are not disclosed, please refer to the method part of the embodiment of the present application. The computer device may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, a wearable device, and the like, taking a computer device as a mobile phone as an example. :

FIG. 7 is a block diagram showing a part of a structure of a mobile phone related to a computer device according to an embodiment of the present application. Referring to FIG. 7, the mobile phone includes: a radio frequency (RF) circuit 710, a memory 720, an input unit 730, a display unit 740, a sensor 750, an audio circuit 760, a wireless fidelity (WiFi) module 770, and a processor 780. And power supply 790 and other components. It will be understood by those skilled in the art that the structure of the mobile phone shown in FIG. 7 does not constitute a limitation to the mobile phone, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.

The RF circuit 710 can be used for receiving and transmitting signals during the transmission and reception of information or during a call. The downlink information of the base station can be received and processed by the processor 780. The uplink data can also be sent to the base station. Generally, RF circuits include, but are not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, RF circuitry 710 can also communicate with the network and other devices via wireless communication. The above wireless communication may use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (Code Division). Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), e-mail, Short Messaging Service (SMS), and the like.

The memory 720 can be used to store software programs and modules, and the processor 780 executes various functional applications and data processing of the mobile phone by running software programs and modules stored in the memory 720. The memory 720 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as an application of a sound playing function, an application of an image playing function, etc.); The data storage area can store data (such as audio data, address book, etc.) created according to the use of the mobile phone. Moreover, memory 720 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 730 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function controls of the handset 700. Specifically, the input unit 730 may include a touch panel 731 and other input devices 732. The touch panel 731, also referred to as a touch screen, can collect touch operations on or near the user (such as the user using a finger, a stylus, or the like on the touch panel 731 or near the touch panel 731. Operation) and drive the corresponding connection device according to a preset program. In one embodiment, the touch panel 731 can include two portions of a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information. The processor 780 is provided and can receive commands from the processor 780 and execute them. In addition, the touch panel 731 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 731, the input unit 730 may also include other input devices 732. In particular, other input devices 732 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.).

The display unit 740 can be used to display information input by the user or information provided to the user as well as various menus of the mobile phone. The display unit 740 can include a display panel 741. In one embodiment, the display panel 741 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. In one embodiment, the touch panel 731 can cover the display panel 741. When the touch panel 731 detects a touch operation on or near it, the touch panel 731 transmits to the processor 780 to determine the type of the touch event, and then the processor 780 is The type of touch event provides a corresponding visual output on display panel 741. Although the touch panel 731 and the display panel 741 are used as two independent components to implement the input and input functions of the mobile phone in FIG. 7, in some embodiments, the touch panel 731 can be integrated with the display panel 741. Realize the input and output functions of the phone.

The handset 700 can also include at least one type of sensor 750, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 741 according to the brightness of the ambient light, and the proximity sensor may close the display panel 741 and/or when the mobile phone moves to the ear. Or backlight. The motion sensor may include an acceleration sensor, and the acceleration sensor can detect the magnitude of the acceleration in each direction, and the magnitude and direction of the gravity can be detected at rest, and can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching), and vibration recognition related functions (such as Pedometer, tapping, etc.; in addition, the phone can also be equipped with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors.

Audio circuitry 760, speaker 761, and microphone 762 can provide an audio interface between the user and the handset. The audio circuit 760 can transmit the converted electrical data of the received audio data to the speaker 761 for conversion to the sound signal output by the speaker 761; on the other hand, the microphone 762 converts the collected sound signal into an electrical signal by the audio circuit 760. After receiving, it is converted into audio data, and then processed by the audio data output processor 780, transmitted to another mobile phone via the RF circuit 710, or outputted to the memory 720 for subsequent processing.

WiFi is a short-range wireless transmission technology, and the mobile phone can help users to send and receive emails, browse web pages, and access streaming media through the WiFi module 770, which provides users with wireless broadband Internet access. Although FIG. 7 shows the WiFi module 770, it can be understood that it does not belong to the essential configuration of the mobile phone 700 and can be omitted as needed.

The processor 780 is the control center of the handset, which connects various portions of the entire handset using various interfaces and lines, by executing or executing software programs and/or modules stored in the memory 720, and invoking data stored in the memory 720, The phone's various functions and processing data, so that the overall monitoring of the phone. In one embodiment, processor 780 can include one or more processing units. In one embodiment, processor 780 can integrate an application processor and a modem, where the application processor primarily processes an operating system, user interface, applications, etc.; the modem primarily handles wireless communications. It will be appreciated that the above described modem may also not be integrated into the processor 780. For example, the processor 780 can integrate an application processor and a baseband processor, and the baseband processor and other peripheral chips can form a modem. The handset 700 also includes a power source 790 (such as a battery) that supplies power to the various components. Preferably, the power source can be logically coupled to the processor 780 via a power management system to manage functions such as charging, discharging, and power management through the power management system.

In one embodiment, the handset 700 can also include a camera, a Bluetooth module, and the like.

In the embodiment of the present application, the processor included in the mobile phone implements the memory processing method described above when executing a computer program stored in the memory.

Any reference to a memory, storage, database or other medium used herein may include non-volatile and/or volatile memory. Suitable non-volatile memories can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as an external cache. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronization. Link (Synchlink) DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The above embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the claims. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present application. Therefore, the scope of the invention should be determined by the appended claims.

Claims

A memory processing method, comprising:

Get the reclaimable memory page occupied by the pending application;

Obtaining a proportion of dependencies that the to-be-processed application is dependent on by the foreground application;

Determining the amount of recycling of the recyclable memory page according to the recyclable memory page and the dependency ratio; and

The recovered number of memory pages are selected from the recyclable memory pages for recycling.
The method according to claim 1, wherein the obtaining a proportion of dependencies that the to-be-processed application is dependent on by the foreground application comprises:

Detecting whether the data stored in each recyclable memory page is dependent on the foreground application;

Determining, according to the detection result, a proportion of dependencies that the to-be-processed application is dependent on by the foreground application; the detection result includes that the memory page is not dependent on the foreground application or is dependent on the foreground application.
The method according to claim 2, wherein said retrieving said recovered number of memory pages from said recyclable memory page for recycling comprises:

The recycled number of memory pages that are not depended by the foreground application are selected from the reclaimable memory pages for recycling.
The method according to claim 2, wherein said detecting whether data stored in each recyclable memory page is dependent on a foreground application comprises:

When the foreground application uses data stored in the recyclable memory page within a preset time period, it is determined that the recyclable memory page is dependent on the foreground application.
The method according to claim 1, wherein the determining the amount of recycling of the recyclable memory page according to the recyclable memory page and the dependency ratio comprises:

Determining a recycling ratio of the recyclable memory page according to the dependency ratio;

The amount of recycling of the recyclable memory page is determined based on the recycling ratio and the total number of recyclable memory pages.
The method according to claim 1, further comprising: before determining the amount of recycling of the recyclable memory page according to the recyclable memory page and the dependency ratio, further comprising:

Obtaining a correspondence between the recycling ratio corresponding to the to-be-processed application and the secondary startup duration; the secondary startup duration is when the reclaimable memory page occupied by the to-be-processed application is recycled corresponding to the recycling ratio, The length of time spent at startup;

Determining, according to the recyclable memory page and the dependency ratio, a quantity of the reclaimed memory page, including:

And determining, according to the recyclable memory page, the dependency ratio, and the correspondence between the recycling ratio and the secondary startup duration, the number of the memory pages to be recovered.
The method according to claim 6, wherein the determining the number of reclaimed memory pages according to the correspondence between the recyclable memory page, the dependency ratio, and the recovery ratio and the secondary startup duration ,include:

And configuring, according to the second startup duration, an application type to which the application belongs, and configuring a corresponding reference ratio for the application type;

Determining the recovery ratio according to the reference ratio and the dependency ratio;

The amount of recycling of the memory page is obtained according to the recycling ratio and the total number of the recycled memory pages.
The method according to claim 1, wherein said retrieving said recovered number of memory pages from said recyclable memory page for recycling comprises:

The recovered number of memory pages are selected from the recyclable memory pages at equal intervals according to the memory page number for recycling.
The method according to claim 1, wherein the obtaining a recyclable memory page occupied by the application to be processed comprises:

Traversing the memory mapped file of the pending application;

Querying, by the memory mapping file, all memory pages occupied by the to-be-processed application;

Removing the memory page carrying the occupied mark from all the memory pages;

Get reclaimable memory pages from the stripped memory page.
The method according to any one of claims 1 to 9, further comprising:

When there is a communication mechanism or a synchronization mechanism between the to-be-processed application and the foreground application, it is determined that the to-be-processed application is dependent on the foreground application.
An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein when the computer program is executed by the processor, the processor performs the following operations:

Get the reclaimable memory page occupied by the pending application;

Obtaining a proportion of dependencies that the to-be-processed application is dependent on by the foreground application;

Determining the amount of recycling of the recyclable memory page according to the recyclable memory page and the dependency ratio; and

The recovered number of memory pages are selected from the recyclable memory pages for recycling.
The electronic device according to claim 11, wherein the processor performs acquisition of a dependency ratio of the to-be-processed application that is dependent on the foreground application, and further performs an operation of: detecting whether data stored in each recyclable memory page is Rely on the foreground application;

Determining, according to the detection result, a proportion of dependencies that the to-be-processed application is dependent on by the foreground application; the detection result includes that the memory page is not dependent on the foreground application or is dependent on the foreground application.
The electronic device according to claim 12, wherein the processor performs the process of selecting the recovered number of memory pages from the recyclable memory page for recycling, and further performing the following operations:

The recycled number of memory pages that are not depended by the foreground application are selected from the reclaimable memory pages for recycling.
The electronic device according to claim 12, wherein the processor performs a process of detecting whether data stored in each recyclable memory page is dependent on the foreground application, and further performs the following operations:

When the foreground application uses data stored in the recyclable memory page within a preset time period, it is determined that the recyclable memory page is dependent on the foreground application.
The electronic device according to claim 11, wherein the processor performs the determining the amount of recycling of the recyclable memory page according to the recyclable memory page and the dependency ratio, and further performs the following operations:

Determining a recycling ratio of the recyclable memory page according to the dependency ratio;

The amount of recycling of the recyclable memory page is determined based on the recycling ratio and the total number of recyclable memory pages.
The electronic device according to claim 11, wherein the processor performs the following operations before performing the determining, according to the recyclable memory page and the dependency ratio, the number of reclaimed memory pages. :

Obtaining a correspondence between the recycling ratio corresponding to the to-be-processed application and the secondary startup duration; the secondary startup duration is when the reclaimable memory page occupied by the to-be-processed application is recycled corresponding to the recycling ratio, The length of time spent at startup;

The processor performs the determining, according to the recyclable memory page and the dependency ratio, a quantity of the reclaimed memory page, and further performing the following operations:

And determining, according to the recyclable memory page, the dependency ratio, and the correspondence between the recycling ratio and the secondary startup duration, the number of the memory pages to be recovered.
The electronic device according to claim 11, wherein the processor performs the process of selecting the recovered number of memory pages from the recyclable memory page for recycling, and further performing the following operations:

The recovered number of memory pages are selected from the recyclable memory pages at equal intervals according to the memory page number for recycling.
The electronic device according to claim 11, wherein the processor executes the retrievable memory page occupied by the to-be-processed application, and further performs the following operations:

Traversing the memory mapped file of the pending application;

Querying, by the memory mapping file, all memory pages occupied by the to-be-processed application;

Removing the memory page carrying the occupied mark from all the memory pages;

Get reclaimable memory pages from the stripped memory page.
The electronic device according to any one of claims 11 to 18, wherein the processor further performs the following operations:

When there is a communication mechanism or a synchronization mechanism between the to-be-processed application and the foreground application, it is determined that the to-be-processed application is dependent on the foreground application.
A computer readable storage medium having stored thereon a computer program, wherein the computer program is executed by a processor to perform the steps of the method of any one of claims 1 to 10.