KR101783148B1 - Task scheduling method for energy-efficient mobile web browsing and mobile device for performing the same - Google Patents

Abstract

A task scheduling method for energy-efficient mobile web browsing and a mobile device for performing the same are disclosed. The task scheduling method includes a step of starting web page loading using a mobile web browser, a step of determining the image size of a web page to be loaded, a step of classifying the threads of the mobile web browser into a first thread to be placed in a high performance core and a second thread to be placed in a low performance core according to a determined image size, a step of placing the first thread in the high performance core, and a step of placing the second thread in the low performance core.

Description

[0001] Task scheduling method for energy efficient mobile web browsing [0002] A task scheduling method for energy-efficient mobile web browsing and mobile device [

The present invention relates to a task scheduling method for energy efficient mobile web browsing.

Most modern mobile devices use a heterogeneous multi-core processor, which includes both a high-performance high-performance core and a low-power low-power core (Small Core) ). In order to efficiently utilize heterogeneous multicore processors including these different types of cores, it is important to arrange and execute threads in a suitable type of CPU core. This is because placing a thread that does not require high performance in a low power core can reduce power consumption, and performance can be improved by placing a high performance thread in a high performance core.

Currently, the most widely used task scheduling method in the Linux kernel determines the CPU core to which threads are allocated considering only the CPU utilization of each thread. However, since the conventional task scheduling method does not consider the characteristics of the web browser at all, it is not energy efficient in web browsing. Depending on the configuration of the web page being loaded, the threads that need higher performance in the web browser are different. For example, when loading a web page with many images, the threads that process the image need high performance. Also, when loading web pages with relatively few images and relatively large number of scripts, the threads that process the scripts need high performance. Existing task scheduling that does not consider the characteristics of the web browser causes unnecessary energy consumption by allocating threads that do not require high performance to a high performance core. As a result, the high performance core can not enter the idle state and can not be turned off.

On the other hand, mobile devices have limited battery life. Therefore, there is a need for a method of increasing the energy efficiency of a mobile device in order to increase battery usage time.

In order to reduce the energy consumption of a mobile device by a web browser, which is one of the most frequently used applications of mobile device users, the present invention analyzes a characteristic of a mobile web browser, And a task scheduling method for energy efficient mobile web browsing in which a thread that does not require high performance is placed in a low power core.

According to an aspect of the present invention, a task scheduling method for energy efficient mobile web browsing is provided in a mobile device equipped with a processor including a high performance core and a low power core.

A task scheduling method according to an exemplary embodiment of the present invention includes starting a web page loading using a mobile web browser, determining an image size by checking an image size of a web page to be loaded, Classifying the threads of a mobile web browser into a first thread to be placed in the high performance core and a second thread to be placed in the low power core; placing the first thread in the high performance core; To the low power core.

Wherein the step of determining the image size comprises the steps of determining the web page to be loaded as a web page having a large image if the size of the image is greater than or equal to a predetermined threshold value among the components of the web page to be loaded, If the size is less than a predetermined threshold, determining that the web page to be loaded is a web page with a small number of images.

The first and second threads are classified according to whether they affect the loading time of the mobile web page.

The classifying thread may include classifying a thread associated with image processing into the first thread if the size of the image included in the web page to be loaded is greater than or equal to a predetermined threshold, Classifying the thread related to the script processing into the first thread and classifying all the other threads into the second thread when the size of the image included in the web page to be loaded is less than a predetermined threshold, .

The thread associated with the image processing is at least one of RendererMain, Compositor and CompositorRasterWorker, and the thread associated with the script processing is RendererMain.

Wherein the step of arranging the first thread in the high performance core comprises periodically checking the processor usage of the first thread until the loading of the mobile web page is completed, , Placing the first thread in a high performance core and placing the first thread in a low power core if the processor usage of the first thread is below a certain level.

The step of placing the second thread in the low power core always places the second thread in the low power core until loading of the mobile web page is terminated.

According to another aspect of the present invention, a mobile device for performing task scheduling for energy efficient mobile web browsing is disclosed.

A mobile device according to an embodiment of the present invention includes a memory for storing instructions and a processor for executing the instructions and including a high performance core and a low power core, Determining a size of an image of a loading web page to determine an image size; determining a first thread to place threads of a mobile web browser on the high performance core according to the determined image size; , Placing the first thread in the high performance core, and placing the second thread in the low power core.

A task scheduling method for an energy efficient mobile web browsing according to an embodiment of the present invention is a task scheduling method for allocating threads that do not require high performance to low power cores and arranging threads requiring high performance on high performance cores, High-performance cores with high power consumption can be idle for a long time to power-off, thereby reducing energy consumption and improving performance.

1 illustrates a method for scheduling tasks for energy efficient mobile web browsing according to an embodiment of the present invention.
2 illustrates an example of thread classification of a mobile web browser;
3 is a schematic view illustrating a configuration of a mobile device according to an embodiment of the present invention.

As used herein, the singular forms "a", "an" and "the" include plural referents unless the context clearly dictates otherwise. In this specification, the terms "comprising ", or" comprising "and the like should not be construed as necessarily including the various elements or steps described in the specification, Or may be further comprised of additional components or steps. Also, the terms "part," " module, "and the like described in the specification mean units for processing at least one function or operation, which may be implemented in hardware or software or a combination of hardware and software .

Hereinafter, various embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 is a diagram illustrating a task scheduling method for energy efficient mobile web browsing according to an embodiment of the present invention, and FIG. 2 is a diagram illustrating an example of thread classification of a mobile web browser. A task scheduling method for an energy efficient mobile web browsing according to an embodiment of the present invention is performed in a mobile device. Hereinafter, a task scheduling method of FIG. 1 will be described with a mobile device as a main body. In addition, the mobile device according to the embodiment of the present invention includes a heterogeneous multi-core processor including both a high-performance high-performance core and a low-power low-power core (Small Core) .

In step S110, the mobile device starts loading the web page using the mobile web browser.

In step S120, the mobile device determines the image size by checking the size of the image of the web page to be loaded. That is, the mobile device can determine whether the web page to be loaded is a web page with many images or a web page with a small number of images.

For example, if the image size of the web page to be loaded is equal to or greater than a predetermined threshold, the mobile device determines that the web page to be loaded is a web page having a large number of images, ), The web page to be loaded can be determined as a web page having a small number of images.

In step S130, the mobile device classifies the threads of the mobile web browser into the first thread and the second thread according to the determined image size. Here, the first thread is an important thread to be placed in a high performance core, and the second thread is an insignificant thread to be placed in the low power core.

For example, referring to FIG. 2, if the web page to be loaded is a web page having many images, the RendererMain, the Compositor, and the CompositorRasterWorker are classified as important first threads of the mobile web browser, It can be classified into a second thread. If the web page to be loaded is a web page with a small number of images, the RendererMain may be classified as an important first thread, and all other threads may be classified as a non-critical second thread.

Most of the threads in a mobile web browser operate asynchronously. Thus, among the threads of a mobile web browser, there are threads that do not affect the loading time of the entire mobile web page, that is, non-critical threads, even when operated on a low power core. Conversely, there are threads, or critical threads, that affect the overall loading time of mobile web pages.

When a mobile web browser loads a web page, depending on the configuration of the web page to be loaded, the threads of the mobile web browser are different from the important thread and the non-critical thread.

That is, when the web page to be loaded is a web page having many images, it is important to process the image through the CPU or GPU and display the processed image. So, RendererMain, Compositor, and CompositorRasterWorker, which are threads related to image processing in CPU or GPU, are classified as important threads, and all other threads can be classified as non-critical threads.

Conversely, if the loading web page is a web page with few images and a relatively large number of scripts, the process of parsing and running the script through the CPU is important. Thus, only the RendererMain, the thread associated with script processing, is classified as an important thread, and all other threads can be classified as non-critical threads.

In step S140, the mobile device places the first thread in the high performance core of the CPU. At this time, the mobile device periodically checks the CPU usage of the first thread until the loading of the mobile web page is terminated. If the CPU usage of the first thread is higher than a certain level, the first thread is placed in the high performance core, If the CPU usage of the first thread is less than a certain level, the first thread is placed in the low power core.

In step S150, the mobile device places the second thread in the low power core of the CPU. That is, the mobile device always places the non-critical second thread in the low-power core until the loading of the mobile web page is terminated.

The task scheduling method for an energy efficient mobile web browsing according to an embodiment of the present invention realigns important threads to a high performance core or a low power core according to the CPU usage of a thread. That is, if the CPU usage of any critical thread is higher than a certain level, then the thread is placed in the high performance core, and if the CPU usage of some critical thread is lower than a certain level, the thread can be placed in the low power core. And non-critical threads are always placed in the low-power core, regardless of the thread's CPU usage. By doing this, non-critical threads are not placed in the high performance core, and unnecessary energy consumption can be reduced.

3 is a schematic view illustrating a configuration of a mobile device according to an embodiment of the present invention.

Referring to FIG. 3, a mobile device according to an embodiment of the present invention includes a processor 10, a memory 20, a communication unit 30, and an interface 40.

The processor 10 may be a CPU or a semiconductor device that executes processing instructions stored in the memory 20. For example, the processor 10 may be a heterogeneous multi-core processor including both a high-performance high-performance core and a low-power consumption low-power core.

The memory 20 may include various types of volatile or non-volatile storage media. For example, the memory 20 may include ROM, RAM, and the like.

For example, the memory 20 may store instructions for performing a task scheduling method for energy efficient mobile web browsing according to an embodiment of the present invention. Also, the memory 20 may store thread classification information according to thread importance of the mobile web browser.

The communication unit 30 is a means for transmitting and receiving data to and from other devices through a communication network.

The interface unit 40 may include a network interface and a user interface for connecting to the network.

On the other hand, the components of the above-described embodiment can be easily grasped from a process viewpoint. That is, each component can be identified as a respective process. Further, the process of the above-described embodiment can be easily grasped from the viewpoint of the components of the apparatus.

In addition, the above-described technical features may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

It will be apparent to those skilled in the art that various modifications, additions and substitutions are possible, without departing from the spirit and scope of the invention as defined by the appended claims. Should be regarded as belonging to the following claims.

10: Processor
20: Memory
30:
40:

Claims (8)

A task scheduling method for energy efficient mobile web browsing performed in a mobile device equipped with a processor including a high performance core and a low power core,
Initiating web page loading using a mobile web browser;
Determining an image size of a web page to be loaded and determining an image size;
Classifying threads of a mobile web browser into a first thread to be placed in the high performance core and a second thread to be placed in the low power core according to the determined image size;
Placing the first thread in the high performance core; And
Placing the second thread in the low power core,
Wherein determining the image size comprises:
Determining that the web page to be loaded is a web page having a large number of images if the size of the image of the web page to be loaded is greater than or equal to a predetermined threshold; And
And determining that the web page to be loaded is a web page having a small number of images if the size of the image is less than a predetermined threshold,
Wherein classifying the threads comprises:
Classifying a thread associated with image processing into the first thread and classifying all the other threads into the second thread if the size of the image included in the web page to be loaded is greater than or equal to a preset threshold value; And
Classifying the thread associated with the script processing into the first thread and classifying all the other threads into the second thread when the size of the image included in the web page to be loaded is less than a preset threshold value The task scheduling method comprising:
delete The method according to claim 1,
Wherein the first and second threads are classified according to whether they affect the loading time of the mobile web page.
delete The method according to claim 1,
Wherein the thread associated with the image processing is at least one of RendererMain, Compositor, and CompositorRasterWorker, and the thread associated with the script processing is a RendererMain.
The method according to claim 1,
The step of placing the first thread in the high performance core comprises:
Periodically checking the processor usage of the first thread until the loading of the web page is terminated;
Placing the first thread in a high performance core if the processor usage of the first thread is above a certain level; And
And if the processor usage of the first thread is less than a predetermined level, placing the first thread in a low power core.
The method according to claim 1,
The step of placing the second thread in the low-
Wherein the second thread is always placed in the low power core until loading of the mobile web page is terminated.
1. A mobile device for performing task scheduling for energy efficient mobile web browsing,
A memory for storing instructions; And
A processor executing the instructions and including a high performance core and a low power core,
Wherein the command comprises:
Initiating web page loading using a mobile web browser;
Determining an image size of a web page to be loaded and determining an image size;
Classifying threads of a mobile web browser into a first thread to be placed in the high performance core and a second thread to be placed in the low power core according to the determined image size;
Placing the first thread in the high performance core; And
And placing the second thread in the low power core,
Wherein determining the image size comprises:
Determining that the web page to be loaded is a web page having a large number of images if the size of the image of the web page to be loaded is greater than or equal to a predetermined threshold; And
And determining that the web page to be loaded is a web page having a small number of images if the size of the image is less than a predetermined threshold,
Wherein classifying the threads comprises:
Classifying a thread associated with image processing into the first thread and classifying all the other threads into the second thread if the size of the image included in the web page to be loaded is greater than or equal to a preset threshold value; And
Classifying the thread associated with the script processing into the first thread and classifying all the other threads into the second thread when the size of the image included in the web page to be loaded is less than a preset threshold value Mobile devices.

Images