subtitlecat.com

All language subtitles for 4_Process Management

Afrikaans

Albanian

Amharic

Arabic Download

Armenian

Azerbaijani

Basque

Belarusian

Bengali

Bosnian

Bulgarian

Catalan

Cebuano

Chichewa

Chinese (Simplified)

Chinese (Traditional)

Corsican

Croatian

Czech

Danish

Dutch

English

Esperanto

Estonian

Filipino

Finnish

French

Frisian

Galician

Georgian

German

Greek

Gujarati

Haitian Creole

Hausa

Hawaiian

Hebrew

Hindi

Hmong

Hungarian

Icelandic

Igbo

Indonesian

Irish

Italian

Japanese

Javanese

Kannada

Kazakh

Khmer

Korean

Kurdish (Kurmanji)

Kyrgyz

Lao

Latin

Latvian

Lithuanian

Luxembourgish

Macedonian

Malagasy

Malay

Malayalam

Maltese

Maori

Marathi

Mongolian

Myanmar (Burmese)

Nepali

Norwegian

Pashto

Persian

Polish

Portuguese

Punjabi

Romanian

Russian

Samoan

Scots Gaelic

Serbian

Sesotho

Shona

Sindhi

Sinhala

Slovak

Slovenian

Somali

Spanish

Sundanese

Swahili

Swedish

Tajik

Tamil

Telugu

Thai

Turkish

Ukrainian

Urdu

Uzbek

Vietnamese

Welsh

Xhosa

Yiddish

Yoruba

Zulu

Odia (Oriya)

Kinyarwanda

Turkmen

Tatar

Uyghur

Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,200 --> 00:00:02,820 One of the most important tasks that 2 00:00:02,820 --> 00:00:05,505 our kernel performs is process management. 3 00:00:05,505 --> 00:00:07,980 A process is a program that's executing, 4 00:00:07,980 --> 00:00:10,470 like our Internet browser or text editor. 5 00:00:10,470 --> 00:00:12,720 A program is an application 6 00:00:12,720 --> 00:00:14,685 that we can run, like Chrome. 7 00:00:14,685 --> 00:00:16,160 Take note of the difference. 8 00:00:16,160 --> 00:00:17,880 We can have many processes of 9 00:00:17,880 --> 00:00:20,535 the same program running at the same time. 10 00:00:20,535 --> 00:00:23,040 Think of how many Chrome windows you can open. 11 00:00:23,040 --> 00:00:26,175 These are all different processes for the same program. 12 00:00:26,175 --> 00:00:27,854 When we want to run our programs, 13 00:00:27,854 --> 00:00:30,330 we have to dedicate computer resources to them, 14 00:00:30,330 --> 00:00:32,160 like RAM and CPU. 15 00:00:32,160 --> 00:00:34,580 We only have a finite amount of resources, 16 00:00:34,580 --> 00:00:37,145 and we want to be able to run multiple programs. 17 00:00:37,145 --> 00:00:38,900 Our kernel has to manage our resources 18 00:00:38,900 --> 00:00:40,970 efficiently so that all the programs 19 00:00:40,970 --> 00:00:42,570 we want to use can be run. 20 00:00:42,570 --> 00:00:44,255 Our kernel doesn't just dedicate 21 00:00:44,255 --> 00:00:46,780 all of our computers resources to one process. 22 00:00:46,780 --> 00:00:49,295 Our system is actually constantly running 23 00:00:49,295 --> 00:00:52,765 multiple processes that are necessary for it to function. 24 00:00:52,765 --> 00:00:54,680 Our kernel has to worry about all of 25 00:00:54,680 --> 00:00:56,570 these processes at once. 26 00:00:56,570 --> 00:00:58,490 What a program wants to run, 27 00:00:58,490 --> 00:01:00,550 a process needs to be created for it. 28 00:01:00,550 --> 00:01:01,970 This process needs to have 29 00:01:01,970 --> 00:01:04,580 hardware resources like RAM and CPU. 30 00:01:04,580 --> 00:01:07,190 The kernel has to schedule time for the CPU to 31 00:01:07,190 --> 00:01:09,560 execute the instructions in the process, 32 00:01:09,560 --> 00:01:12,735 but there's only one CPU and many processes. 33 00:01:12,735 --> 00:01:14,920 How is the CPU able to execute 34 00:01:14,920 --> 00:01:18,175 multiple processes at once? It actually doesn't. 35 00:01:18,175 --> 00:01:21,130 It executes processes one-by-one 36 00:01:21,130 --> 00:01:23,650 through something known as a time slice. 37 00:01:23,650 --> 00:01:26,830 A time slice is a very short interval of time that 38 00:01:26,830 --> 00:01:30,340 gets allocated to a process for CPU execution. 39 00:01:30,340 --> 00:01:33,460 It's so short that you don't even notice it. 40 00:01:33,460 --> 00:01:35,345 It's super short. 41 00:01:35,345 --> 00:01:38,890 The CPU executes one process in milliseconds, 42 00:01:38,890 --> 00:01:41,650 then executes another process, then another. 43 00:01:41,650 --> 00:01:43,330 To the human eye, everything looks 44 00:01:43,330 --> 00:01:45,395 like it runs simultaneously. 45 00:01:45,395 --> 00:01:48,180 That's how fast the CPU works. 46 00:01:48,180 --> 00:01:50,130 If your computer is running slowly, 47 00:01:50,130 --> 00:01:52,795 and your CPU resources are being maxed out, 48 00:01:52,795 --> 00:01:55,175 there can be many factors at play. 49 00:01:55,175 --> 00:01:57,590 It's possible that one process is 50 00:01:57,590 --> 00:02:00,185 taking up more time slices than it should. 51 00:02:00,185 --> 00:02:03,490 This means that the next process can't be executed. 52 00:02:03,490 --> 00:02:05,300 Another possibility is that 53 00:02:05,300 --> 00:02:06,830 there are too many processes that 54 00:02:06,830 --> 00:02:10,235 want CPU time and the CPU can't keep up with them. 55 00:02:10,235 --> 00:02:12,045 Whatever the case may be, 56 00:02:12,045 --> 00:02:13,640 even though the kernel does its best 57 00:02:13,640 --> 00:02:15,365 to manage processes for us, 58 00:02:15,365 --> 00:02:18,160 we might need to step in manually from time-to-time. 59 00:02:18,160 --> 00:02:19,865 The kernel creates processes, 60 00:02:19,865 --> 00:02:21,560 efficiently schedules them, and 61 00:02:21,560 --> 00:02:23,770 manages how processes are terminated. 62 00:02:23,770 --> 00:02:26,195 This is important since we need a way to collect 63 00:02:26,195 --> 00:02:28,610 all the previously used resources that 64 00:02:28,610 --> 00:02:30,500 active processes were taking up 65 00:02:30,500 --> 00:02:33,720 and reallocate them to another process. 4992