Joke Collection Website - Mood Talk - Why do Android phones run so many programs in the background? 360 Guardian desktop floating icon, 80% at a time, can not be cleaned with one click.

Why do Android phones run so many programs in the background? 360 Guardian desktop floating icon, 80% at a time, can not be cleaned with one click.

Andriod is developed based on Linux system, which is very important, because I believe there are many people, even

Some experts will ignore this and fall into a misunderstanding. What misunderstanding? Is to manually close Sung Hoon and pursue more.

Large capacity spare memory.

We are used to the Windows system and the concept that the more free memory, the faster it runs. Everyone is using it.

Andriod's mobile phone will also maintain this concept. Close programs manually frequently to save memory. Actually, you don't have to work.

For Andriod system, or Linux system, it is completely different from Windows system, so they

I have a completely different view of memory.

The design that most Android applications don't quit is actually reasonable, which is related to the system's scheduling mechanism for processes.

Department. If you know Java, you will be more aware of this mechanism, because Java itself has a garbage collection mechanism.

Similar to Java's garbage collection mechanism, Andriod system has a rule to recycle memory. The memory scheduler has a valve.

Value, only below this value, the system will close things that users don't need according to a list. Of course, this value is set by default.

Set it very small, so you will see that the memory is always hovering over several values. But it doesn't actually affect the speed. on the contrary

It is faster to start the application next time. This is one of the advantages of Andre's propaganda. If the process is shut down artificially,

There is not much demand, especially using software that automatically closes the process. This is what I'm talking about. Why don't you need to shut it down manually?

The process has ended. And I believe that as a stable system, the setting of each value itself should be the most balanced.

Therefore, there is no need to blindly pursue the size of value, just enough. )

Then you may ask, why is it so slow to run large programs when there is little memory? It's actually very simple,

Opening a large program when there is little memory left will trigger the system's own scheduling strategy, which is very costly.

Manage the operation of resources, especially when a program frequently requests memory from the system. In this case, the system will not

Close all open processes, but selectively. Frequent scheduling will naturally slow down the system. (This is the reason.

Large-scale programs started slowly at first, and then gradually returned to normal speed. Of course, adjusting the time requires

Look at the machine. )

So, is process management software necessary? This is necessary. Before running a large program, you can

Moving and closing some processes to release memory can significantly improve the running speed. But some small programs can be handed over to the system.

Manage yourself.

Someone may ask, if you don't turn off the program, it will consume more electricity. Some netizens are concerned about whether it will consume traffic.

Let me talk about the principle of Android background, and everyone will understand. When an Android application switches to the background, it actually

Has been suspended, will not consume cpu resources, just keep running, with little power consumption and no traffic. (This is it.

Why do we cut off some programs and re-enter the program, or will we go to the main interface of the program? but

If a program wants to handle something in the background, such as music playing, it will start a service. The service can be obtained from the following website

The background runs continuously, so only applications with services consume power in the background. This can be seen in the process management software.

Here, the label is the service. As for broadcasting, I won't involve it. So no application with service is completed in the background.

There is no need to turn it off if there is no power consumption at all. This design is a very good design. The next time you start this program,

It will be faster, because you don't need to read the interface resources, so why turn it off and obliterate the advantages of this Android?

There is another one, why an Android application seems to consume so much memory. This is because, on Android, you should

With Java, of course, virtual machines are needed. Applications on Android have independent virtual machines, that is, each one is open.

The application will open a separate virtual machine. The reason for this design is to avoid the virtual machine crash leading to the paralysis of the whole system.

Crash, but at the cost of more memory. (So you will find that if you use the Andriod system normally,

It rarely crashes, except bad firmware. )

These designs ensure the stability of Android. Under normal circumstances, at most one program crashes, but the whole system

The system will not crash, and there will never be a hint of insufficient memory. You may be used to using Windows, and you are in it.

The concept of memory is so poisonous that I always want to keep more memory, but in fact it doesn't necessarily improve the speed, on the contrary.

But it is unnecessary to lose the system characteristic of fast program startup. )

I also downloaded the process management software when I used it, but later I found that it didn't make much difference (because I played on a large scale)

There are fewer games), so now I trust Andriod's ability of self-regulating memory.