CN114691358A

CN114691358A - Android system performance optimization method, system, device and storage medium

Info

Publication number: CN114691358A
Application number: CN202210276535.6A
Authority: CN
Inventors: 罗伟坚; 刘弋波
Original assignee: Allwinner Technology Co Ltd
Current assignee: Allwinner Technology Co Ltd
Priority date: 2022-03-21
Filing date: 2022-03-21
Publication date: 2022-07-01

Abstract

The application discloses a method, a system and a device for optimizing android system performance and a storage medium. The method comprises the following steps: modifying a preset parameter, and determining that dex2oat is in an inactivated state; if the system finishes booting, confirming to execute the writeback operation; and determining to release redundant background processes according to the number of the preset background cache processes. The system comprises: the device comprises a first execution module, a second execution module and a third execution module. By using the method in the application, the memory utilization rate of the system can be improved, and the user experience is favorably improved. The method and the device can be widely applied to the technical field of computers.

Description

Android system performance optimization method, system, device and storage medium

Technical Field

The application relates to the technical field of computers, in particular to a method, a system and a device for optimizing android system performance and a storage medium.

Background

With the version upgrade of the android system, the system code is more and more huge, which results in the memory consumption of the android native system being more and more large. Starting from Android R, in the 1GB GMS scheme, the available memory is reduced to 300MB, so that the experience requirements are difficult to meet, and the problems of user operation card pause, application flash retreat, online video playing card pause and the like are caused.

Disclosure of Invention

The present application aims to solve at least to some extent one of the technical problems existing in the prior art.

Therefore, the invention aims to provide an efficient and reliable android system performance optimization method, system, device and storage medium.

Another object of the embodiment of the present application is to provide a system for optimizing android system performance.

In order to achieve the technical purpose, the technical scheme adopted by the embodiment of the application comprises the following steps:

on one hand, the embodiment of the application provides an android system performance optimization method, which comprises the following steps:

the android system performance optimization method comprises the following steps: modifying a preset parameter, and determining that dex2oat is in an unopened state; if the system finishes booting, confirming to execute the writeback operation; and determining to release redundant background processes according to the number of the preset background cache processes. By the method, the memory utilization rate of the system can be improved, and the user experience is favorably improved.

In addition, according to the android system performance optimization method of the embodiment of the application, the following additional technical features can be further provided:

further, in the method for optimizing the performance of the android system in the embodiment of the present application, modifying the preset parameter and determining that dex2oat is in an inactivated state includes the following steps: acquiring the memory of the current equipment, and judging whether the memory of the current equipment is smaller than a preset memory; and if the memory of the current equipment is smaller than the preset memory, modifying the preset parameters and determining that the dex2oat is in an unopened state.

Further, in an embodiment of the present application, after the modifying the preset parameter and determining that the dex2oat is in the disabled state, the method includes the following steps: and modifying a PMS packet scanning mechanism and determining that dex2oat is in an inactivated state.

Further, in an embodiment of the application, the modifying the PMS packet scanning mechanism to determine that dex2oat is in an inactive state includes: judging whether dex2oat is started through an application end or not according to the application ID; and if the dex2oat is started through the application terminal, confirming that the dex2oat is placed in a non-enabled state.

Further, in an embodiment of the present application, after determining to release redundant background processes according to the number of the preset background cache processes, the method further includes the following steps: releasing the system interface memory; the application-self-initiated broadcast process is restricted.

Further, in an embodiment of the present application, the confirming to execute the writeback operation if the system completes booting includes: if the system finishes starting up, recording a first time length; and if the first time length is equal to the preset waiting time length, triggering the writeback function through the refreshZramaWritebock interface.

Further, in an embodiment of the present application, before triggering the writeback function through the refreshZramWriteback interface, the method further includes: and judging whether the current system supports ZramWriteback.

On the other hand, the embodiment of the present application provides an android system performance optimization system, including: the first execution module is used for modifying the preset parameters and determining that the dex2oat is in an inactivated state; the second execution module is used for confirming to execute the writeback operation when the system finishes starting; and the third execution module is used for determining to release redundant background processes according to the preset number of the background cache processes.

On the other hand, this application embodiment provides an android system performance optimization device, includes:

at least one processor;

at least one memory for storing at least one program;

when executed by the at least one processor, the at least one program causes the at least one processor to implement any of the android system performance optimization methods described above.

In another aspect, an embodiment of the present application provides a storage medium, where a program executable by a processor is stored, and when the program is executed by the processor, the program is used to implement any one of the methods for optimizing performance of an android system described above.

The android system performance optimization method in the embodiment of the application comprises the following steps: modifying a preset parameter, and determining that dex2oat is in an unopened state; if the system finishes starting, confirming to execute the writeback operation; and determining to release redundant background processes according to the number of the preset background cache processes. By using the method, the memory utilization rate of the system can be improved, and the user experience is favorably improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description is made on the drawings of the embodiments of the present application or the related technical solutions in the prior art, and it should be understood that the drawings in the following description are only for convenience and clarity of describing some embodiments in the technical solutions of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.

Fig. 1 is a schematic flow chart of an embodiment of a method for optimizing the performance of an android system provided in the present application;

fig. 2 is a schematic flowchart of an example of a method for optimizing the performance of an android system provided in the present application;

fig. 3 is a schematic flowchart of another example of the android system performance optimization method provided in the present application;

fig. 4 is a schematic flowchart of another example of a method for optimizing android system performance provided in the present application;

fig. 5 is a schematic structural diagram of an embodiment of an android system performance optimization system provided by the present application;

fig. 6 is a schematic structural diagram of an embodiment of the android system performance optimization device provided in the present application.

Detailed Description

Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application. The step numbers in the following embodiments are provided only for convenience of illustration, the order between the steps is not limited at all, and the execution order of each step in the embodiments can be adapted according to the understanding of those skilled in the art.

In recent years, with more and more functions and continuously upgraded versions of Android systems, larger and larger codes are brought in the Android and kernel upgrading process, and more memory consumption of the systems is caused, so that the user has less and less available memory, and serious problems of operation blockage, application flash withdrawal, online video playing blockage and the like are caused. The requirement of a low-end flat panel or related products certified by GMS for a 1GB small memory is still very large, and therefore, a performance improvement technique of a 1GB small memory scheme of an android system becomes more and more important.

In view of the above problems, the following solutions exist in the related art:

1. by combining scene prejudgment and a more detailed memory management mechanism, a memory 'balanced' state is achieved, and as much memory as possible is provided for application; the scheme cannot improve more available memories per se, and the effect is not obvious.

2. The 32-bit ARM chip is used, so that the occupation of the kernel memory is reduced, and the system has more memories for use; the optimization of this scheme is limited and limited to 32 bits.

3. A cutting system, which cuts out the functions of the product which are not used, such as GMS bags, for reducing the load of the system; this scheme is not applicable to systems that require GMS authentication.

4. The image quality and the resolution are reduced, and the available memory is improved by reducing the occupation of the display buffer; this approach reduces the user visual experience.

5. Forbidding a 1GB memory scheme to install third-party application, and pre-installing lightweight application; the use scene of the scheme is too limited and is not suitable for most products.

6. Starting a Zram mechanism, and enabling the idle application program memory swap to flash, so that the application memory occupation is saved; too much swap in this scheme would result in the kswapd process taking up CPU height.

Therefore, the present application provides a method and a system for optimizing the performance of an android system, and first, the method for optimizing the performance of the android system provided in the embodiments of the present application will be described with reference to the accompanying drawings.

Referring to fig. 1, an embodiment of the present application provides a method for optimizing performance of an android system, where the method for optimizing performance of an android system in the embodiment of the present application may be applied to a terminal, a server, software running in the terminal or the server, and the like. The terminal may be, but is not limited to, a tablet computer, a notebook computer, a desktop computer, and the like. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, cloud functions, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, and a big data and artificial intelligence platform. The android system performance optimization method in the embodiment of the application mainly comprises the following steps:

s110: modifying a preset parameter, and determining that dex2oat is in an unopened state;

in this step, the dex2oat is set to be in the non-enabled state by modifying the preset parameters. The dex2oat is a program for performing compilation optimization on a dex file, and after the dex2oat is compiled and optimized, the (installation speed and starting speed) can be increased, but the dex2oat is not friendly to low-memory devices. In some possible embodiments, for a 1GB small memory device, the available memory is generally about 400MB, the short video related application itself occupies 300MB, and at this time, if dex2oat (130MB +) is also enabled, the system memory is not enough, and a kernel memory recycling mechanism is triggered, causing the kswapd process to crazy perform CPU exchange, and severely occupying the CPU. The Google native does not consider the situation of a small memory device, and after the dex2oat is started, the system does not achieve the optimization effect and can cause the situation that the application cannot run at all. Therefore, the application determines that the dex2oat is in the non-enabled state by modifying the preset parameter. Specifically, by modifying the virtual machine parameter pm, dexopt, boot, verify, the modified user has already completed the dex2oat precompilation optimization when installing the short video class or other related applications, which is equivalent to pre-importing the run-time dex2oat to the user installation process. Through the optimization of the dex2oat strategy, a native mechanism is modified, and the dex2oat is forbidden to be started aiming at 1GB low-memory equipment, so that the foreground application can be ensured to have abundant available CPU/DDR, and the user experience is improved.

S120: if the system finishes booting, confirming to execute the writeback operation;

in this step, if the system is booted, the writeback operation is executed, and the memory is released. Specifically, the Zram is a block device for memory compression, an unusual memory page is stored on the Zram block device through a swap mechanism, then the unusual page is released, an available memory is increased, and when the memory page in the block needs to be used, data are read from the Zram block device to the memory. The Zram supports the writeback function, and can write back the physical page applied in the Zram to a real disk, so that the memory is further released. Therefore, the available memory of the system is optimized through the Zram writeback technical principle. In the related art, the Android native mechanism does not enable the Zram writeback function by default, and even if the function is enabled, the time for triggering writeback is very strict (the system needs to be in an idle state and triggers once in 24 hours). In contrast, the system memory is improved by modifying the trigger time of the writeback. In some possible embodiments, triggering writeback is performed after the system is booted, so as to release the memory. By the method, more available memory is provided for the application.

S130: and determining to release redundant background processes according to the number of the preset background cache processes.

In this step, the number of the background caching processes is preset, and the release of redundant background processes is determined. In some possible embodiments, the number of background cache processes, that is, the maximum retainable processes in the background, is preset, the size of the system memory can be detected by setting the background management service, the number of the preset background cache processes is customized, and a few redundant background processes are determined to be optimized by monitoring the available system memory in real time, so that the real-time foreground application process can obtain more available system memories. Specifically, the number of the background caching processes is preset and can be set according to user requirements, and the specific numerical value of the number of the background caching processes is not limited in the application. In some possible embodiments, the available memory of the system may be monitored and optimized periodically or for a certain period of time by adding a time attribute, and by this method, the experience of the foreground application is optimized.

Optionally, in the method for optimizing performance of an android system in this embodiment of the application, the modifying the preset parameter and determining that the dex2oat is in the non-enabled state includes the following steps:

acquiring the memory of the current equipment, and judging whether the memory of the current equipment is smaller than a preset memory;

and if the memory of the current equipment is smaller than the preset memory, modifying the preset parameters and determining that the dex2oat is in an unopened state.

In this step, the above steps are executed after determining that the current device belongs to the small memory device by detecting the memory of the current device. And memory optimization is performed on the small memory device, so that the system performance is improved.

Optionally, in the method for optimizing performance of an android system in this embodiment of the application, after the preset parameter is modified and it is determined that dex2oat is in the non-enabled state, the method includes the following steps:

and modifying a PMS packet scanning mechanism and determining that dex2oat is in an inactivated state.

In this step, the native PMS packet scanning mechanism of the installation system is modified to confirm that dex2oat is in an inactive state, so as to improve the performance of the system from the application layer.

Optionally, in the method for optimizing performance of an android system in this embodiment, the modifying a PMS packet scanning mechanism and determining that dex2oat is in an inactive state includes:

judging whether dex2oat is started through an application end or not according to the application ID;

and if the dex2oat is started through the application terminal, confirming that the dex2oat is placed in a non-enabled state.

In the step, whether dex2oat is initiated from the shell end is judged by modifying an Android native PMS packet scanning mechanism and detecting uid, and if yes, dex2oat is prohibited, so that the application end cannot initiate dex2oat any more. Referring to fig. 2, through step 210 and step 220, the dex2oat policy of the application runtime is moved forward to the application installation, and the application self-starting dex2oat is prohibited from the framework layer, so that on one hand, the occupation consumption of the dex2oat process on the CPU is reduced, and on the other hand, the memory occupation of the dex2oat is reduced.

Optionally, in the method for optimizing performance of an android system in this embodiment of the present application, after determining to release redundant background processes according to the number of the preset background cache processes, the method further includes the following steps:

releasing the system interface memory;

the application-self-initiated broadcast process is restricted.

In this step, referring to fig. 3, the background management service system is optimized to perform background process intervention, so that the background process does not occupy too much memory, and more memory is released to be used by the foreground process. Specifically, in step 320, the intervention system ui occasionally releases the memory by the GC, so that the foreground can obtain more memory at the first time, avoid frequent memory recovery by the kernel, avoid frequent high load of the CPU, and optimize the experience of foreground application. In some possible embodiments, the process is: as shown in fig. 3, step 310, automatically recognizing that the current system is a low memory device by reading the configuration; step 320, performing GC on the SystemUI to release the memory; step 330, limiting the number of the background caches (redundant caches are cleaned up), in this embodiment, the number of the processes of the background caches is preset to be 3; step 340, limiting the broadcast service that the rogue application still starts after exiting the foreground. By the method, the experience of foreground application is optimized.

Optionally, in the method for optimizing performance of an android system in this embodiment of the application, the determining to execute the writeback operation if the system completes booting includes:

if the system finishes starting up, recording a first time length;

and if the first time length is equal to the preset waiting time length, triggering the writeback function through the refreshZramWriteback interface.

In this step, after the system is booted and waits for a certain time, the writeback operation is executed. Specifically, the first duration may be 30s, which is used to wait for the writeback operation to proceed when the CPU load is low, and the writeback function may be triggered through the refreshZramWriteback interface. In some possible embodiments, referring to fig. 4, the specific implementation method is as follows: modifying the native opportunity of triggering the writeback, waiting for 30s after the system finishes booting, and then realizing that a refreshZramaWriteback interface calls ZramaWiteback. Through actual measurement, the Zram writeback can optimize and increase 60MB of memory on a 1GB memory scheme, and the effect is obvious.

Optionally, before triggering the writeback function through the refreshhzramwriteback interface, the method for optimizing performance of an android system in this embodiment of the application further includes:

and judging whether the current system supports ZramWriteback.

In this step, the subsequent operation is performed by detecting whether the current system supports ZramWriteback. Specifically, if the current system supports ZramWriteback, the writeback function is triggered through the refreshZramWriteback interface.

Through the description, the fluency of the system is improved by reducing the CPU occupancy rate and increasing the two dimensions of the memory available for the application, so that the user experience is improved. The performance optimization method is high in universality and applicable to any Android version, hardware platform and related products; the common effects of the foreground application program on three dimensions of CPU occupation, IO occupation and available memory are reduced, and sufficient performance space is provided for the foreground application program.

In order to better describe the method proposed in the present application, the effect of the method is illustrated by specific examples below. Referring to table 1, when the method provided by the application is used for an A133 Android R1 GB platform, 100MB + optimization results are obtained on a memory, the memory optimization is improved by 40%, and from the perspective of user experience, the performance improvement of both small video software and online network video clients and game experience is greater than that before the optimization.

TABLE 1

Next, an android system performance optimization system proposed according to an embodiment of the present application is described with reference to the drawings.

Fig. 5 is a schematic structural diagram of an android system performance optimization system according to an embodiment of the present application, where the system specifically includes:

a first executing module 510, configured to modify a preset parameter, and determine that dex2oat is in an inactivated state;

a second executing module 520, configured to confirm that the writeback operation is executed when the system is booted;

a third executing module 530, configured to determine to release redundant background processes according to a preset number of background cache processes.

It can be seen that the contents in the foregoing method embodiments are all applicable to this system embodiment, the functions specifically implemented by this system embodiment are the same as those in the foregoing method embodiment, and the advantageous effects achieved by this system embodiment are also the same as those achieved by the foregoing method embodiment.

Referring to fig. 6, an embodiment of the present application provides an android system performance optimization device, including:

at least one processor 610;

at least one memory 620 for storing at least one program;

when executed by the at least one processor 610, causes the at least one processor 610 to implement the android system performance optimization methodology.

Similarly, the contents of the method embodiments are all applicable to the apparatus embodiments, the functions specifically implemented by the apparatus embodiments are the same as the method embodiments, and the beneficial effects achieved by the apparatus embodiments are also the same as the beneficial effects achieved by the method embodiments.

The embodiment of the present application further provides a computer-readable storage medium, in which a program executable by the processor 610 is stored, and when the program executable by the processor 610 is executed by the processor 610, the method for controlling the fresh air system is performed.

Similarly, the contents in the foregoing method embodiments are all applicable to this storage medium embodiment, the functions specifically implemented by this storage medium embodiment are the same as those in the foregoing method embodiments, and the advantageous effects achieved by this storage medium embodiment are also the same as those achieved by the foregoing method embodiments.

In alternative embodiments, the functions/acts noted in the block diagrams may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Furthermore, the embodiments presented and described in the flowcharts of the present application are provided by way of example in order to provide a more thorough understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed and in which sub-operations described as part of larger operations are performed independently.

Furthermore, although the present application is described in the context of functional modules, it should be understood that, unless otherwise stated to the contrary, one or more of the functions and/or features may be integrated in a single physical device and/or software module, or one or more functions and/or features may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion regarding the actual implementation of each module is not necessary for an understanding of the present application. Rather, the actual implementation of the various functional modules in the apparatus disclosed herein will be understood within the ordinary skill of an engineer given the nature, function, and interrelationships of the modules. Accordingly, those skilled in the art can, using ordinary skill, practice the present application as set forth in the claims without undue experimentation. It is also to be understood that the specific concepts disclosed are merely illustrative of and not intended to limit the scope of the application, which is defined by the appended claims and their full scope of equivalents.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium, which includes programs for enabling a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable programs that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with a program execution system, apparatus, or device (such as a computer-based system, processor-containing system, or other system that can fetch the programs from the program execution system, apparatus, or device and execute the programs). For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the program execution system, apparatus, or device.

More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.

It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable program execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.

In the foregoing description of the specification, reference to the description of "one embodiment/example," "another embodiment/example," or "certain embodiments/examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

While embodiments of the present application have been shown and described, it will be understood by those of ordinary skill in the art that: numerous changes, modifications, substitutions and alterations can be made to the embodiments without departing from the principles and spirit of the application, the scope of which is defined by the claims and their equivalents.

While the present application has been described with reference to the preferred embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A performance optimization method for an android system is characterized by comprising the following steps:

modifying a preset parameter, and determining that dex2oat is in an unopened state;

if the system finishes booting, confirming to execute the writeback operation;

and determining to release redundant background processes according to the number of the preset background cache processes.

2. The android system performance optimization method of claim 1, wherein the modifying the preset parameter and determining that dex2oat is in an inactive state comprises:

3. The android system performance optimization method of claim 1, wherein the modifying the preset parameter and determining that dex2oat is in an inactive state comprises:

4. The android system performance optimization method of claim 3, wherein the modifying the PMS packet scanning mechanism to determine that dex2oat is in an inactive state comprises:

5. The android system performance optimization method of claim 1, wherein after determining to release redundant background processes according to the number of the preset background cache processes, the method further comprises the following steps:

releasing the system interface memory;

the application-self-initiated broadcast process is restricted.

6. The android system performance optimization method of claim 1, wherein confirming to execute a writeback operation if the system completes booting comprises:

if the system finishes starting up, recording a first time length;

7. The android system performance optimization method of claim 6, wherein before triggering the writeback function via the refreshZramWriteback interface, the method further comprises:

and judging whether the current system supports ZramWriteback.

8. An android system performance optimization system, comprising:

the first execution module is used for modifying the preset parameters and determining that the dex2oat is in an inactivated state;

the second execution module is used for confirming to execute the writeback operation when the system finishes starting up;

and the third execution module is used for determining to release redundant background processes according to the preset number of the background cache processes.

9. An android system performance optimization device, comprising:

at least one processor;

at least one memory for storing at least one program;

when executed by the at least one processor, cause the at least one processor to implement the android system performance optimization method of any of claims 1-7.

10. A computer-readable storage medium in which a program executable by a processor is stored, characterized in that: the processor-executable program, when executed by a processor, is for implementing the android system performance optimization method of any of claims 1-7.