News for hackers. Stuff that matters.
Re:PostgreSQL Performance on Docker by jpgvm on Wednesday July 09, 2014 @11:26PM (#8013441)
No.

First of all. Docker is -not- virtualisation. It's -containerization-. Effectively namespacing and little else.

In Linux namespaces are hierarchal, I can arrange them in a tree. Where at the top namespace A can have 2 sub-namespaces B and C. A can see the process table of B and C, but B and C can only see their respective process tables. This is called pid name spacing.

Full containerisation on Linux actually requires a bunch of different namespacing, firstly the pid namespaces above but also uids, network (yes, in Docker your container has a fully namespaced network stack in including it's own (multiple!) route tables and adapters) and also device/filesystem etc.

The key take away here is NOTHING is being virtualised, we are simply only showing a section of the system to each process depending on it's position in the namespace hierarchy. What this means is Docker (well really Linux.. Docker is just glue that calls this functionality up) is just.. Linux. Nothing fancy and definitely nothing KVM/Xen/VMWare would be able to influence.

Re:PostgreSQL Performance on Docker by crazy1van on Thursday July 10, 2014 @10:33AM (#8015081)
"DigitalOcean uses KVM virtualization" All of these benchmarks were run on DigitalOcean.

Source: https://www.digitalocean.com/help/

Re:PostgreSQL Performance on Docker by ticklemyelmo on Thursday July 10, 2014 @10:16AM (#8015034)
> The key take away here is NOTHING is being virtualised

The droplet itself is virtualized.

Re:PostgreSQL Performance on Docker by jpgvm on Thursday July 10, 2014 @12:48PM (#8015660)
Yes I realize this, if you read my comment I was addressing that KVM couldn't have interfered with Docker if it tried.