Hi, everyone. In the last video, we talked about concurrency. We talked about how we can utilize the CPU wait time, and in order to give the full CPU utilization of any of the tasks that we are running. So now we're going to be talking about concurrency and parallelism. So why is this conversation even there was a lot of people confuse between concurrency and parallelism, parallelism, they like that, okay, if multiple tasks are being multiplexed on the CPU, then isn't that parallel computing, or isn't that a parallel task? So if this is a serious task, isn't this a pilot task?

And in short, no, because if you look at concurrency, gopher comes waits for two minutes while he's waiting, another gopher comes. So this in this preemption is happening, right. So this is a pre emptive process. But in parallel in parallelism, what we do is we take one method method, and then we replicate across all of our CPU cores. So if you look at the other diagram over here, So this is our concurrent paradigm that we had the same concurrent paradigm can be stretched across multiple CPU cores. So this now has become parallel.

So we have an array of processes, which want to take the CPU time. But now we can divide those into two CPUs. And then both the set of tasks and the set of tasks can execute parallely. Note that if you're if you're looking at one CPU, and if you're looking at one thread, it might still be cereal. But stretching that paradigm across multiple cores into a multi threaded multiple core architecture is what is known as vandalism. So there is a really great talk by Rob pike.

I'm going to share the link in the resource section. I want you all to take a look at that talk. And it's going to clear a lot of concepts or a lot of doubts that you have around concurrency parallelism. So I hope you're also cleared. See you guys in the next video.