It's a very interesting read and I request everyone from infra read it and recommend others to put down a few minutes and read it.
To give the VDSM POV. Even though it make things faster. It still doesn't solve the IO issues since they are caused by a mix of kernel issues (D state) and python libraries implementations. Namely not releasing the GIL either by mistake or for optimization sake or because an underlying C implementation just isn't thread safe. It is an interesting read about how locking policy effects speed even with a single Lock. It's good to remember this was made without effecting how people write python code at all. Thanks Francesco for sending it. ----- Original Message ----- > From: "Francesco Romani" <from...@redhat.com> > To: "vdsm-devel" <vdsm-devel@lists.fedorahosted.org> > Sent: Thursday, March 13, 2014 10:33:34 AM > Subject: [vdsm] The new GIL in python 3.2+ > > Hi everyone > > I found some time ago this very good presentation about the improvements > made on python 3.2+ for the GIL (which unfortunately is still there... I > think we need pypy to get rid of it) > > http://www.dabeaz.com/python/NewGIL.pdf > > > -- > Francesco Romani > RedHat Engineering Virtualization R & D > Phone: 8261328 > IRC: fromani > _______________________________________________ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
