Комментарии:
Thanks for the great video!🎉
ОтветитьSo how many process can 4 ram handle
ОтветитьTeaching them plz
ОтветитьThis 4-minute video explains what my professor could not do in an entire semester.
ОтветитьI think your animator is overdoing it, am having trouble focusing on the content. Also, could you pause and take breaks, because it feels like you're rushing. Thank you for the content though.
ОтветитьThis video helped me, thank you 😊
ОтветитьBest video on this subject by far
ОтветитьI like how he’s a fan of witcher 3
ОтветитьCode in a program, loaded into memory and executed by the processor, it becomes a process❤
Ответитьpowerful concepts within just 4 minutes. Thanks
Ответить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
This is a brilliant video.
ОтветитьLove you Sir, please keep it up. and Thank you very much
Ответить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?
This 4 minute video sums up your years of coding experience.
Ответить超讚得
Ответить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
ОтветитьThis is high quality content, but I'm also curious if you could do a video on how you make your videos? :)
ОтветитьThis should not be a fang interview question 💁
ОтветитьMan you're dope, thanks a lot
ОтветитьCan you please explain about fibres & co-routines?
Ответить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!!!!
ОтветитьI really love these videos!!! The visuals are very helpful to build mental models and understand these complex concepts - thank you so much!!!
ОтветитьMulti tasking and multi threading needs to be well known and especially where to use under what circumstances 🙏
Ответить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.
simply awesome
Ответитьpls upload more videos on operating systems concepts
ОтветитьGreat video. Thxs
Ответить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)
The simplest explanation I would say that the Process is virtualization of memory and Thread is virtualization of CPU the rest is following cons
ОтветитьIt would be much more interesting to watch a video "fibers vs coroutines" :)
ОтветитьGreat channel. Simple, short and straight-forward
Ответитьwhat is the software used for animation
ОтветитьHoly cow... so clear. So coherent. So neat. The graphics go perfectly with your explanation. Thank you for this.
ОтветитьMany many thanks! This is a great video instruction!
ОтветитьIf adding coroutine comparison, that would be perfect!
ОтветитьBrilliant channel
ОтветитьThis is how video lessons should be done; plenty of diagrams and animations instead of someone just talking.
Thanks!
Please make more such videos on common interview questions explained so greatly
ОтветитьFantastic video - concise and clear explanations accompanied by extremely helpful visuals. Couldn't ask for a better description within 4 minutes of time. Subscribed!
ОтветитьDo you feel like this same verbage is consistent when considering Erlang?
ОтветитьThanks for your sharing
ОтветитьWhat app did you use to create that animated presentation graphics?
Ответить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?
ОтветитьThe graphics and animations are so good!
(And the content of course 😄)
Thanks for sharing!
Best explanation!!!
Ответить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.
ОтветитьYOu have a great way of explaining things. Keep the good work! Can't wait you get into subjects like Docker and Kubernetes.
ОтветитьAs always, incredible video! Real great work. I'm so impressed by the animations. How do you create them?
Ответитьanimation is amazing
Ответить