I can try to explain using a definition and a real-life example: 1. Program Definition: A program is a set of instructions written in a specific programming language that the computer can execute. It is essentially a blueprint, and it does not perform any action until it is run. Analogy: Think of a program as a recipe for cooking. The recipe outlines all the steps and ingredients needed to make a dish, but until you start cooking, the recipe is just an inactive set of instructions. 2. Process Definition: A process is an instance of a program in execution. When you run a program, it becomes a process. A process has its own memory space, system resources, and an operating system environment. Analogy: Continuing with the recipe analogy, a process is like someone actually cooking according to the recipe. Each person (process) has their own kitchen space (memory) and resources, like ingredients and utensils, which they use while cooking. Example: When you open a web browser (like Chrome or Firefox), a process is created for it. Each tab within the browser might even have its own process, depending on the browser design. 3. Thread Definition: A thread is the smallest unit of execution within a process. A process can have multiple threads, all sharing the same memory but running independently. Threads within a process can perform different tasks simultaneously, improving efficiency. Analogy: In the cooking example, if multiple people are working together on the same dish, each person could be considered a thread. They share the same kitchen (memory) and ingredients (resources) but may be responsible for different parts of the task, like chopping vegetables or stirring the pot. Example: In your web browser, multiple threads might handle different tasks: one for rendering the page, another for handling user input, and yet another for network requests. These threads all work within the same browser process. 4. Task Definition: In many modern programming frameworks (like .NET), a task is an abstraction that represents an asynchronous operation, which can run on a thread. Tasks are typically used for parallelism and concurrency, making it easier to manage multiple operations without blocking the main thread. Analogy: If cooking is the process and each cook is a thread, then a task might represent specific cooking jobs, like “boil water” or “slice onions.” These tasks can be assigned to cooks (threads) as they become available, optimizing workflow without everyone waiting for one task to complete before starting another. Example: In a web application, if you request data from a database, this request can be handled as a task. The application doesn't have to wait for the database to respond (which can be slow); instead, it can continue other work until the data is ready.
Building a house is a process, but the people doing the work to install the pipes, paint the walls and do the electrical work are all the working threads within the process of building the house. I like to use threads synonymously with “unit of work” or “thing that executes a specific piece of work / action for the process to complete successfully. So if I run chrome, and have 10 tabs open, I will have 10 processes running. Within each process are 1 or many units of work (called threads) responsible for memory management, access, logic, etc. I believe the house analogy works well in a lot of cases Also, I was asked this question in an interview during a Comp. Sci. Fundamentals round during the systems design portion of my interview process at a large, global company we all interact with daily. (Keeping vague for obvious reason)
I have to admit... I have never seen such good explaination videos merged with animations and diagrams in my life. GREAT CONTENT SIR! Keep on doing what you do.
Analogy for understanding process and thread • In essence a program/process/thread is executing a job(a set of instructions). So, in that context, it’s no different than physical labour work where one executes a bunch of instructions from his/her brain and uses the required tools to complete a job • Imagine you hire a fitter to mount your newly bought TV and you have already bought a TV mount. Here, the fitter represents a program. He has skills required to mount the TV(Set of instructions) and required tools(Data, library, plugins) • Hiring a fitter is equivalent to installing a program. You have got commitment from him/her to work on your job. And he brings himself and loads the tools in your space ready to do the job. But, You have yet to extract the job from him. For this, you need to prepare some physical space near your TV and also give him the authorization to work at your home. This is the equivalent of creating a process where you allocate CPU and ram memory for the program to execute its job • Just as a program can spin up multiple process, a fitter can bring multiple fitters to execute the same job. All of them work independently in their own physical space and with required authorization • So, what's the analogy for threads? A fitter usually breaks the job into sub tasks. Here, mounting a TV can be broken in tasks like punching holes in the wall, preparing the Mount frame, adjusting the tilt etc. These subtasks represent individual threads. These threads are executed in the same memory/heap space just as the fitter performs his subtasks on his original physical space. •Threads can be executed in parallel saving time. You can imagine this to be fitter performing tasks at the same time using his two hands. For example, one hand used to punch holes in the wall and other hand used to prepare the mount frame. This might sound like a stretch but there are some crazy people who could multitask with both hands
Thread is the mechanism of sending instructions from a program(process) to CPU. Threads are OS based mechanisms, also processes are too but a process includes at least one thread. You can imagine that a process is encapsulation of a thread or threads. The OS looks at the program(when you click an executable), creates an executing process for the execution of the program and in the process the thread or threads are the carrier of instructions which are sent to the CPU. This is the execution mechanism of a program in an OS. When you create a thread rather than the main thread, you say to the OS that in this thread those instructions should run in a different context, that will create a context switch(that is execution of instruction(s) given by a thread to the CPU in a determined duration), and by that, you will see imaginary parallel execution of different instructions in different threads. Maybe one second long instruction set will be executed in a one short lived thread while another long running thread (especially main thread) keeps running and by that short living thread will not wait the long running thread to be finished. That is the magical part of multi threaded executions.
@@mils3318 Yes, it is possible to run multiple threads in parallel within a single process in most modern operating systems. A process can have multiple threads of execution, which are also known as lightweight processes. Each thread runs concurrently and shares the process's resources, including memory and open files.
@@TheZhouh12 so it is possible that, for example, if we have a 8-core CPU on it, in one currently active process, multiple threads can be executed in parallel... not multitasking. Okay, thank you very much.
@@mils3318 When a CPU has multiple cores, it can execute multiple threads concurrently, as long as the operating system supports it. This is known as parallel processing.
@@mils3318 On a system with a single-core CPU, the operating system can still create multiple threads and schedule them to be executed one after the other, but they will not be able to run concurrently. This is known as multitasking.
Fantastic video - concise and clear explanations accompanied by extremely helpful visuals. Couldn't ask for a better description within 4 minutes of time. Subscribed!
All information that I knew but would be hard-pressed to scoop out of my brain on demand - it's great to have clear and succinct refreshers like this to keep the neurons fresh
0:07 What is the difference between Process and Thread? 0:10 This is a common interview question. Let’s take a look. 0:12 To better answer this question, let’s first understand what a program is. 0:17 A program is an executable file. 0:20 It contains the code, or a set of processor instructions, that is stored as a file on disk. 0:26 When the code in a program is loaded into memory and 0:29 executed by the processor, it becomes a process. 0:33 An active process also includes the resources the program needs to run. 0:37 These resources are managed by the operating system. 0:40 Some examples are processor registers, program counters, 0:44 stack pointers, memory pages assigned to the process for its heap and stack, etc. 0:51 There is an important property of a process that is worth mentioning. 0:55 Each process has its own memory address space. 0:57 One process cannot corrupt the memory space of another process. 1:01 This means that when one process malfunctions, other processes keep running. 1:07 Chrome is famous for taking advantage of this 1:10 process isolation by running each tab in its own process. 1:13 When one tab misbehaves due to a bug or a malicious attack, other tabs are unaffected. 1:21 So what is a thread? 1:23 A thread is the unit of execution within a process. 1:26 A process has at least one thread. It is called the main thread. 1:30 It is not uncommon for a process to have many threads. 1:35 Each thread has its own stack. 1:36 Earlier we mentioned registers, program counters, and stack pointers as being part of a process. 1:42 It is more accurate to say that those things belong to a thread. 1:46 Threads within a process share a memory address space. 1:50 It is possible to communicate between threads using that shared memory space. 1:55 However, one misbehaving thread could bring down the entire process. 2:01 How does the operating system run a thread or process on a CPU? 2:05 This is handled by context switching. 2:08 During a context switch, one process is switched out of the CPU so another process can run. 2:13 The operating system stores the states of the current running 2:17 process so the process can be restored and resume execution at a later point. 2:22 It then restores the previously saved states of a 2:26 different process and resumes execution for that process. 2:30 Context switching is expensive. 2:32 It involves saving and loading of registers, switching out memory pages, 2:37 and updating various kernel data structures. 2:40 Switching execution between threads also requires context switching. 2:45 It is generally faster to switch context between threads than between processes. 2:50 There are fewer states to track, and more importantly, since threads share 2:54 the same memory address space, there is no need to switch out virtual memory pages, 2:59 which is one of the most expensive operations during a context switch. 3:03 Context switching is so costly there are other mechanisms to try to minimize it. 3:08 Some examples are fibers and coroutines. 3:11 These mechanisms trade complexity for even lower context-switching costs. 3:16 In general, they are cooperatively scheduled, that is, they must yield control for others to run. 3:23 In other words, the application itself handles task scheduling. 3:28 It is the responsibility of the application 3:30 to make sure a long-running task is broken up by yielding periodically. 3:35 This concludes our discussion of Process vs Thread. 3:39 If you like to learn more about system design, check out our books and weekly newsletter. 3:44 Please subscribe if you learned something new. 3:46 Thank you so much and we'll see you next time.
Also, would love to see videos on "heap" and "serialization / encoding" (some visuals on why in-memory representation is different from byte sequence would be super super helpful ). Thanks again for these great videos!!!!
- **Definition Overview** - **Process:** Created when a program (executable file) is loaded into memory; includes resources managed by the OS (e.g., registers, memory pages). - **Key Property:** Each process has **its own memory address space**, preventing interference between processes; isolation ensures other processes continue running if one fails (e.g., Chrome tabs). - **Thread:** Unit of execution within a process; every process has at least one thread, with threads sharing the same memory space. - **Thread vs. Process Context** - Threads share memory, enabling easy communication but risking the whole process if one thread fails. - Processes have **separate memory spaces**, enhancing isolation but making inter-process communication more complex. - **Context Switching:** The OS switches between processes/threads, saving/restoring states. Switching between threads is faster than between processes due to shared memory. - **Context Switching Details** - Context switching is **expensive**, requiring saving/loading registers, memory pages, and updating kernel data structures. - **Thread switching** is faster since threads share memory, avoiding virtual memory page switching, which is the most costly part. - Mechanisms like **fibers** and **coroutines** are designed to minimize context-switching costs by being cooperatively scheduled, with tasks yielding control periodically. - **Conclusion** - Threads enable efficient execution within processes but can compromise stability. - Processes ensure strong isolation at the cost of slower context switching. - The discussion emphasizes trade-offs between complexity and performance.
Thank you for this video! I got this question in an interview this week, and I wish I could have watched this video before the interview! So concise but detailed explanation! And now I get to know what is the purpose of "yield" in Python. None of the resources about it explain in context of OS and context switching...!
program - executable instructions of code Program disc + ram + cpu = process process control block(PCB) thread - unit of execution within process stack pointers counters thread vs process? threads (of the same process) run in a shared memory space, processes run in separate memory spaces shared memory virtual memory pages switching ⚠ fibers coroutines
A process is a program executing by a processor. A process doesn't share memory with another process. It has a collection of threads: the main thread and the other threads if any. A thread is an execution unit inside a process. It shares the same heap memory with the other threads in the same process. But it has its own stack memory.
Great video. But I didn't understand how auto yielding reduces the cost of context switching? Because after yielding, context switching will have to be done anyway for the CPU to execute other processes.
Love your channel. Subscribed to it. If you don't mind, what tool do you use to author the content? I find this to be more engaging vs powerpoint based sessions. Thanks
Thanks for great video. Two questions, 1. So to run K programs embarassingly parallel via multi-processing you have to have K CPU? If number of CPU < K then it would have to switch context, correct? 2. when we are talking about multi-processing python basically two of same script is copied to each process memory?
For the process having multiple threads, OS would provide time quantum of execution per thread under a process? or each thread would get (1 quantum time / no. of threads in process) time for execution?
And what if we have processors with more cores. Does this mean that we can run more processes at the same time? In that case, do we potentially have higher performance because more processors mean less context switching between processes? Can we run two threads in parallel in one process? Or is only multitasking threads allowed per process (execution one by one)?
_And what if we have processors with more cores. Does this mean that we can run more processes at the same time?_ Yes, every logical core can run one thread. _In that case, do we potentially have higher performance because more processors mean less context switching between processes?_ Hypothetically, if the number of active threads were lower than the number of available logical cores, no context switching would occur. However in reality, even freshly installed system like Windows 10 will have ~100-150 processes running by default, which means context switching is necessary. Higher performance comes from being able to process multiple threads concurrently, not from reduced cost of context switching. _Can we run two threads in parallel in one process?_ Yes, if code was properly written to allow multithreading.
someone explain this to university level at the electron levels. like use logic gates, an electricity because in the end it is just 1's and 0's 1 instruction at a time
can you or anybody from the comments provide a systematic overview of the relationship(technical,,,,not abstract concepts ///take x86, unix for example)bw mode bits(when exactly they are changed,,,,kindly try to be precise),kernel user mode(relating kernel stack ,,,ig both implementations ie per process,,,one for all)and virtual address spaces?
I can try to explain using a definition and a real-life example:
1. Program
Definition: A program is a set of instructions written in a specific programming language that the computer can execute. It is essentially a blueprint, and it does not perform any action until it is run.
Analogy: Think of a program as a recipe for cooking. The recipe outlines all the steps and ingredients needed to make a dish, but until you start cooking, the recipe is just an inactive set of instructions.
2. Process
Definition: A process is an instance of a program in execution. When you run a program, it becomes a process. A process has its own memory space, system resources, and an operating system environment.
Analogy: Continuing with the recipe analogy, a process is like someone actually cooking according to the recipe. Each person (process) has their own kitchen space (memory) and resources, like ingredients and utensils, which they use while cooking.
Example: When you open a web browser (like Chrome or Firefox), a process is created for it. Each tab within the browser might even have its own process, depending on the browser design.
3. Thread
Definition: A thread is the smallest unit of execution within a process. A process can have multiple threads, all sharing the same memory but running independently. Threads within a process can perform different tasks simultaneously, improving efficiency.
Analogy: In the cooking example, if multiple people are working together on the same dish, each person could be considered a thread. They share the same kitchen (memory) and ingredients (resources) but may be responsible for different parts of the task, like chopping vegetables or stirring the pot.
Example: In your web browser, multiple threads might handle different tasks: one for rendering the page, another for handling user input, and yet another for network requests. These threads all work within the same browser process.
4. Task
Definition: In many modern programming frameworks (like .NET), a task is an abstraction that represents an asynchronous operation, which can run on a thread. Tasks are typically used for parallelism and concurrency, making it easier to manage multiple operations without blocking the main thread.
Analogy: If cooking is the process and each cook is a thread, then a task might represent specific cooking jobs, like “boil water” or “slice onions.” These tasks can be assigned to cooks (threads) as they become available, optimizing workflow without everyone waiting for one task to complete before starting another.
Example: In a web application, if you request data from a database, this request can be handled as a task. The application doesn't have to wait for the database to respond (which can be slow); instead, it can continue other work until the data is ready.
Best description thanks. I got a test on this tomorrow!
@palomacardozo-willigs2314 This description is taken from ChatGpt.
@@palomacardozo-willigs2314 How was the test?
Did you generated this through ChatGPT?
@@tayyab.sheikh Yes
This is how video lessons should be done; plenty of diagrams and animations instead of someone just talking.
Thanks!
Building a house is a process, but the people doing the work to install the pipes, paint the walls and do the electrical work are all the working threads within the process of building the house.
I like to use threads synonymously with “unit of work” or “thing that executes a specific piece of work / action for the process to complete successfully.
So if I run chrome, and have 10 tabs open, I will have 10 processes running. Within each process are 1 or many units of work (called threads) responsible for memory management, access, logic, etc.
I believe the house analogy works well in a lot of cases
Also, I was asked this question in an interview during a Comp. Sci. Fundamentals round during the systems design portion of my interview process at a large, global company we all interact with daily. (Keeping vague for obvious reason)
brov why don't you make a video the house example is very brilliant
Thank you! You just helped a compsci freshman immensely.
Excellent metaphor, actually helped me understand.
Man, I understood better from your explanation than this video.
I have to admit... I have never seen such good explaination videos merged with animations and diagrams in my life. GREAT CONTENT SIR! Keep on doing what you do.
He is sleeping... Chineseeeee
Analogy for understanding process and thread
• In essence a program/process/thread is executing a job(a set of instructions). So, in that context, it’s no different than physical labour work where one executes a bunch of instructions from his/her brain and uses the required tools to complete a job
• Imagine you hire a fitter to mount your newly bought TV and you have already bought a TV mount. Here, the fitter represents a program. He has skills required to mount the TV(Set of instructions) and required tools(Data, library, plugins)
• Hiring a fitter is equivalent to installing a program. You have got commitment from him/her to work on your job. And he brings himself and loads the tools in your space ready to do the job. But, You have yet to extract the job from him. For this, you need to prepare some physical space near your TV and also give him the authorization to work at your home. This is the equivalent of creating a process where you allocate CPU and ram memory for the program to execute its job
• Just as a program can spin up multiple process, a fitter can bring multiple fitters to execute the same job. All of them work independently in their own physical space and with required authorization
• So, what's the analogy for threads? A fitter usually breaks the job into sub tasks. Here, mounting a TV can be broken in tasks like punching holes in the wall, preparing the Mount frame, adjusting the tilt etc. These subtasks represent individual threads. These threads are executed in the same memory/heap space just as the fitter performs his subtasks on his original physical space.
•Threads can be executed in parallel saving time. You can imagine this to be fitter performing tasks at the same time using his two hands. For example, one hand used to punch holes in the wall and other hand used to prepare the mount frame. This might sound like a stretch but there are some crazy people who could multitask with both hands
Thread is the mechanism of sending instructions from a program(process) to CPU. Threads are OS based mechanisms, also processes are too but a process includes at least one thread. You can imagine that a process is encapsulation of a thread or threads. The OS looks at the program(when you click an executable), creates an executing process for the execution of the program and in the process the thread or threads are the carrier of instructions which are sent to the CPU. This is the execution mechanism of a program in an OS. When you create a thread rather than the main thread, you say to the OS that in this thread those instructions should run in a different context, that will create a context switch(that is execution of instruction(s) given by a thread to the CPU in a determined duration), and by that, you will see imaginary parallel execution of different instructions in different threads. Maybe one second long instruction set will be executed in a one short lived thread while another long running thread (especially main thread) keeps running and by that short living thread will not wait the long running thread to be finished. That is the magical part of multi threaded executions.
@@mils3318 Yes, it is possible to run multiple threads in parallel within a single process in most modern operating systems. A process can have multiple threads of execution, which are also known as lightweight processes. Each thread runs concurrently and shares the process's resources, including memory and open files.
bro, we hate to read so that's why watching video but bro is writing essay here🤣🤣
@@TheZhouh12 so it is possible that, for example, if we have a 8-core CPU on it, in one currently active process, multiple threads can be executed in parallel... not multitasking.
Okay, thank you very much.
@@mils3318 When a CPU has multiple cores, it can execute multiple threads concurrently, as long as the operating system supports it. This is known as parallel processing.
@@mils3318 On a system with a single-core CPU, the operating system can still create multiple threads and schedule them to be executed one after the other, but they will not be able to run concurrently. This is known as multitasking.
This video perfectly summed up 100 lecture slides provided by my teacher without missing any key points... well done 👏👏
Fantastic video - concise and clear explanations accompanied by extremely helpful visuals. Couldn't ask for a better description within 4 minutes of time. Subscribed!
All information that I knew but would be hard-pressed to scoop out of my brain on demand - it's great to have clear and succinct refreshers like this to keep the neurons fresh
0:07 What is the difference between Process and Thread?
0:10 This is a common interview question. Let’s take a look.
0:12 To better answer this question, let’s first understand what a program is.
0:17 A program is an executable file.
0:20 It contains the code, or a set of processor instructions, that is stored as a file on disk.
0:26 When the code in a program is loaded into memory and
0:29 executed by the processor, it becomes a process.
0:33 An active process also includes the resources the program needs to run.
0:37 These resources are managed by the operating system.
0:40 Some examples are processor registers, program counters,
0:44 stack pointers, memory pages assigned to the process for its heap and stack, etc.
0:51 There is an important property of a process that is worth mentioning.
0:55 Each process has its own memory address space.
0:57 One process cannot corrupt the memory space of another process.
1:01 This means that when one process malfunctions, other processes keep running.
1:07 Chrome is famous for taking advantage of this
1:10 process isolation by running each tab in its own process.
1:13 When one tab misbehaves due to a bug or a malicious attack, other tabs are unaffected.
1:21 So what is a thread?
1:23 A thread is the unit of execution within a process.
1:26 A process has at least one thread. It is called the main thread.
1:30 It is not uncommon for a process to have many threads.
1:35 Each thread has its own stack.
1:36 Earlier we mentioned registers, program counters, and stack pointers as being part of a process.
1:42 It is more accurate to say that those things belong to a thread.
1:46 Threads within a process share a memory address space.
1:50 It is possible to communicate between threads using that shared memory space.
1:55 However, one misbehaving thread could bring down the entire process.
2:01 How does the operating system run a thread or process on a CPU?
2:05 This is handled by context switching.
2:08 During a context switch, one process is switched out of the CPU so another process can run.
2:13 The operating system stores the states of the current running
2:17 process so the process can be restored and resume execution at a later point.
2:22 It then restores the previously saved states of a
2:26 different process and resumes execution for that process.
2:30 Context switching is expensive.
2:32 It involves saving and loading of registers, switching out memory pages,
2:37 and updating various kernel data structures.
2:40 Switching execution between threads also requires context switching.
2:45 It is generally faster to switch context between threads than between processes.
2:50 There are fewer states to track, and more importantly, since threads share
2:54 the same memory address space, there is no need to switch out virtual memory pages,
2:59 which is one of the most expensive operations during a context switch.
3:03 Context switching is so costly there are other mechanisms to try to minimize it.
3:08 Some examples are fibers and coroutines.
3:11 These mechanisms trade complexity for even lower context-switching costs.
3:16 In general, they are cooperatively scheduled, that is, they must yield control for others to run.
3:23 In other words, the application itself handles task scheduling.
3:28 It is the responsibility of the application
3:30 to make sure a long-running task is broken up by yielding periodically.
3:35 This concludes our discussion of Process vs Thread.
3:39 If you like to learn more about system design, check out our books and weekly newsletter.
3:44 Please subscribe if you learned something new.
3:46 Thank you so much and we'll see you next time.
I keep getting confused between the two (threads and processes) but this depiction has helped me a ton. Thank you!
Recently came across your channel. Love the content. Very informative yet short enough to digest unlike most other tech videos
The standard here is exceptional. Thank you so much for this - I wish my lecturers had taken a leaf out of your book!
Learnt more in 4 min than from 4 hrs of classes, thank you!
Also, would love to see videos on "heap" and "serialization / encoding" (some visuals on why in-memory representation is different from byte sequence would be super super helpful ). Thanks again for these great videos!!!!
Good refresher for me. Thanks once again for the awesome and meaningful video.
This channel is a gem
- **Definition Overview**
- **Process:** Created when a program (executable file) is loaded into memory; includes resources managed by the OS (e.g., registers, memory pages).
- **Key Property:** Each process has **its own memory address space**, preventing interference between processes; isolation ensures other processes continue running if one fails (e.g., Chrome tabs).
- **Thread:** Unit of execution within a process; every process has at least one thread, with threads sharing the same memory space.
- **Thread vs. Process Context**
- Threads share memory, enabling easy communication but risking the whole process if one thread fails.
- Processes have **separate memory spaces**, enhancing isolation but making inter-process communication more complex.
- **Context Switching:** The OS switches between processes/threads, saving/restoring states. Switching between threads is faster than between processes due to shared memory.
- **Context Switching Details**
- Context switching is **expensive**, requiring saving/loading registers, memory pages, and updating kernel data structures.
- **Thread switching** is faster since threads share memory, avoiding virtual memory page switching, which is the most costly part.
- Mechanisms like **fibers** and **coroutines** are designed to minimize context-switching costs by being cooperatively scheduled, with tasks yielding control periodically.
- **Conclusion**
- Threads enable efficient execution within processes but can compromise stability.
- Processes ensure strong isolation at the cost of slower context switching.
- The discussion emphasizes trade-offs between complexity and performance.
Holy cow... so clear. So coherent. So neat. The graphics go perfectly with your explanation. Thank you for this.
Great channel. Simple, short and straight-forward
1:00 "one process cannot corrupt the memory space of another process" - well, should not be able to.
The graphics and animations are so good!
(And the content of course 😄)
Thanks for sharing!
Thanks for those visuals, I can tell a lot of love went into them
This 4 minute video sums up your years of coding experience.
powerful concepts within just 4 minutes. Thanks
I really love these videos!!! The visuals are very helpful to build mental models and understand these complex concepts - thank you so much!!!
Best video on this subject by far
Multi tasking and multi threading needs to be well known and especially where to use under what circumstances 🙏
YOu have a great way of explaining things. Keep the good work! Can't wait you get into subjects like Docker and Kubernetes.
This 4-minute video explains what my professor could not do in an entire semester.
Sir Alex, Please do in-depth videos. The content you post is so amazing but they are covered on a high level. Please go deep and explain things.
Thank you for this video! I got this question in an interview this week, and I wish I could have watched this video before the interview! So concise but detailed explanation! And now I get to know what is the purpose of "yield" in Python. None of the resources about it explain in context of OS and context switching...!
Code in a program, loaded into memory and executed by the processor, it becomes a process❤
The best explanation I watched!
love it, short and on point. Also i like your style! directly subbed :)
Nice and insightful capture of concepts that I were fuzzy on : thanks for putting this together
gosh, this is so clear and informative
program - executable instructions of code
Program disc + ram + cpu = process
process control block(PCB)
thread - unit of execution within process
stack
pointers
counters
thread vs process?
threads (of the same process) run in a shared memory space,
processes run in separate memory spaces
shared memory
virtual memory pages switching ⚠
fibers
coroutines
clear concise explanation together with great graphics. Would love to know how you guys do your graphics.... Thank you...
These animations are beautiful holy. Do you mind sharing just how they were accomplished?
A process is a program executing by a processor. A process doesn't share memory with another process. It has a collection of threads: the main thread and the other threads if any.
A thread is an execution unit inside a process. It shares the same heap memory with the other threads in the same process. But it has its own stack memory.
Captain 😅 it was precisely explained in the video
We need more of these videos
This is high quality content, but I'm also curious if you could do a video on how you make your videos? :)
very good. makes more sense now.
Thank you! Very clear and useful video content!
This video helped me, thank you 😊
Excellent Stuff!
Thanks for the great video!🎉
If adding coroutine comparison, that would be perfect!
Please make more such videos on common interview questions explained so greatly
Well explained. Thank you.
great explanation!
Brilliant channel
This is a brilliant video.
You can add subtitles also for a larger audience
Great Video
thank you for the information, sr. Subscribed!!!!
Nice video! What about doing one about coroutines.
Love you Sir, please keep it up. and Thank you very much
Many many thanks! This is a great video instruction!
Hi, can the upcoming videos be on -> http polling (short and long), streaming, websockets etc. ? Thanks your teaching style is just awesome
Best explanation!!!
deserve a subscribe
Great video. But I didn't understand how auto yielding reduces the cost of context switching? Because after yielding, context switching will have to be done anyway for the CPU to execute other processes.
fan of ByteByteGo 👏
Well done
Amazing SIR!
simply awesome
pls upload more videos on operating systems concepts
As always, incredible video! Real great work. I'm so impressed by the animations. How do you create them?
Man you're dope, thanks a lot
Love your channel. Subscribed to it.
If you don't mind, what tool do you use to author the content? I find this to be more engaging vs powerpoint based sessions.
Thanks
I'd be interested in hearing this too
@@thieltube390 Looks like Adobe After Effect
animation is amazing
Great video. Thxs
我的娘这么复杂🥲 amazing content tho! Thank you!
whole semester of a damn college course in 5 mins here
Good video
It would be much more interesting to watch a video "fibers vs coroutines" :)
Thanks for great video. Two questions,
1. So to run K programs embarassingly parallel via multi-processing you have to have K CPU? If number of CPU < K then it would have to switch context, correct?
2. when we are talking about multi-processing python basically two of same script is copied to each process memory?
Thanks for your sharing
For the process having multiple threads, OS would provide time quantum of execution per thread under a process? or each thread would get (1 quantum time / no. of threads in process) time for execution?
Can you please explain about fibres & co-routines?
I like how he’s a fan of witcher 3
I am about to have an interview and this topic has given me a headache for days :(
So your not suitable there
You explanation is good but need voice to be more clear. I think
And what if we have processors with more cores. Does this mean that we can run more processes at the same time? In that case, do we potentially have higher performance because more processors mean less context switching between processes?
Can we run two threads in parallel in one process? Or is only multitasking threads allowed per process (execution one by one)?
_And what if we have processors with more cores. Does this mean that we can run more processes at the same time?_
Yes, every logical core can run one thread.
_In that case, do we potentially have higher performance because more processors mean less context switching between processes?_
Hypothetically, if the number of active threads were lower than the number of available logical cores, no context switching would occur. However in reality, even freshly installed system like Windows 10 will have ~100-150 processes running by default, which means context switching is necessary.
Higher performance comes from being able to process multiple threads concurrently, not from reduced cost of context switching.
_Can we run two threads in parallel in one process?_
Yes, if code was properly written to allow multithreading.
Describe fibers in react
What software was this video made with?
I'm also interested in this question. Did you find it out?
@@kovolexiy nope a lot of channel not willing to share knowledge they scared of competition. What’s your telegram handler let’s research this up
@@kovolexiy Looks like Adobe After Effect
Does anyone know what animation software is used to create this video?
I was thinking of this for a long time. I'd also like to know. Not interested in the animation part. But the diagrams are beautiful
@@dgeo27 Looks like Adobe After Effect
What app did you use to create that animated presentation graphics?
What program is used for visualization?
What is registers ?
what is the software used for animation
someone explain this to university level at the electron levels. like use logic gates, an electricity because in the end it is just 1's and 0's 1 instruction at a time
Notification of successful receipt of BTC transaction
The simplest explanation I would say that the Process is virtualization of memory and Thread is virtualization of CPU the rest is following cons
Teaching them plz
can you or anybody from the comments provide a systematic overview of the relationship(technical,,,,not abstract concepts ///take x86, unix for example)bw mode bits(when exactly they are changed,,,,kindly try to be precise),kernel user mode(relating kernel stack ,,,ig both implementations ie per process,,,one for all)and virtual address spaces?
So how many process can 4 ram handle
Same count of your mommy's bre*ast
Read the Windows internals book by Mark Russinovich and you guys will discover the new universe
Will it help me too understand Linux too?(Or it is entirely different)