This is a masterful exposition on the linux kernel fundamentals of containers, as well as a rich history of the origin of not only containers in general, but also companies like Odin (formerly Parallels) and Docker. Pure banger!
His pronunciation and articulation is spot-on which is a must have skill in public speaking be it a tech talk or so. People seems to not follow this most of the times and forget the audience which they are addressing to. The skills comes with practice and practice. I mean, if you simply want to read out your slides and what is going on in your mind with MTI then, it could bleed the ears out of poor audience.
16:42 As long as the container's kernel is a good one, it makes resource decisions much more efficiently than hypervisor's, because there is no two kernels fighting each other over the resource decisions. There is only a single kernel arbitrating all of the resources in the entire system, and it sees everything at the correct granularity. So a hypervisor only really sees when it wants to control memory resources, it sees pages, and it doesn't even see what the LRU listed in the guest kernel is, and which page is going to be reclaimed next. So under memory pressure just takes a random page out of the guest that happened to be at the bottom of the LRU list instead of at the top, then the guest is going to evict this page, and then it's going to come to the one that the hypervisor just took away. And the hypervisor is going to go through some horrible thing where it tries to swap that page back into the guest's again. Whereas the kernel that's arbitrating containers, not only sees all of the pages that everybody's using, it itself controls the LRU list because the container's Operating System only starts at 'init' -- it has no kernel piece -- and it also sees all of the objects and how they're being used inside every container. So, it has much fuller information when it comes to making resource decisions, and this is why the resource decisions tend to e made much more efficiently inside containers
It is a teaching art to bring a difficult topic over so that actually most people can understand it. I think the speaker was not able to achieve it with me. I could not listen to him very good... But i think, he chose very good topic and important viewpoints, but the sound of his mic is really annoying. What i will remember from this talk is only "unshare -r -U" rest was just gibberish blabla
A lot gibberish indeed. What I could understand was blablablablaba we invented containers. Blablablabla containers are different than vm. Talks a lot informs little.
This is a masterful exposition on the linux kernel fundamentals of containers, as well as a rich history of the origin of not only containers in general, but also companies like Odin (formerly Parallels) and Docker. Pure banger!
His pronunciation and articulation is spot-on which is a must have skill in public speaking be it a tech talk or so. People seems to not follow this most of the times and forget the audience which they are addressing to. The skills comes with practice and practice. I mean, if you simply want to read out your slides and what is going on in your mind with MTI then, it could bleed the ears out of poor audience.
Great talk from a very talented and knowledgable person.
Very informative talk. I wish this guy had all the time in the world to teach whatever he knows.
16:42
As long as the container's kernel is a good one, it makes resource decisions much more efficiently than hypervisor's, because there is no two kernels fighting each other over the resource decisions.
There is only a single kernel arbitrating all of the resources in the entire system, and it sees everything at the correct granularity.
So a hypervisor only really sees when it wants to control memory resources, it sees pages, and it doesn't even see what the LRU listed in the guest kernel is, and which page is going to be reclaimed next.
So under memory pressure just takes a random page out of the guest that happened to be at the bottom of the LRU list instead of at the top, then the guest is going to evict this page, and then it's going to come to the one that the hypervisor just took away.
And the hypervisor is going to go through some horrible thing where it tries to swap that page back into the guest's again.
Whereas the kernel that's arbitrating containers, not only sees all of the pages that everybody's using, it itself controls the LRU list because the container's Operating System only starts at 'init' -- it has no kernel piece -- and it also sees all of the objects and how they're being used inside every container.
So, it has much fuller information when it comes to making resource decisions, and this is why the resource decisions tend to e made much more efficiently inside containers
Brilliantly summary on containers.
beginners...
great talk to, was watching the whole thing! thanks
Good information for beginners to learn about container
Very heavy but valuable
Really informative, the presentation style is superb. Thanks a lot
Reggie Watts is talking to me... about containers.
It is a teaching art to bring a difficult topic over so that actually most people can understand it. I think the speaker was not able to achieve it with me. I could not listen to him very good... But i think, he chose very good topic and important viewpoints, but the sound of his mic is really annoying. What i will remember from this talk is only "unshare -r -U" rest was just gibberish blabla
A lot gibberish indeed. What I could understand was blablablablaba we invented containers. Blablablabla containers are different than vm. Talks a lot informs little.