Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
1–10 of 15 posts
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#2[deleted]
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#3That was great. PyPy looks like a great bytecode equivalent to what is happening with other languages and he does highlight this "disconnect" that is raised by new approaches that produce amazing results. He even got a async node joke in there, cracked me up.
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#4This keynote was by far the highlight of PyCon for me. I hope to hear David speak again soon.
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#5I do nothing with Python and I couldn't care less about Python, but... I really enjoyed this video. Great talk!
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#6I didn't get a chance to see this at PyCon, but wow, this video really helped me understand some of the fundamentals of PyPy. (For example, I had no idea it didn't have a parser, and instead only acts on the intermediate representation of Python bytecode.)
Also, David Beazley has a great way of making difficult concepts approachable.
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#7[deleted]
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#8Can somebody explain the end of lecture?
Why Ruby and PyPy looks similar in this benchmark?
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#9Can somebody explain the end of lecture? Why Ruby and PyPy looks similar in this benchmark?
Yeah, he skipped over what might have been the most interesting part of the talk! I have a very cursory understanding of how the GIL works, so it would be nice to understand what's going on here.
Re: Lets Talk About Something Diabolical: A PyPy Intro (David Beazley PyCon keynote)
#10Can somebody explain the end of lecture? Why Ruby and PyPy looks similar in this benchmark?
The bug that caused Ruby to run slow on that benchmark turned out to be one that afflicted earlier versions of Python. It's a priority inversion problem related to the GIL.
GIL: The global interpreter lock, basically a single lock that threads running in Python or Ruby synchronize on frequently to sync up, which causes problems in multithreaded applications.
Priority inversion: I don't think I'm qualified to explain this clearly, so I'll defer to wikipedia: https://en.wikipedia.org/wiki/Priority_inversion
The later slide where he showed PyPy having terrible performance on a benchmark where the other two code bases worked fine was an unrelated problem.
His point was that whereas he was able to dig into the Ruby implementation and figure out why it was running slow, it was much harder to find the reason why PyPy was not performing as it should due to the implementation complexity.
It is basically tying back to the analogy of the VW versus the Porsche. He could often fix his VW using a pocket knife, which would be very difficult to do with a Porsche.